Unity 6.5 Is Here: Should Your Studio Upgrade?

Unity 6.5 现已发布：你的工作室应该升级吗？

Unity 6.5 arrived in mid-June 2026, and if you skimmed the announcement you would be forgiven for filing it under “minor update.” There is no single headline feature to point at. But 6.5 is more consequential than it looks, because the important changes are subtractions. Several systems that a lot of production projects still lean on have been marked for removal, and the countdown has started. This post is the read we would give a client: what actually changed, which parts matter depending on where you are in your development cycle, and a straight answer on whether to upgrade.

Unity 6.5 于 2026 年 6 月中旬发布。如果你只是粗略浏览了公告，将其归类为“小更新”也情有可原，因为并没有什么单一的重磅功能。但 6.5 版本的意义远比表面看起来重大，因为其重要的变化在于“删减”。许多生产项目仍在依赖的几个系统已被标记为即将移除，倒计时已经开始。本文是我们提供给客户的解读：实际发生了哪些变化，根据你所处的开发周期哪些部分至关重要，以及关于是否升级的直接建议。

First, What Kind of Release This Is

首先，这是什么类型的版本？

Under the Unity 6 model there are two kinds of release, and the difference decides most of the upgrade question on its own. Update releases (6.4, 6.5, 6.6) carry the newest features, platform support, and performance work. Unity describes 6.5 as a Supported release with the same stability and critical-fix quality as an LTS, right up until the next release lands. They are aimed at projects in active or mid-cycle development. LTS releases (6.3 LTS, and 6.7 LTS later this year) are the ones to lock production on. 6.3 LTS is supported with fixes and platform updates through December 2027. They are the safe harbour for a title that is shipping or about to. One date to note if you have not moved recently: Unity 6.0 LTS support ends in October 2026. If you are still on it, that is the real deadline on your calendar, not 6.5.

在 Unity 6 的模式下，有两种发布类型，这种区别本身就决定了大部分关于升级的决策。更新版本（6.4、6.5、6.6）包含最新的功能、平台支持和性能优化。Unity 将 6.5 描述为一个“支持版本”（Supported release），在下一个版本发布之前，它拥有与 LTS（长期支持）版本相同的稳定性和关键修复质量。它们旨在服务于处于活跃开发或中期阶段的项目。LTS 版本（6.3 LTS 以及今年晚些时候的 6.7 LTS）才是用于锁定生产的版本。6.3 LTS 将获得修复和平台更新支持至 2027 年 12 月。对于正在发布或即将发布的游戏来说，它们是安全的港湾。如果你最近没有迁移，请注意一个日期：Unity 6.0 LTS 的支持将于 2026 年 10 月结束。如果你仍在使用该版本，那才是你日程表上真正的截止日期，而不是 6.5。

The Real Story: What Is Being Deprecated

真正的重点：哪些功能被弃用了？

This is the part worth your attention. None of these break your project today, but each one is a planning item. The Built-In Render Pipeline is deprecated. BIRP still works, and Unity has committed to supporting it through the full 6.7 LTS lifecycle, but it will become obsolete in a future release. If your project is still on BIRP, this is your signal to scope a migration to URP while it is a controlled piece of work rather than something forced on you by an engine upgrade you cannot avoid. Unity has added command-line and Render Pipeline Converter tooling to help move BIRP assets across, which makes now a sensible time to start.

这是最值得你关注的部分。虽然这些变动目前不会破坏你的项目，但每一项都应列入规划。内置渲染管线（Built-In Render Pipeline, BIRP）已被弃用。BIRP 目前仍可使用，Unity 也承诺在 6.7 LTS 的整个生命周期内提供支持，但它将在未来的版本中彻底淘汰。如果你的项目仍在使用 BIRP，这是一个信号：趁现在工作尚在可控范围内，尽快规划迁移到 URP，而不是等到未来被迫进行无法避免的引擎升级时才手忙脚乱。Unity 已经增加了命令行和渲染管线转换工具来帮助迁移 BIRP 资源，现在正是开始行动的明智时机。

Dynamic batching is deprecated and will be removed in a future release. If you rely on it for draw-call reduction, you will want to move to GPU instancing, the SRP Batcher, or static batching depending on your content. HDRP is in maintenance. It remains available and is still being brought to new platforms (the Nintendo Switch 2 among them), but it is no longer receiving new features. Unity is consolidating around URP as the primary pipeline for all targets. If you are choosing a pipeline for a new project today, that consolidation should inform the decision.

动态批处理（Dynamic batching）已被弃用，并将在未来版本中移除。如果你依赖它来减少绘制调用（draw-call），你需要根据内容改用 GPU 实例化（GPU instancing）、SRP Batcher 或静态批处理。HDRP 目前处于维护状态。它仍然可用，并继续适配新平台（包括任天堂 Switch 2），但不再接收新功能。Unity 正在将 URP 整合为所有目标平台的主要管线。如果你今天正在为新项目选择管线，这一整合趋势应作为你的决策依据。

Smaller items: the HDRP OptiX denoiser is deprecated in favour of Intel’s hardware-agnostic OIDN (a compatibility-breaking change if you use OptiX temporal coherence in path tracing), the ReplayKit API has been removed after being obsolete since 6.0, and Entities Journaling is deprecated. Key takeaway: The headline of Unity 6.5 is not a feature, it is a set of end-of-life notices. The studios that handle these calmly are the ones that read the deprecation list on every release and schedule the work early. The ones that get hurt are the ones that discover BIRP is gone during a rushed engine upgrade two years from now.

