After three well-tested and quite stable alpha builds, we’re now ready to enter the beta stage for the upcoming Godot 3.2 release.
The beta stage corresponds for us to a release freeze, as announced today on GitHub, which means that we will only consider critical bug fixes for merging in the master branch, and that until Godot 3.2 is released. This way, we can focus on making the 3.2 release as stable as possible with continuously increasing the scope of its new features.
Note: Illustration credits at the bottom of this page.
IMPORTANT: This is a beta build, which means that it is not suitable for use in production, nor for press reviews of what Godot 3.2 would be on its release.
There will still be various fixes made before the final release, and we will need your detailed bug reports to debug issues and fix them.
Release notes are not written yet, but you can refer to the detailed changelog that our contributor Hugo Locurcio is maintaining.
Our past devblogs should also give you an idea of the main highlights of the upcoming release. Note that the Vulkan port outlined in Juan’s latest posts is developed in a separate branch for Godot 4.0, and is not included in this release.
Documentation writers are hard at work to catch up with the new features, and the latest branch should already include details on many of the new 3.2 features.
For changes since the last alpha build, see the list of commits.
The download links are not featured on the Download page for now to avoid confusion for new users. Instead, browse one of our download repository and fetch the editor binary that matches your platform:
- Classical build (GDScript, GDNative, VisualScript).
- Mono build (C# support + all the above). You need to have MSbuild installed to use the Mono build. Relevant parts of Mono 188.8.131.52 are included in this build.
IMPORTANT: Make backups of your Godot 3.1 projects before opening them in any 3.2 development build.
- Due to some build issues beta1 does not have export templates for the UWP platform. This will be fixed in later builds.
There are still hundreds of open bug reports for the 3.2 milestone, which means that we are aware of many bugs already. Yet, many of those issues may not be critical for the 3.2 release, and now that we reached the release freeze, they will be reviewed again and some pushed back to later milestones.
As a tester, you are encouraged to open bug reports if you experience issues with 3.2 beta. Please check first the existing issues, using the search function with relevant keywords, to ensure that the bug you experience is not known already.
The illustration picture is from the gorgeous procedural arcade shooter Infinistate, developed by James Redmond (Fracteed). Fracteed is an early adopter of Godot 3.0’s new PBR pipeline, and helped a lot testing and improving it with his impressive artwork. Follow Infinistate’s development on Twitter and stay tuned for a possible Early Access release next year!