This is it.
Crimild v4.10.0 is out and this will be the last of the 4.x versions. From now on I’ll be focused on the next major release for Crimild which will bring a lot of changes.
But first let’s talk about what’s included in v4.10.0:
There are many nodes included in this release and many more will come in future versions.
Although shader graphs were actually introduced in v4.9, I ended up refactoring them to work in a similar way as render graphs do, simplifying both the internal implementation as well as the API.
Now, each node in the graph represents either a variable or an expression, and there’s also a way to discard nodes that are not relevant to the end result.
The translation to GLSL mechanism has also being simplified, but I guess it could received a little more love in the future.
Most importantly, this newer API allowed me to create…
Crimild Shading Language
Well, it’s not an actual programming language, but more of a set of functions providing us a way to write shaders in plain C++, disregarding the actual graphics API using for rendering.
Of all the new features includes in v4.10.0, this is the one that got me more excited and I’m really looking forward to start creating shaders this way.
UI Canvas & Layout
Last but not least, I started working on several tools for creating UI elements, either in screen or world space. As it is right now, only basic UI elements can be created but there’s support for a very expressive set of layout constraints to arrange them in a canvas, with a size defined independently of the actual screen resolution and aspect ratio.
Minor fixes and updates
As usual, new releases come with a bunch of fixes and minor updates to existing features and v4.10.0 is not the exception.
There are a couple of new containers: Digraph and Set.
In addition, many changes have been made to how render resources are internally handled.
And I finally fixed some math bugs that have been causing issues for quite some time.
Please refer to the complete release notes on Github.
Crimild v4.10.0 includes a lot of (experimental) features that are going to became critical players in v5, Crimild’s next major release.
The biggest goal for next year will be to refactor the entire rendering system, which has become quite limited and it’s time for it to level up. I’ll be focusing first on improving the existing OpenGL renderer before moving to Vulkan. Not sure what will happen with Metal support, though.
Indeed, next year is going to be very exciting…