Can you check if this issue is still present when running the latest Ember from master? It now uses Ogre 1.7 which perhaps have rectified this behavior.
Can you check if this issue is still present when running the latest Ember from master? It now uses Ogre 1.7 which perhaps have rectified this behavior.