For those who don’t know the tool: The open-source Godot Engine is a cross-platform game engine widely used for interactive 2D and 3D content creation. Godot 4.6 is shifting focus toward workflow polish, production-ready defaults and deeper rendering and tool enhancements.

Rendering under the hood

Godot Engine 4.6 continues the Vulkan-based renderer introduced in the 4.x series, but most changes in this release target correctness, predictability and tunability rather than new visual effects. The most visible change is a full rewrite of Screen Space Reflections. The new implementation reduces temporal instability and artefacts at grazing angles, with explicit half-resolution and full-resolution modes. The latter is computationally expensive but provides cleaner reflections for high-end realtime visuals and virtual production style scenes.

Reflection probes gain octahedral encoding support, lowering memory usage while preserving angular resolution. This is relevant for large environments with many probes, where cube map memory pressure was previously a limiting factor. Glow is now composited before tonemapping rather than after, resulting in more physically consistent highlights when working in HDR pipelines.

Tonemapping itself is more configurable, with parameters exposed for artists and TDs who need predictable output across displays. Material debanding has been improved to reduce banding in low-gradient areas, particularly noticeable in sky domes and volumetric-style lighting setups.

On Windows, Direct3D 12 becomes the default rendering backend. Vulkan remains supported, but the switch acknowledges ongoing driver instability on certain consumer GPUs. This is a pragmatic rather than ideological decision, and it may matter for studios deploying on heterogeneous hardware.

Physics as an engineering choice

Godot Engine 4.6 makes Jolt the default 3D physics engine for new projects. Jolt is a third-party rigid body solver designed for determinism and stability, and it has been available as an option in earlier versions. Making it the default is a statement that Godot’s in-house 3D physics is no longer considered production-ready for complex scenes.

This change affects collision behaviour, stacking stability and joint simulation. Existing projects are not automatically migrated, and the release notes explicitly warn that results will differ. The engine does not claim bit-exact determinism across platforms, but behaviour is reported as more consistent under load. This is a technical foundation change, not a feature, and it will mostly be noticed when things stop exploding.

Animation systems restored and expanded

Inverse Kinematics returns in Godot Engine 4.6 after being absent in early 4.x releases. The new system is modular, node-based and supports multiple solvers including TwoBoneIK3D and FABRIK3D. These are not cosmetic tools but structural animation constraints that can be evaluated deterministically or iteratively depending on setup.

The animation editor gains direct timeline retiming by resizing clips and keys, reducing the need for script-side adjustments. Node-based constraints can now be targeted more flexibly, which is relevant for procedural rigs and runtime animation blending. While Godot is still not a replacement for DCC rigging tools, the direction is clear. Animation in Godot is expected to survive iteration, not just previews.

Editor architecture and debugging

The new Modern editor theme is the most visible change, but the more relevant shift is architectural. Docking is now unified and panels can float freely across monitors. This matters for technical users who rely on debugger, shader editor and scene views simultaneously. Debugging gains ObjectDB snapshots and diffing. This allows developers to capture the state of live objects and compare them over time, which is useful for tracking memory leaks, orphaned nodes and unintended object growth. Errors in the Output panel now link directly to scripts or resources, including when using external editors. Select and Transform modes are decoupled in the viewport, aligning Godot more closely with established DCC interaction models. This is a small change with large ergonomic impact.

Embedding and deployment

LibGodot is introduced as a supported way to embed the engine into other applications. This allows Godot to run as a library rather than a standalone editor or player. The release notes are cautious about scope, but this opens the door to custom tools, simulation hosts and non-game realtime applications. Export workflows gain patch PCK delta encoding, reducing update sizes for deployed projects. GPU-accelerated 3D texture imports shorten iteration times when working with volumetric or layered textures.

What this release is really about

Godot Engine 4.6 is not a showcase release. It does not promise cinematic visuals or revolutionary workflows. Instead, it concentrates on technical debt, defaults and systems that must be correct before higher-level tools can be trusted. Many changes are invisible unless something goes wrong, which is precisely the point.

As always, new tools and engine versions should be tested carefully before being introduced into active production environments.

