Ogre 1.12 released

by | May 1, 2019 | News

We just tagged the Ogre 1.12 release, making it the new current and recommended version. We would advise you to update wherever possible, to benefit from all the fixes and improvements that made their way into the new release.
This release represents 1 year of work from various contributors when compared to the previous 1.11 release. Compared to the last Ogre 1.11 release (1.11.5), however we are only talking about 4 months. Here you will mainly find bugfixes and the architectural changes that justify the version number bump.

For source code and precompiled SDKs, see the download page. Currently the Android is still missing. We will update the download page as it becomes available.

Changes

The 1.12 release focuses on preparing the codebase for future development instead of on new features. Some obsolete parts were removed and certain APIs adapted to be more generic. This is also reflected by the diff between v1.11.5..v1.12.0 as: 10994 insertions(+), 27142 deletions(-)

For an detailed overview of the changes see the New And Noteworthy Document. Among the highlights are:

  • #include directive supported for GLSL shaders
  • PF_DEPTH support for shadows with the RTSS and the Terrain component
  • RTSS 3.0: vastly improved internal API and refactored shader library
  • Per pixel-shading on D3D11/ GL3+/ GLES2 by default (via RTSS)
  • The GL3+ RenderSystem is now used for rendering the reference Test images
  • More precise timings for built-in profiler and support for external profiling via Remotery
  • unified API for fixed-function pipeline and shaders
  • NEON intrinsics for OptimizedMath on ARM (Android)
  • Stable Material library (Media/) that you can reference in your projects
  • the MSVC SDK now also includes the Python and Java components
  • support for loading 1.7 style terrains (aka “terrain.cfg”)

For an overview of the bugfixes, see the v1.11.6 changelog.

We continued removing the deprecated API with this release and together with the architectural improvements it means that your code might not compile any more. However we tried to keep API changes as non-invasive as possible.

We are keeping the time based release model for the 1.x branch. This means that you can expect OGRE 1.13 in April 2020.

Contributors

We would like to thank everyone who helped us make this release possible. The following list shows a list of contributors for 1.12 based on the git logs:

Pavel Rojtberg, Eugene Golushkov, Alex Choi, Dmytro Yunchyk, George Evmenov, SNiLD, Apivan, Rémi Verschelde, cread mefford, 1k0, Alex, Alexey Pavlov, Alon Faraj, Arthur Brainville, Bastien Bourineau, Edgar, Felipe Martínez, Felix Tschirschwitz, Gabriel Cuvillier, Gaudet Kevin, Grzegorz Szadkowski, Kevin Gaudet, LuChu, Mitja, Petr Ohlidal, Robin Norrman, Sonu Lohani, Stefan Roellin, Stoyanov Vlad, Tobias Schmidt, Xu Zhongxing, ulteq, wxyu247

Additionally you might have noticed that OGRE got a modern Logo. It has been contributed by Pierre Fontaine

Ogre 1.11.6

If you are currently deep in the development cycle using 1.11.5 and do not want any disruptions, I have good news for you: relevant bug-fix only commits were cherry-picked from master (1.12) to 1.11 and accumulated in the 1.11.6 release, which you can find here.