This page has my custom binaries for Godot Engine with the selection of modules I use and develop on. All binaries have been built with the official dockers, except for Windows which were built with MSVC.
These binaries allow you to use these modules without compiling the engine yourself.
Below the downloads, you’ll also find my voxel demo and tutorials for use with these binaries.
- Voxel Tools for infinitely paged blocky and smooth voxel terrains.
- FastNoise wrapper for the FastNoise library. There is a PR to eventually merge this module into Godot.
- FastNoiseSIMD wrapper for the FastNoiseSIMD library. This module will not be merged into Godot.
- VoxelGeneratorFastNoiseSIMD for Voxel Tools that takes advantage of FastNoiseSIMD.
Click a version to expand the section.
>> Version 3.2.2rc – March, 2020
- Only Windows and Linux have been tested. Let me know if the other builds or export templates work or not.
- Win32 + mono does not work on Windows/64. (need to test this with new msvc build)
- Mono + IOS is not currently supported by Godot.
- Voxel Tools does not work on HTML5 (due to lack of threading support).
- FastNoiseSIMD does not work with: HTML5, Android x86/x86-64 (ARM7/8 OK). IOS does not build with the NEON instruction set. It’s unknown if it works with any of the other SIMD levels. Compare against regular FastNoise and see if it’s any faster, or call get_simd_level() and see if you get a number higher than 0 back.
>> Version: 3.2 Alpha – November, 2019
|3.2 alpha 4569f5ec8|
|3.2 Mono/C#||alpha 4569f5ec8|
- *Voxel Tools doesn’t work with HTML5.
- **Win32 + mono does not work with Win64.
To use these binaries to make voxel games, I suggest you follow these steps:
- Download the newest appropriate binary above.
- Download my demo. If you are using the old binaries from November, you must use this specific version.
- Watch the tutorial video below.
- Read through the written documentation.
- Review the troubleshooting section below.
How To Use Voxel Tools
Godot has reached the end of the scene file
This occurs because the build of Godot you are using does not recognize the objects named in the scene file. The .tscn is just a text file, so you can open it in notepad.
If you open a VoxelTools scene in a regular build of Godot you’ll get this error because Godot doesn’t recognize the “VoxelTerrain” or “VoxelLodTerrain” classes.
You might be using the old binaries with the new demo, and classes have been renamed. You can try manually renaming the classes in the text file. In Godot, press SHIFT+F1 for help and you can search for class names built into that binary.
For instance, at one point the class VoxelStreamNoise was renamed to VoxelGeneratorNoise. The scene file wouldn’t open, but by manually changing it in notepad, we were able to open the file.
I don’t see any voxels
This is almost always because of a mismatch of settings. Work has been done to eliminate or at least warn when settings won’t produce any results.
For blocky, you need a Voxel Library. Your stream needs to be set to a channel of TYPE.
For smooth voxels, your channel must be set to SDF.
If you haven’t done so already then watch the tutorial video above which shows you exactly how to use it. Also, review the written documentation.
Zylann’s demos are generally out of date, so avoid those.
If there’s another issue you’re having with Voxel Tools specifically, you can open an issue. If the issue is with one of the FastNoise modules, or my demo, open issues on those specific repositories.
You can also leave a comment below, especially if it’s about these binaries and whether they work or not. I’d like to know.