Skip to content
digital_developer
Game DevGodot EngineGodot 4.8Beta

Godot 4.8 beta 2 released with 144 fixes, feature-complete

Godot 4.8 beta 2 is out two weeks after beta 1, focused on regression fixes. The 4.8 feature set is considered complete, so testers are asked to check for remaining regressions.

Digital Developer Desk, 2h ago, 2 min read

Image: Godot Engine blog

Godot 4.8 beta 2 is available, two weeks after beta 1. The Godot Engine blog says the team has detected and resolved nearly 150 regressions in that time. Because 4.8 is considered feature-complete, the post is lighter than the dev snapshot posts. For an overview of what is new in 4.8, the post points readers to the beta 1 highlights.

According to the changelog, 59 contributors submitted 144 fixes. The build is made from commit cafc17a19. Downloads are offered for Linux, macOS and Windows, in Standard and .NET versions, along with export templates. The Web editor, the XR editor and the Android editor can also be tried. For the Android editor, testers need to request access to the testing group for pre-release builds.

Fixes called out in the post include a bezier track undo data problem in the animation editor after collapsing time with box scaling, and multiply blending that was too dark in the Compatibility renderer. The default curve range for particle angles changes to [-1, 1]. The Asset Store's default sorting returns to most relevant. Other listed items cover the editor evaluator in static functions, GDScript completion for for variables, touch event handling in BaseButton, and an improved error message for a Camera3D on an XR viewport.

On the build side, the minimum Python version in CI goes from 3.9 to 3.10, and third-party Unicode files are updated to version 18.0.0. The C# change enables Optimize for GodotSharp Debug builds. The .NET build requires .NET 10.0 or newer, which changes the minimum supported version from .NET 8 to 10.

The post describes beta 2 as pre-release software and recommends frequent backups or version control such as Git to guard against corruption or data loss. Testers are asked to report bugs on GitHub after checking existing issues, and regressions from earlier 4.x releases are described as especially important to report. A list of regressions and significant issues the team aims to address before the 4.8 release is available, and the post says it may be updated as more users test.

Sources

Get the daily brief

The five stories that matter, every weekday morning. Free.