I just missed tagging Alpha 4 by the end of June, which would've continued the 6 monthly release cycle that I'd organically fallen into. This was largely because I've been pushing some final bug fixes into the release to make it so much better!
And what a release it is, a total of 51 merge requests were merged this cycle! Let's see what they bring!
Skeletal animation has been a glaring missing feature in Simulant for years, but now it's here and ready to go! The first skeletal mesh file format that Simulant supports is Milkshape 3D, but in the next few releases I plan to bring more new formats into the mix.
Mesh objects that support skeletal animation support both pre-defined animations through the existing KeyFrameAnimated interface, and also manual joint manipulation through the new skeleton API.
Previously there was a poorly implemented flag for disabling culling of actors. Now, you can disable all spatial culling of any stage node by setting its
is_cullable property. This is useful for debugging, or if you know that a node will always be visible it can lead to small performance improvements.
StageNode pooling was rewritten for Alpha 3, but the resulting code had some deficiencies, particularly around iteration and insertion performance. The next iteration of that pooling has arrived in Alpha 4, bringing huge speed improvements.
When loading heightmap meshes from texture data, Simulant has always provided information about the way the heightmap was generated via the stored
TerrainData has gained utility functions to get the exact height at a world coordinate, and to give you the triangle indexes at a world coordinate. These are super useful for placing things on your terrain, or performing ray-intersections.
Additionally, you can now pass a
new_mesh_from_heightmap instead of a file which is great if you're generating the heightmap procedurally.
Simulant now has a basic implementation of Coroutines, and all mutexes throughout the codebase have been removed. Not only do Coroutines provide a simpler model of concurrency, and reduced complexity of the entire codebase, but they've improved performance.
None of the Simulant API is now threadsafe, and Coroutines should be used for all concurrency.
Although Simulant isn't threadsafe, that doesn't mean you won't need threads at all. Simulant now provides a consistent and clean threading API for all platforms for you to use in your own code. This is an alternative to C++'s std::thread which has spotty (or non-existent) implementations on older compilers.
Too many to mention, but here are the hightlights
... and many many more!
Special thanks go to Charlotte Koch and David Reichelt for their contributions this cycle!