These are maintenance releases. Little effort should be spent porting to these newer versions.
Most of the work aimed at improving Vulkan RenderSystem stability and compatibility.
For a full list of changes see the Github release
Source and SDK is in the download page.
Discussion in forum thread.
Ogre 13.4.0 was just released. This release contains some significant bug-fixes and feature additions, which we will discuss in more detail below. We recommend all users of the 13.x branch to update.
For a full overview of the changes, see the changelog.
with blender 2.8+ and blender2ogre 0.8.3, you can now choose to export PBR metal-roughness parameters instead of converting them to a FFP approximation as before.
While at it, several bugs in the RTSS PBR implementation were fixed. Now transparency, ambient lighting and PSSM shadows play nicely with PBR.
In the User Survey btogre was the most popular external Ogre component with over 53% votes.
To make life for those who use it easier, it is now integrated into the main repo as a component. This allows you to just build it as part of Ogre on one hand and on the other hand this ensures that it is integration tested by our CI.
Ogre now supports normalized INT_10_10_10_2 as the vertex format. This packs 3 signed values with 10bit precision and a fourth 2bit value into 4 bytes – the size required by a single float.
If you are using normal-maps, you will notice how this format is perfect to store a tangent with parity, while only requiring 25% of storage compared to 4 floats.
Additionally, you can use it to store normals where storage requirements drop to 33% too.
In both cases the 10bit resolution is typically sufficient.
The format is natively supported by GLES3, GL3+, Vulkan and Metal meaning that you also save bandwidth and VRAM.
With the other RenderSystems, Ogre will transparently unpack the data to float at mesh load time, so you at least can benefit from smaller mesh files.
E.g. a 76 MB mesh can be reduced to 50 MB, when using packed normals and tangents.
To update your meshes, OgreMeshUpgrader gained the option -pack, to be used like:
OgreMeshUpgrader -pack your.meshIn other news Bites Input now not only handles Gamepads but generic Joysticks and Ogre can be used online through Google Colab.
During the period of Jan 10. – February 10. we received 54 replies. At the same time the ogre 13.2.4 Windows SDK alone was downloaded 2188 times. So while the results are insightful, they are probably not representative.
When it comes to RenderSystems, we finally see a significant drop for the legacy systems (D3D9, GL). This will allow us to focus on new features only supported on modern APIs. However, I doubt the numbers for Vulkan, given how recent the Vulkan addition was.
The most relevant result for further development is likely the question of target audience. Here, we see an increase of the enthusiast portion at the cost of the Enterprise one. I take it as we can sacrifice some API stability to gain modern rendering techniques when moving forward.
The following one is also interesting, as the HLMS was dropped with Ogre 13 and the inclusion in the poll is a copy/ paste error. I guess that any component with less than 18 votes is not actually used, but people were merely ticking every option.
As always statistics are lies though, so better take a look at the actual numbers yourself.
Following the #MeanTweets idea I also wrote some short replies to the criticism, that you can read below:
(more…)Ogre 13.3.0 was just released. This release contains some significant feature additions, which we will discuss in more detail below.
For a full overview of the changes, see the changelog.
The most significant addition is probably built-in PBR support via the RTSS.
To enable the PBR pipeline via material scripts, specify
rtshader_system
{
lighting_stage metal_roughness texture Default_metalRoughness.jpg
}The parameters are expected to be in the green and blue channels (as per glTF2.0) and lighting will be done according to the Filament equations.
Alternatively, you can use material-wide settings, by omitting the texture part like:
rtshader_system
{
lighting_stage metal_roughness
}Here, metalness is read from specular[0] and roughness from specular[1].
Furthermore, the Assimp Plugin will automatically use the PBR pipeline, if it encounters any PBR maps. This in turn allows correctly loading and displaying glTF2 meshes – as shown in the ogre-meshviewer screenshot above.
The Gamepad Support in OgreBites (via SDL2) has been improved. Now the according events are correctly delegated to ImGui, so you can control the UI with your gamepad.
Also additional gamepad mappings can be specified by placing a gamecontroller.t<a href="http://wiki.libsdl.org/SDL_GameControllerAddMappingsFromFile">xt</a> in the working directory.
Those of you who have been around Ogre for some time might remember that back in 2020, we conducted a survey about our user base. The results of which can be found here.
For the Ogre 13 development cycle we would like to assess to correctly emphasize the development on the most used features.
So for the next four weeks until the 10th of February, you have the chance to participate and help us to get an impression about our user base, how Ogre is used and share some wishes for the future. Simply follow the link and make your way through the 14 questions. It should not take up much time since most of the questions are simple checkbox or radio button questions.
We want to thank you all upfront for helping us to develop Ogre further and getting some valuable insight information about the people using the engine!
PS: We would be glad if you could spread the word about the survey via all available channels to all potential Ogre users, because: The more participants, the more accurate are the results of course.
As we mentioned last time, Ogre-Next 2.4 will be mostly focusing on maintenance and fixing code debt.
Over a week we’ve fixed a lot of warnings.
With default settings on Clang on Linux, there’s no errors (except on OgreMeshTool).
But we haven’t taken a look at deprecated warnings yet.
On Apple/XCode and MSVC there’s very few warnings now
GCC needs Wconversion off because it’s incredibly dumb. It’s got too many false positives.
Fixing them would hurt readability too much, causing more harm than good.
Some CMake settings may cause warnings, e.g. we generate lots of warnings if OGRE_CONFIG_DOUBLE is on.
We also applied clang format to everything, and added C++11 override everywhere.
We’ve also removed dead code and added an option to turn off custom memory allocators off which is the default.
We’ve removed Boost, thus CMake won’t waste its time (and that was a lot) looking for an optional dependency we didn’t really need anymore.
Overall in Debug builds we’re seeing a 20% reduction in binary size (incl. symbols)!!
While Release builds have between 1% and 3% reductions.
The only drawback is that merging code 2.3 -> 2.4 is now harder as it’s almost guaranteed to cause a merge conflict, since nearly every line got touched.
Nonetheless it seems that merging by “merge using always theirs”, then applying clang format, then seeing the diff of what’s going to be merge is a good approach to prevent bad merges and fix accidentally introducing bugs
The numbers are in MBs
|
Lib Name |
Before (2.3) |
After (2.4) |
Diff |
|
libOgreHlmsPbs_d.so |
8,69 |
7,53 |
-15,48 % |
|
libOgreHlmsUnlit_d.so |
1,92 |
1,59 |
-20,48 % |
|
libOgreMain_d.so |
65,00 |
55,01 |
-18,17 % |
|
libOgreMeshLodGenerator_d.so |
4,27 |
3,71 |
-15,11 % |
|
libOgreOverlay_d.so |
3,87 |
3,30 |
-17,23 % |
|
libOgreSamplesCommon_d.a |
10,80 |
9,10 |
-18,64 % |
|
libOgreSceneFormat_d.so |
2,55 |
2,03 |
-25,44 % |
|
Plugin_ParticleFX_d.so |
1,79 |
1,63 |
-9,85 % |
|
RenderSystem_GL3Plus_d.so |
6,97 |
5,23 |
-33,25 % |
|
RenderSystem_NULL_d.so |
1,70 |
1,35 |
-25,87 % |
|
RenderSystem_Vulkan_d.so |
15,82 |
14,63 |
-8,18 % |
|
|
|
|
|
|
Total |
123,39 |
105,12 |
-17,39 % |
|
Lib Name |
Before (2.3) |
After (2.4) |
Diff |
|
libOgreHlmsPbs.so |
0,80 |
0,78 |
-3,03 % |
|
libOgreHlmsUnlit.so |
0,19 |
0,19 |
-3,58 % |
|
libOgreMain.so |
7,31 |
6,93 |
-5,61 % |
|
libOgreMeshLodGenerator.so |
0,24 |
0,22 |
-5,21 % |
|
libOgreOverlay.so |
1,00 |
1,00 |
-0,14 % |
|
libOgreSamplesCommon.a |
0,43 |
0,41 |
-3,85 % |
|
libOgreSceneFormat.so |
0,23 |
0,23 |
0,95 % |
|
Plugin_ParticleFX.so |
0,25 |
0,24 |
-5,38 % |
|
RenderSystem_GL3Plus.so |
0,85 |
0,76 |
-11,86 % |
|
RenderSystem_NULL.so |
0,16 |
0,16 |
-0,94 % |
|
RenderSystem_Vulkan.so |
7,93 |
7,91 |
-0,22 % |
|
|
|
|
|
|
Total |
19,40 |
18,83 |
-3,02 % |
|
Lib Name |
Before (2.3) |
After (2.4) |
Diff |
|
OgreHlmsPbs_d.dll |
1,89 |
1,82 |
-3,45 % |
|
OgreHlmsPbs_d.pdb |
15,53 |
12,82 |
-21,15 % |
|
OgreHlmsUnlit_d.dll |
0,47 |
0,45 |
-4,50 % |
|
OgreHlmsUnlit_d.pdb |
9,51 |
6,89 |
-37,96 % |
|
OgreMain_d.dll |
24,28 |
22,81 |
-6,45 % |
|
OgreMain_d.pdb |
101,56 |
81,94 |
-23,94 % |
|
OgreMeshLodGenerator_d.dll |
1,02 |
0,98 |
-4,90 % |
|
OgreMeshLodGenerator_d.pdb |
10,57 |
8,64 |
-22,34 % |
|
OgreMeshTool_d.pdb |
11,95 |
8,66 |
-37,98 % |
|
OgreOverlay_d.dll |
1,77 |
1,75 |
-1,45 % |
|
OgreOverlay_d.pdb |
13,28 |
9,50 |
-39,70 % |
|
OgreSceneFormat_d.dll |
0,58 |
0,57 |
-1,78 % |
|
OgreSceneFormat_d.pdb |
11,07 |
8,04 |
-37,82 % |
|
Plugin_ParticleFX_d.dll |
0,39 |
0,37 |
-5,59 % |
|
Plugin_ParticleFX_d.pdb |
6,18 |
5,12 |
-20,59 % |
|
RenderSystem_Direct3D11_d.dll |
2,02 |
1,90 |
-6,32 % |
|
RenderSystem_Direct3D11_d.pdb |
17,13 |
14,11 |
-21,37 % |
|
RenderSystem_GL3Plus_d.dll |
2,00 |
1,69 |
-18,41 % |
|
RenderSystem_GL3Plus_d.pdb |
16,17 |
12,25 |
-32,03 % |
|
RenderSystem_NULL_d.dll |
0,39 |
0,36 |
-8,09 % |
|
RenderSystem_NULL_d.pdb |
8,96 |
6,26 |
-43,04 % |
|
RenderSystem_Vulkan_d.dll |
17,69 |
17,58 |
-0,66 % |
|
RenderSystem_Vulkan_d.pdb |
104,54 |
87,89 |
-18,94 % |
|
OgreSamplesCommon_d.lib |
12,83 |
11,63 |
-10,28 % |
|
OgreSamplesCommon_d.pdb |
7,74 |
6,78 |
-14,18 % |
|
|
|
|
|
|
Total |
399,51 |
330,81 |
-20,77 % |
|
Lib Name |
Before (2.3) |
After (2.4) |
Diff |
|
OgreHlmsPbs.dll |
0,55 |
0,55 |
0,09 % |
|
OgreHlmsUnlit.dll |
0,14 |
0,13 |
-1,45 % |
|
OgreMain.dll |
6,91 |
6,82 |
-1,32 % |
|
OgreMeshLodGenerator.dll |
0,20 |
0,21 |
2,12 % |
|
OgreOverlay.dll |
0,71 |
0,71 |
-0,28 % |
|
OgreSceneFormat.dll |
0,17 |
0,17 |
0,00 % |
|
Plugin_ParticleFX.dll |
0,14 |
0,14 |
0,35 % |
|
RenderSystem_Direct3D11.dll |
0,52 |
0,51 |
-0,38 % |
|
RenderSystem_GL3Plus.dll |
0,59 |
0,54 |
-9,37 % |
|
RenderSystem_NULL.dll |
0,12 |
0,12 |
-2,54 % |
|
RenderSystem_Vulkan.dll |
3,81 |
3,80 |
-0,18 % |
|
OgreSamplesCommon.lib |
1,48 |
1,41 |
-4,72 % |
|
|
|
|
|
|
Total |
15,33 |
15,11 |
-1,44 % |
That’s all for now. Ogre 2.3 was released just a week ago and we wanted to share such an exciting development already happening on 2.4.
Discussion in forum thread.