[Solved] Upgrading to 1.0.22T5, how?

gbisocoli

07-04-2009 23:59:34

There is a new version of Ogre (1.6.1 VC90 ), does latest NxOgre ( 1.0.22T5 ) support this version of Ogre?
If true, which version should I use? (Bleeding, BloodyMess) I don't know the differences between them (I've been searching but couldn't find). I'm using now: Ogre v1.4.9 [Eihort] + NxOgre 1.0 '21 (this is bleeding, right?)
I've never upgraded before, I started using Ogre/NxOgre on June, 2008 and haven't upgraded yet. It is just pasting (uncompressing) over the previous files or I should delete previous installations? This question is for NxOgre and Ogre also. Thanks!

spacegaier

08-04-2009 13:31:25

NxOgre, doesn't care which version of Ogre you are using as long it's either 1.4.X or 1.6.X ;) (don't know if 1.2.X or earlier work as well).

NxOgre 1.0.X is Bleeding, yes. I'd go ahead and uninstall Ogre with its uninstaller. For NxOgre: Just delete the old folder and put the new one there.

Regarding the version decision:
- Bleeding, currently has more features and is stable, however not developed any further (was just kind a temporary version).
- BloodyMess is the current version. Currently, it doesn't have as much features as Bleeding does, however it's already a bit more stable and continouesly growing.

If you immediately need fully featured physics, go for Bleeding, but if you are just starting to work with physics and try to get a hold on it, I'd go for BloodyMess. It has already more documentation than the other versions before had toghether. So, it should be much more easy to start with. But of course it's up to you...

PS: No matter which version you choose, have a look at the NxOgre Portal in the Ogre wiki.

gbisocoli

09-04-2009 03:14:01

Thanks! I upgraded perfectly, I'll keep using Bleeding for now.
Now I'm having the famous "fatal error C1083: Cannot open program database file" but that's a Visual Studio bug, so don't mind about it. Thanks again!

nargil

09-04-2009 08:45:17

just delete the pdb file

gbisocoli

09-04-2009 19:21:53

Oh, thanks! I was worried about that because I applied an official hotfix and didn't fix it, but the deleting did!. Thanks!