openmw.org

A new scripting language is probably a long way off We are not planning to have a new scripting language everl. The current one is fine. Most of the modding community has lots of practical experience with it. Yes, it has a few quirks, but they are fixable. For some value of "fine" IMHO it...

Got a random crash while walking around in the Seyda Neen area: openmw: /home/marc/Tools/ogre-1-7-1/OgreMain/src/OgreRenderQueueSortingGrouping.cpp:386: void Ogre::QueuedRenderableCollection::addRenderable(Ogre::Pass*, Ogre::Renderable*): Assertion `retPair.second && "Error inserting n...

Zini wrote:Nope. The iterator is incremented before erase is called. All good.

I was like what? No. And then I double checked where the sequence point is. That is really really subtle.

Zini wrote:We are planning to update to 1.8 a while after 1.8 comes out of RC status. Probably during 0.13.0 or 0.14.0.

Isn't it just a couple of IFDEFs that are needed? Or are the bigger problems than renaming msSingleton

The issue is that OpenMW is not compatible with Ogre 1.8

All you need to do is to use Ogre 1.7.3. If you don't have a copy on your machine (downgrade will show you them) then look at the ARM: http://arm.konnichi.com/search/

Zini wrote:Honestly can't see the point of code names.

They make new users more confused about what version they are running as you can't meaningfully order them?

Probably worth rendering things like containers at batched geometry. I think it is possible to move statics so whatever we do at some point we are going to have to write something to remove an object from batched geometry.

Got a random crash while walking around in the Seyda Neen area: openmw: /home/marc/Tools/ogre-1-7-1/OgreMain/src/OgreRenderQueueSortingGrouping.cpp:386: void Ogre::QueuedRenderableCollection::addRenderable(Ogre::Pass*, Ogre::Renderable*): Assertion `retPair.second && "Error inserting n...

Sorry everything has slowed down a bit. I am going to try and allocate some time to this soon. The current issues are: Terrain splatting isn't quite correct The Ogre material generator only supports ~5-6 textures splatted per terrain. There seems to be rare cases where we need more than 6. This is a...

Yeah, that seems to build fine with the debug libs