During the period of Feb 7. – March 7. we received 117 replies. At the same time the ogre 1.10 Windows SDK alone was downloaded 5161 times. So while the results are significant, they are probably not representative.

The average Ogre application is a Game displaying Overlays and Particles. It was written as a Hobby in C++ and targets Windows 10 using OpenGL.

As you see statistics are lies, so better take a look at the actual numbers yourself.

To spare you reading all the free-form answers though, here is a summary

Most severe drawbacks of Ogre 1.10

  • lack of documentation (8x)
  • Difficult to build/ setup (6x)
  • code quality/ readability (5x)
  • outdated documentation (4x)
  • Performance (4x)
  • Compositor Component (2x)
  • no/ bad scene editor (2x)
  • diverging 1.x and 2.x branches (2x)
  • lack of art/ asset pipeline (2x)
  • Abandoned Plugins (2x)
  • “next-gen” graphics (1x)

Most important future change for Ogre 1.11

  • modern rendering techniques (8x)
  • Keeping code stable (7x)
  • Archive out of date documentation (2x)
  • more support for existing Addons/ Plugins (2x)
  • simplify SCM (2x)
  • C++11 Support (2x)
  • VR & Stereo Rendering (1x)

 

As you can see some of the requests are contradicting and some are only vague, like “next-gen graphics”.

To others I wrote a short reply here.

To streamline the development process & discussion of Ogre 1.x, we now have theĀ Ogre evolution proposals.
Basically it consists of a structured textual specification similar to the Python PEPs. Click on the link above to learn more.