For those who don’t know the tool: Unity is a realtime game engine that ships to desktop and consoles, and Platform Toolkit sits in the build and platform integration layer, so your release pipeline spends less time arguing with targets and more time making frames.

What changed and when

A Unity product update at the Game Developers Conference included two platform-focused announcements. First, official Steam support is planned, including a native solution intended to help bring games to the platform. This support should be covering Steam, Steam Deck, and Steam Machine.

Second, targeted enhancements to the engine Linux runtime are planned with the goal of native performance increases. The same update frames this work as a way to reduce reliance on running Windows builds through Proton.

https://twitter.com/unitygames/status/2031777294394552663

Steam support without the scavenger hunt

If you have shipped on Steam before, you already know the punchline: it is possible, but the path has historically depended on what you integrate and how you maintain it over time. The new message is about making that experience feel like a supported lane rather than a community tradition. The announcement describes a built-in platform toolkit that will facilitate the workflow of bringing games to Steam. That phrasing matters for production because it points to changes that sit inside your day to day build and release loop, not just documentation or a sample project you copy once and then forget until it breaks on a Friday.

So for now, the important production takeaway is narrower and still useful: the roadmap points at a native solution for Steam targeting Steam Deck and Steam Machine as part of the same effort.

Linux runtime work aimed at less Proton reliance

The second half of the update calls out targeted enhancements to the Linux runtime in Unity, framed around native performance gains and removing the need to rely on Windows through Proton.

For teams shipping to Linux ecosystems, that focus is notable because runtime changes tend to land below your gameplay code and sometimes below your rendering decisions. When runtime behavior shifts, it can affect performance, stability, input, windowing, threading, and the kinds of issues that only appear on particular hardware and driver mixes.

Still, the direction is clear enough to influence planning. If your release strategy currently depends on Windows builds plus Proton, the announcement signals that native Linux performance is a priority area rather than an afterthought. That can change how you triage bugs, where you invest profiling time, and how you communicate platform expectations internally.

What is still missing

The story is big, but the specifics are currently thin in the provided material. There is no published schedule in the sources for when official Steam support will ship. There is no description of what the native solution includes, whether it is a package, an editor workflow, a build target configuration, or a set of services. There is no compatibility matrix that spells out editor versions, player versions, or which OS targets are covered.

That means any team looking to act immediately should treat this as a roadmap signal rather than a shipping feature drop. It is a green light to pay attention, not a license to rewrite your platform plan overnight.

https://unity.com

https://gdconf.com

The post Official Steam support lands on Unity roadmap first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

The open-source engine Godot hits a new development milestone with its 4.6-dev5 snapshot. As the project moves toward feature freeze (scheduled for 3 December 2025), this build bundles a wide set of changes across rendering, export workflows, patching and editor usability.

Use D3D12 by default on Windows

For Windows users the default rendering backend now switches from Vulkan (or older defaults) to Direct3D 12 (D3D12). This reflects long-standing concerns about Vulkan stability on Windows, particularly around GPU driver reliability. The change only affects new projects created in 4.6-dev5 or later. For existing 4.5 projects you must manually set rendering/rendering_device/driver.windows = d3d12.

Delta-encoded PCK patching

Content patching sees a major enhancement. Previously, patch exports compared files at a per-file level — meaning even a single-character change in a large localisation file triggered a full export of that file.
Now, the engine supports delta encoding (binary diffing) when exporting patches. Only the modified bytes are stored, potentially turning megabyte-sized patches into lightweight, byte-level edits. This must be explicitly enabled in the Patching tab of the export dialog. Note: applying such patches comes with a small runtime cost (a few milliseconds worst case).

Native Android Gradle builds via companion app

Exporting to Android gets more robust. Previously, Godot allowed injecting game data into a pre-built APK — quick but limited. Now, thanks to a companion build app providing a Linux-like build environment on Android, Godot can run full Gradle builds on-device. This enables easier use of Android plugins (for example billing, XR, ads) and closer parity with native Android builds. The companion app is planned for release via Google Play and other stores before Godot 4.6 stable ships.

OpenXR 1.1 support and improved XR export

Godot now supports OpenXR 1.1. On devices with 1.1 support, the engine will automatically enable the newer API features. Loader logic for AOSP (Android Open Source Project) platforms has been moved from a vendor-specific plugin into Godot’s core. That means games targeting generic Android distributions can now export one APK that runs across many XR headsets without separate vendor plugins. The existing first-party OpenXR vendor plugin remains available for vendor-specific extensions and permission management.

