running out of memory

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
User avatar
psi29a
Posts: 5361
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: running out of memory

Post by psi29a »

sirherrbatka wrote:Does OpenMW builds with that RC?
We currently build with _no_ RCs of anything. The last RC was SDL2, but those packages have just been updated to the final release.
User avatar
sirherrbatka
Posts: 2159
Joined: 07 Aug 2011, 17:21

Re: running out of memory

Post by sirherrbatka »

I don't ask if we do it. I ask If anybody succeded to build OpenMw with Ogre 1.9 RC.
User avatar
psi29a
Posts: 5361
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: running out of memory

Post by psi29a »

sirherrbatka wrote:I don't ask if we do it. I ask If anybody succeded to build OpenMw with Ogre 1.9 RC.
Sorry, I didn't understand your question. That is something else and I believe someone did some work a few months ago in preparation with Ogre3D 1.9

Update: According to Chris, he had OpenMW working with Ogre3D 1.9 but that it required some ugly hacks and broke compatibility with 1.8. The ugly hacks could be hidden behind macros, but the real issue and fix needs to be in Ogre3D. It is unsure if the fix will land in time for 1.9 (since it in RC) or later though.
Chris
Posts: 1626
Joined: 04 Sep 2011, 08:33

Re: running out of memory

Post by Chris »

sirherrbatka wrote:I don't ask if we do it. I ask If anybody succeded to build OpenMw with Ogre 1.9 RC.
I did. I required some pretty ugly changes in OpenMW, though... basically changing things like this:

Code: Select all

Ogre::MaterialPtr material = Ogre::MaterialManager::getSingleton().getByName(name);
to

Code: Select all

Ogre::MaterialPtr material = Ogre::MaterialManager::getSingleton().getByName(name).staticCast<Ogre::Material>();
Not only is it exceedingly ugly, it's incompatible with 1.8. There were a number of cases like this in the code base, and it affected every inherited ResourceManager function that returns a ResourcePtr (while type-specific managers may have custom functions that return an appropriate type-specific SharedPtr that doesn't need the staticCast, so it was also inconsistent).

Last I read, there was one or two prospects for fixing this, but I have no idea when it will be fixed, nor do I know whether or not it will be done for the 1.9 release.
User avatar
sirherrbatka
Posts: 2159
Joined: 07 Aug 2011, 17:21

Re: running out of memory

Post by sirherrbatka »

Ok, that's clear.
User avatar
scrawl
Posts: 2152
Joined: 18 Feb 2012, 11:51

Re: running out of memory

Post by scrawl »

Chris wrote:
sirherrbatka wrote:I don't ask if we do it. I ask If anybody succeded to build OpenMw with Ogre 1.9 RC.
I did. I required some pretty ugly changes in OpenMW, though... basically changing things like this:
Fix for this has been merged: https://bitbucket.org/sinbad/ogre/commi ... a88da2652a
User avatar
psi29a
Posts: 5361
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: running out of memory

Post by psi29a »

Holy crap man, you managed to get code into Ogre so that OpenMW can be upgraded to Ogre3D 1.9 :)
Tarius
Posts: 574
Joined: 24 Oct 2011, 19:29

Re: running out of memory

Post by Tarius »

Chris: "Oh yea, I required some ugly stuff for this."
Scrawl: "Already fixed it."
haha

I nominate scrawl to be the next Zini if Zini disappears for some reason.
Locked