Python-Ogre 1.2 Release Candidate 1 Available

It's time for another release cycle for Python-Ogre and as with previous releases I'm making an early release candidate available for testing..

It can be downloaded from [b]here[/b]

Included are Updates and General Library Improvements to:

1. * Ogre (Latest 1.4 cvs version)
   * QuickGui, OgreForests (updated to latest versions)
   * Particle Universe 0.6
   * Bullet 2.66
   * Caelum Rev 127 and updated media.
   * Physx - free functions are now exposed so should work as an independ library
   * Ogrevideoffmpeg - updated to latest ffmpeg
   * various improvements in code generation - see the ChangeLog.txt for more information[/list:u]
   Important Note: NxOgre and Navi are not supported in this release candidate!
   
   Regards
   Andy

Ace,

downloading the beast now!

Cool. My problem is that I need NxOgre, but i´ll try it anyway.
How should I understand the PhysX thingy? Are we allowed to use it independet now? How will you try to combine this with NxOgre?
EDIT:
Is there any possibility to have PythonOgre 1.1 and 1.2 RC1 at the same time?
I would want to name the old one module ogre1 so that I can work with my project that uses nxogre. The RC woudl be named normal so the demos should run fine without any changes then.
Is there an possibility to do this?

Is there any possibility to have PythonOgre 1.1 and 1.2 RC1 at the same time?

Yes i think you can. But you should rename your current 'site-packages/ogre' directory before installing the new RC, cause it deletes/overwrites current contents.

Of course, in your project code you should update your import statements accordingly to match your renamed old directory. In your case 'from ogre1'.

Good luck.

You can't mix and match modules between 'major' Python-Ogre releases -- this is due to the Ogre library changing between releases and nearly every module is linked to a particular Ogre version.

However NxOgre is now working (the '09 version) and will be in the RC2 - Navi is also compiling but failing on the Demo which I need to investigate (probably an API change that I need to handle)

Andy

Which ogre CVS revision does this date to?

It'd be great if the saving to .jpg from texture, deleting nodeTrack, cloning animation bugs were fixed in this one.

Which ogre CVS revision does this date to?


Could use that information too.

massive thanks to the team maintaining python-ogre, we've played around with it and we love it!

just curious, how's the progress on getting the 1.2 out?
I just read from Ogre's main page that OGRE 1.4.9 is out and it contains some important fixes..