2D renderer overhaul: major performance gains

The 2D renderer, especially for scenes benefiting from batching, gets substantial optimisations. Previous automatic 2D batching already reduced CPU usage by combining similar draw calls. In 4.6-dev5 the GPU cost of batching has been reworked. Tests show that on GPU-bound scenarios performance improved between 1.1× and 7× compared to prior versions.

Editor and engine usability upgrades

This snapshot also introduces many smaller but meaningful improvements across the editor, scripting, and core engine: rotating scene tiles in TileMapLayer, improved timeline resizing for animations, better GDScript debugging, extended GUI layout options, improved file attribute support under operating systems, and more.

What, if anything, to watch out for

As with any pre-release build, 4.6-dev5 is not a stable release. The official download page warns users to keep backups or use version control to avoid data loss or regressions. Depending on your project, some changes, like the switch to D3D12 or the use of delta-encoded patches, might require manual configuration or testing before relying on them.

This build is part of a broader push toward the stable 4.6 release. With feature freeze scheduled for 3 December 2025, this dev snapshot likely represents the last major feature add before the engine enters polish-only mode. Developers should test these changes thoroughly before upgrading production projects.

Try the Webversion in your Browser!

And read more about this Release here: https://godotengine.org/article/dev-snapshot-godot-4-6-dev-5/

The post Godot 4.6-dev5 lands: D3D12 default, Delta Patching, Android Gradle, 2D boosts first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

The Open 3D Foundation has released version 25.10.0 of its open-source 3D engine, O3DE. This October 2025 update focuses on engineering stability, build performance, and developer quality-of-life rather than visual feature expansion. The release signals a steady maturation of the engine’s toolchain, with many improvements hidden beneath the surface but significant in day-to-day use.

What’s New in 25.10

O3DE 25.10 introduces a re-engineered installation and build process. The installers have been reduced in size, roughly 26 percent smaller on Windows and about 40 percent smaller on Linux. Dependency handling and installer feedback have been streamlined, making fresh installations and version upgrades less painful. Debug and iteration performance has also improved; the foundation reports faster build times and reduced editor memory consumption, with internal testing showing up to a 50 percent cut in memory use during editing sessions.

The release officially adopts the C++20 language standard, allowing cleaner, modernised engine extensions and plug-in development. While this is mostly relevant for technical directors and engine programmers, it marks an important step toward modern C++ compliance across the toolchain.

Simulation and robotics workflows have also been refined. The ROS2 Gem, central to robotics and simulation integration, has been refactored to improve modularity and separate non-core components. This makes it easier for teams building simulation or automation pipelines to manage dependencies without compiling unnecessary subsystems.

Platform support continues to expand, with improved Vulkan handling and stronger Linux compatibility. Masked occlusion culling now works correctly under Linux, and the OpenXR Gem has been re-enabled, restoring virtual-reality and mixed-reality capabilities on that platform.

Behind the scenes, the build system has undergone a notable overhaul. O3DE’s automated review workflows have migrated from Jenkins to GitHub Actions, providing faster continuous-integration cycles and simplified caching. Build-target management has been restructured to improve consistency across Windows, Linux and macOS.

The modular improvements to simulation components and the ROS2 Gem will be useful for developers, as they simplify integration with external systems and reduce build complexity. Vulkan and Linux fixes strengthen O3DE’s cross-platform credentials, making it more viable for studios using Linux workstations or cloud build servers.

No new rendering systems or visual-effects features have been added in this release, however. The focus remains on stability, build-system efficiency and maintainability: vital for production, but less visible to artists.

Cautions Before Production Use

While O3DE 25.10 is a milestone release, it remains primarily an engineering update. Teams planning migration should note that earlier 25.05 release notes already flagged breaking changes in material-shader APIs and ray-tracing descriptors, now implemented in 25.10. Existing pipelines may require adjustments to remain compatible. As always with open-source engines under active development, studios are advised to test new builds extensively before deployment in production environments.

The post Open-Source Engine O3DE Hits Version 25.10 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Unity Technologies has released Unity 6.2, a mid-cycle update in the Unity 6 series, delivering a suite of integrated Unity AI tools directly within the Editor. This replaces the existing Muse and Sentis services with new Editor-native functions including Assistant, Generators, and the rebranded Inference Engine. Unity emphasises better integration, a broader selection of AI models, and updated pricing, although detailed pricing mechanics remain unconfirmed. Muse is now officially retired.

