Godot 4.7 RC2 Drops With Critical Fixes Before Stable Release
The second release candidate for Godot 4.7 just landed, and it is exactly what developers need before the final stable build ships. This snapshot targets a handful of show-stopping regressions that surfaced during the first RC cycle, giving engine testers one last chance to catch crashes or broken workflows. If nothing major breaks in this window, the official Godot 4.7 release is practically around the corner.
What Changed Since RC1
The update log reads like a standard post-RC cleanup pass, which means the core engine finally stopped introducing new bugs while chasing polish. Most of the changes focus on stabilizing existing systems rather than adding flashy features. A deadlock in WorkerThreadPool got patched, which matters because multithreaded projects would otherwise freeze during heavy scene loads or physics calculations. The message queue also stops flushing prematurely before a MainLoop iteration completes, preventing weird input lag and dropped events that have plagued early 4.x builds.
Editor and Buildsystem Stability
GUI hiccups in the editor got sorted out with a fix for SceneTreeEditor drop operations, so dragging nodes around will no longer trigger silent failures or corrupted references. The build system finally handles debug_tag_stack.pop() without throwing IndexErrors when new error messages appear, which saves hours of frustration during compilation runs. MSYS2 environments also get proper download script adjustments, meaning Windows developers using that toolchain can actually compile the engine without chasing broken dependencies.
Animation and Rendering Tweaks
AnimationTree now includes a null check for root_animation_node, which prevents crashes when loading projects with missing or renamed animation states. The 2D tilemap system finally randomizes its first tile correctly instead of skipping it entirely, a small fix that saves artists from manually overriding default placements in every new level. Documentation links got updated to point at the Multiple Windows demo project, and experimental flags on DrawableTexture2D methods now use generic descriptions so developers stop guessing which features are actually safe to touch.
Testing Godot 4.7 RC2 Before Stable Release
Grabbing this snapshot makes sense if the first candidate broke your project or caused editor crashes during routine tasks. The engine team treats these release candidates as final stress tests, so any critical regression found now directly delays the stable build. Projects that already run smoothly on RC1 can probably skip this update unless they rely on tilemap randomization or complex animation trees. Waiting for the official 4.7 release remains the safest route for production pipelines, but hobbyists and indie teams looking to preview the next major version should grab this snapshot and report any remaining issues before the window closes.
Release candidate: Godot 4.7 RC 2 – Godot Engine
The end is in sight… Race ya there!
Keep your test projects backed up, run through your usual export workflows, and drop any crashes into the issue tracker while the team is still actively patching. The stable build will be here soon enough, but catching these last few kinks now saves everyone a lot of headache later. Happy debugging.
