If you’re tracking our repo you may have observed we renamed the v2-2-WIP branch into v2-2
What does this mean?
It means the branch is stabilizing. Back when it was v2-2-WIP, it was very unstable. Checking out that branch meant you could find crashes, memory leaks, missing or broken features; and the API interface was changing very quickly, thus updating the repository could mean your code would no longer compile and required adapting.
Over the last couple months, the API interfaces on 2.2 had begun to settle down, bugs were fixed and there were no apparent leaks. In fact some teams started already using it.
Now that it is no longer WIP, while there could still be API breakage on the 2.2 branch or accidental crashes/regressions, it shouldn’t be anything serious or that requires intensive porting.
We still have a few missing features (such as saving textures as DDS) but they’re not used frequently.
Coming up next
We still owe you a Progress Report of what’s been going on in 2.1 and 2.2 in the past year and a half; we have that written down but still needs a few reviews.
Coming up next is:
- More real time GI improvements
- VR performance optimizations
- We are planning on a Vulkan/D3D12 backend
Additionally we have a community member working on GPU-driven rendering and GPU particle FXs; while another community member just contributed Morph animations to 2.1
Yes, Morph animations are finally HW accelerated again! We are evaluating on porting this contribution to 2.2; it shouldn’t take long but we’re evaluating if it can be improved with the use of Compute Shaders
What about Ogre 2.1?
If someone wants to teach Matias aka dark_sylinc a quick automated way to create installer SDKs, that is welcomed! (he never liked handling that!!!)
Ogre 2.1 has been very stable. Eugene ported several improvements from the 1.x branch; and we currently are dealing with a regression that caused due to how PF_BYTE_LA / PF_L8 format is treated in D3D11, but other than that 2.1 is ready for release.
The morph animation contribution is brand new so that may need a bit more testing.
If you don’t see an SDK that is mostly due to time and knowledge to package an SDK.
If someone else wants to step in and maintain packaging, that is welcomed!
Further discussion in the Forum Post