Official Godot Engine 4.6 release notes
https://godotengine.org/releases/4.6/

The post Godot 4.6 Arrives With Major CG-Friendly Updates 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.

Epic Games has officially released Unreal Engine 5.7. The update expands major systems across rendering, procedural content, materials, animation, and virtual production. It also introduces an in-Editor AI Assistant. Several features, including the Nanite Foliage rendering system, remain Experimental, while others, most notably the PCG framework and Substrate materials, are now designated production-ready. If you think “Didn’t you tell me all of this already?”: We had a Preview-News for the Preview and Teasers.

Procedural Content Generation (PCG) ready for production

Epic now considers the PCG framework suitable for use in final projects. The system allows artists to populate large environments procedurally, introduce variety, and automate level construction. Unreal Engine 5.7 adds a dedicated PCG Editor Mode, performance optimisations for GPU compute tasks, and a Procedural Vegetation Editor (PVE) for foliage placement. While PCG itself is stable, the PVE remains Experimental. Epic recommends verifying runtime performance and scalability before adoption in production environments.

Nanite Foliage enters testing

Nanite Foliage introduces a new geometry rendering pipeline for dense, animated vegetation in open-world environments. It combines Nanite Assemblies, Nanite Skinning, and Nanite Voxels to balance geometric detail with runtime efficiency. Epic lists the entire system as Experimental. Studios considering it for production should expect incomplete support for physics, collisions, and wind animation, and should validate performance on target hardware.

Substrate materials: modular and physically accurate

The Substrate framework for modular material authoring and rendering has graduated to production-ready status. It enables layering of physically accurate material types such as clear coat, metal, cloth, and skin, producing more realistic composite surfaces.

For material and look-dev teams, Substrate now replaces earlier shading models in complex asset pipelines. Epic recommends migrating projects incrementally and benchmarking shaders to ensure compatibility and consistency across devices.

Animation and virtual-production improvements

Unreal Engine 5.7 extends its animation toolkit with an overhauled Animation Mode, improved IK Retargeter and Skeletal Editor, and a new Dependency View for visualising control hierarchies.

For virtual-production users, the engine adds a Live Link Broadcast Component, allowing Unreal itself to act as a live animation source on-set. Composure, Unreal’s integrated real-time compositor, has been upgraded for improved handling of shadows, reflections, and colour accuracy during LED volume shoots. Incremental Cooking enters Beta, promising faster asset iteration for large virtual-production projects, though Epic cautions against immediate production use.

AI Assistant built into the Editor

A new AI Assistant now lives directly within the Unreal Editor. Users can ask technical questions, request code snippets in C++, or receive step-by-step instructions without leaving the viewport. The tool is designed to reduce context switching but is not intended to replace documentation or verified workflows. Its long-term reliability in multi-user pipelines remains untested, and Epic has not disclosed details about data handling or privacy.

Extended MetaHuman and cross-platform updates

The MetaHuman Creator plugin now runs on Linux and macOS, expanding platform support beyond Windows. Additional scripting APIs enhance automation and integration for character pipelines.

Here’s more about the Hairstyle generator.

Rendering, audio, and mobile improvements

Rendering updates include support for Android 15, new “Geometry Inspection” viewport modes for surface analysis, and expanded anti-aliasing and shadowing options. Nanite continues to gain broader coverage across rendering passes. Audio workflows benefit from “Audio Insights” (Beta), enhanced subtitle support, and updates to the waveform editor. These features target real-time review and iteration efficiency rather than final mixdown.

Caveats and production considerations

Despite multiple “production-ready” designations, Epic’s documentation lists numerous features as Beta or Experimental. Nanite Foliage, the Procedural Vegetation Editor, and MegaLights are explicitly unfinished. Documentation for several systems remains incomplete, and large projects upgrading from earlier versions will require shader recompilation and plugin verification. Studios are advised to test workflows in parallel, evaluate GPU and CPU loads, and confirm asset compatibility before upgrading live projects.

The post Unreal Engine 5.7: foliage, PCG and in-Editor AI first appeared on DIGITAL PRODUCTION and was written by Bela Beier.