Dev snapshot: Godot 3.2 beta 6

By: Rémi Verschelde Jan 11, 2020

After a very busy week with many important bug fixes (plus a bunch of low risk enhancements and a lot of documentation updates), here's Godot 3.2 beta 6! As mentioned in the previous post, we're close to the Release Candidate stage and I hesitated to name this build as such. Since there were a number of big changes though I opted for making it another beta, and if all goes well testing it we should have a RC 1 in coming days.

Note: Illustration credits at the bottom of this page.

219 commits have been merged since 3.2 beta 5. This release is built from commit 0ab1726.

Disclaimer

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.

The features

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 beta build, see the list of commits.

Downloads

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 6.6.0.161 are included in this build.

IMPORTANT: Make backups of your Godot 3.1 projects before opening them in any 3.2 development build.

Bug reports

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 are not critical for the 3.2 release and will be 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.

In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in 3.1.x no longer works in 3.2 beta).


The illustration picture is from Sealed Bite, a delightful pixel art metroidvania by Securas with music by Wandard, which is the winning entry of the GitHub Game Off 2019! Check it out on http://itch.io, or play with the source files on GitHub. Be sure to follow Securas on Twitter, who is allegedly one of the most prolific and talented Godot jammers!