Unity 6.2 also introduces other features relevant to production artists, such as an automatic Mesh LOD system, updates to Shader Graph, improvements in rendering pipelines, enhancements to the 2D system, and refinements to the UI Toolkit.

Generative AI for assets—with vendor variation

The Generators feature centralises sprite, texture, material, sound, and animation generation workflows. It supports both Unity’s own AI models and third-party models from Scenario, Inc. and Layer AI, Inc., trained on foundations like Stable Diffusion and FLUX. Unity retains its proprietary model for generating tileable textures.

Assistant: an AI-powered Editor copilot

Assistant replaces Muse Chat, delivering a “project-aware” experience inside the Editor. It can answer documentation queries, batch rename assets, automate tasks, and write or run C# code. Assistant supports:

• /ask: documentation and project queries without modifying files
• /run: automates repetitive tasks, directly applying Editor changes
• /code: generates or reviews C# code snippets interacting with the Unity API

Local inference—Inference Engine replaces Sentis

The Inference Engine, formerly Sentis, offers local model execution within the Editor or at runtime. It supports various model formats and is intended to support future ML-Agents compatibility. Unlike the cloud-based AI, this component ensures local inference without data leaving the machine.

Data handling and user responsibility

By default, Unity does not use user data to train AI models. Developers may opt into sharing prompts and metadata via the Unity Dashboard—but Unity insists runtime applications or user-created media (like meshes or audio) are not used to train either Unity’s own models or third-party models.

Partner Model providers receive anonymised input—prompts, references, and other data—for processing but not to train their models. Unity shifts the legal risk to users:

“Unity users are ultimately responsible for ensuring that their use of Unity AI complies with our acceptable use principles” and that generated assets do not infringe on third-party rights.

Additional Unity 6.2 improvements

Beyond AI, Unity 6.2 includes updates such as support for Android SDK 36, improvements in XR development, and new diagnostic tools for performance monitoring and crash reporting. The Mesh LOD and revised UI Toolkit are also emphasised in Unity’s release notes.

Production implications

Unity 6.2 is now officially supported as a non-LTS (update) release and receives the same level of support as the Unity 6.0 LTS until the next release arrives. It’s intended for new or mid-cycle productions seeking the latest tools.

Summary for production artists

Unity 6.2 delivers tightly integrated generative AI tools within the Editor, replacing legacy services and giving artists multiple options to create assets and code. The local Inference Engine assures offline capabilities. However, asset ownership and IP clearance remain the developers’ burden. The release also adds practical improvements to LOD workflows, diagnostics, XR, and UI tools

The post Unity 6.2 Welcomes AI, But Pace Caution—User Liability on Copyright first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

A recent update to the open-source 3D graphics editor brings a game-changing feature: support for animated Gaussian splats. While this may sound like something out of a physics textbook, the new addition is poised to make a significant impact on game developers and real-time graphics enthusiasts. Let’s dive into what this means for the workflow and potential applications, straight from the source.

What Are Animated Gaussian Splats?

In simple terms, Gaussian splats are a method of applying splat-based rendering techniques in 3D graphics, often used to simulate soft particles or volumetric effects. By animating these splats, the editor now allows for more dynamic, lifelike rendering of such effects. This makes it ideal for real-time applications like games, simulations, or other interactive media. With this addition, the open-source tool expands its capabilities to support animated effects that respond fluidly to the scene, offering an enhanced level of realism in particle rendering.

https://twitter.com/willeastcott/status/1876589797931938126?mx=2

Real-Time Graphics Just Got a Boost

The most significant takeaway here is the ability to incorporate these animated Gaussian splats directly into real-time projects. Whether you’re simulating environmental effects such as smoke or adding complex particle effects to a game, the editor’s new support for animated Gaussian splats brings greater flexibility and realism to your pipeline. Given that real-time graphics demand efficiency and speed, this tool aims to streamline that process, allowing production artists to preview and tweak animations on the fly.

For more information, you can explore the editor’s capabilities here.

Pricing and Availability

As this is an open-source tool, it remains free to use. However, contributions are encouraged if you’re looking to support the project and its continued development.

---

The post Supersplat! Open-Source 3D Editor Adds Animated Gaussian Splats first appeared on DIGITAL PRODUCTION and was written by Bela Beier.