其他较小的变动：HDRP OptiX 降噪器被弃用，转而支持英特尔硬件无关的 OIDN（如果你在路径追踪中使用 OptiX 时间相干性，这将是一个破坏兼容性的变化）；ReplayKit API 在 6.0 版本后已过时并被移除；Entities Journaling 也被弃用。核心要点：Unity 6.5 的头条不是某个功能，而是一系列“生命周期结束”的通知。那些能从容应对的工作室，通常会在每次发布时阅读弃用列表并尽早安排工作。而那些会受到伤害的，往往是在两年后匆忙进行引擎升级时，才发现 BIRP 已经消失了。

The Changes That Matter for Mobile and Web

对移动端和 Web 端至关重要的变化

If you ship to mobile or the browser, this is where 6.5 earns the upgrade. Web builds got materially better. WebAssembly 2023 is now the default target, Unity bundles the Emscripten compiler with the web platform package so you no longer manage it yourself, and IL2CPP metadata has been optimised to cut web build sizes and shorten load times. There is also a runtime specifically optimised for mobile browsers. For anyone shipping WebGL, this is a real improvement to the two things that hurt most: download size and time-to-first-frame. Android startup is faster, with build-level optimisations reducing launch time. On mobile, startup time is a retention lever, not a nicety, so this is worth having.

如果你发布移动端或浏览器游戏，这就是 6.5 值得升级的原因。Web 构建版本有了实质性的提升。WebAssembly 2023 现在是默认目标，Unity 将 Emscripten 编译器打包在 Web 平台包中，因此你无需再自行管理；IL2CPP 元数据也经过优化，以减小 Web 构建体积并缩短加载时间。此外，还有一个专门针对移动浏览器优化的运行时。对于任何发布 WebGL 的开发者来说，这切实改善了最令人头疼的两件事：下载大小和首帧时间。Android 启动速度更快，构建级别的优化缩短了启动时间。在移动端，启动时间是影响留存的关键杠杆，而非锦上添花，因此这非常值得拥有。

iOS and tvOS get an experimental Swift Xcode project type. Unity is rearchitecting the layer that connects the engine to Apple platforms, and there is now a dedicated public API for native plug-ins that supports lifecycle events, overlay content, and messaging back to C#. If your game depends on native iOS integrations, this is a direction worth tracking, though “experimental” means you test it, you do not ship on it yet. One gotcha to check before your next iOS submission: UnityWebRequest has switched its underlying networking library from NSURLSession to Mbed TLS. As a result it is no longer automatically exempt from App Store encryption export regulations. If you use UnityWebRequest, review whether your export-compliance declarations need updating. It is a five-minute check that prevents a submission rejection.

iOS 和 tvOS 获得了实验性的 Swift Xcode 项目类型。Unity 正在重构连接引擎与 Apple 平台的层级，现在有一个专门用于原生插件的公共 API，支持生命周期事件、覆盖内容以及回传消息给 C#。如果你的游戏依赖原生 iOS 集成，这是一个值得关注的方向，尽管“实验性”意味着你可以测试它，但还不能用于正式发布。在下次提交 iOS 应用前，有一个陷阱需要检查：UnityWebRequest 已将其底层网络库从 NSURLSession 切换为 Mbed TLS。因此，它不再自动豁免于 App Store 的加密出口法规。如果你使用 UnityWebRequest，请检查你的出口合规声明是否需要更新。这是一个只需五分钟的检查，却能防止提交被拒。

For Artists and 2D Teams

给美术和 2D 团队

Briefly, because it is real value even if it is not our core focus: Unity 6.5 adds APIs for custom 2D lighting and shadow systems, a BlendShape API that brings free-form, cage-based deformation to sprites, and continued work on the 2D physics core. Shader Graph gains a shader-function reflection API that lets you author HLSL nodes directly and have them appear automatically in the graph, plus new Expression and Switch nodes that cut down graph clutter. The AI tooling built into the Editor (Assistant for contextual help, Generators for assets, Sentis for runtime inference) continues to expand.

简要说明一下，因为即使这不是我们的核心关注点，它们也具有实际价值：Unity 6.5 增加了用于自定义 2D 光照和阴影系统的 API，引入了为精灵（Sprites）提供自由形式、基于笼状（cage-based）变形的 BlendShape API，并持续优化了 2D 物理核心。Shader Graph 获得了着色器函数反射 API，允许你直接编写 HLSL 节点并使其自动出现在图中，此外还有新的 Expression 和 Switch 节点，可以减少图表的混乱。内置于编辑器中的 AI 工具（用于上下文帮助的 Assistant、用于资源的 Generators、用于运行时推理的 Sentis）也在持续扩展。

The Runtime Is Shifting Underneath All of This

这一切之下的运行时正在发生转变

Worth flagging, because it is the bigger story on the horizon: Unity 6.5 quietly continues the transition from the Mono scripting runtime to Microsoft’s CoreCLR. That migration is the most significant change to Unity’s C# layer in over a decade, and it lands properly in the next two releases: an experimental CoreCLR player in 6.7, and the full removal of Mono in 6.8. It deserves its own treatment rather than a paragraph here, so we…

值得一提的是，因为这是未来更大的趋势：Unity 6.5 正在悄然继续从 Mono 脚本运行时向微软 CoreCLR 的过渡。这次迁移是 Unity C# 层十多年来最重大的变化，它将在接下来的两个版本中正式落地：6.7 版本中提供实验性的 CoreCLR 播放器，并在 6.8 版本中完全移除 Mono。这值得专门撰文探讨，而不是在这里只用一段话带过，所以我们……