Well something I certainly wasn’t expecting – turns out (seems to me anyway) that the Mac C library doesn’t include the strnlen function – how weird is that !!!!!
Had to tweak some of my functionally transformation code to use strlen and then check the result..
Not a big deal – just a surprise..
So in addition to the PLSM2 that was just added there is now support for RakNet – demo is fairly simple at the moment (chat) however everything I could find has been wrapped..
Also updates for Ogre that need the latest PY++ (issues exposing ‘std’ classes has been resolved) plus a fix to my char * functional transformer as I wasn’t writing the terminating null to the C string 
Now to wrap the Ogitor scene importer so we can use that as a scene editor, plus direct wrappers for some of the scene managers…
To try and keep things up to date I felt it was time to use a windows blogger client. So here is post #1 from Windows Live Writer..
I’ve been looking at a possible game conversion across to PythonOgre – something open source (of course), simple and yet fun. This path has been down a few times and previously I’ve looked at a FPS for initial conversion. However I’m now thinking about a simple car racing game as I can get to play with interesting physics along the way.
Thought I’d grab some models and tracks from Q3Rally which meant getting blender to convert the BSP/MD3 files to Ogre meshes and .scene file. All went well and along the way I’ve written a Demo_DotScene.py module for the Python-Ogre demos and fixed a couple of minor bugs in the DotScene.py loader module.
Need to decide which media to include and I’ll update the SVN
Well as part of building the new binaries I thought I’d have a go at doing everything against the Ogre precompiled SDK — while it has an older verisonof CEGUI and OIS I felt that this would ensure longer term supportability and make things just a little easier to support…
However, turns out that as Steve is using the older version of CEGUI it is compiled without RTTI (RunTime information) which means it’s completely incompatible with Boost..
So back to the building board (so to speak) and tweak everything to build Ogre and use paths etc from the build…
Ogre 1.6.1 has been released and I’m working on this for PythonOgre. Expecting a Windwos binary release over the next few days, along with Linux updates (ensure the build works) and if everything goes weel the first Mac binary release….
There are a number of changes happening in the Python-Ogre SVN at the moment so bear with me if something breaks along the way — shouldn’t happen however often it does
Changes include implementing boost indexing as include files instead of linking it into the boost python library. This is actually a change in the latest Py++ that should make building Python-Ogre even simpler. It basically menas you need the pyplusplus/indexing_suite_v2/indexing_suite in your include path to build.
Also working on the Mac build which is going well — however fell like I’ve had to stand on my head and spin three times to get everything working 
— interesting challenges with things like AsertMacros.h defining a macro called ‘check’ with then breaks all the convenience functions in the Python-Ogre wrapper..
However intention to have stable SVN before Christmas..
Those of you who have had a look under the hood of Python-Ogre will know that we still require patches to be applied to many of the C++ libraries – and that these patched (at least for Ogre) have all been about virtual functions.
There has been a limitation in Py++ where transforming virtual functions (this is where we wrap the function to make it useful to Python – ie it might have a void * argument and we need it to be an unsigned int etc) simply didn’t work.
Well that’s now a thing of the past so the next release of Python-Ogre (for windows anyway) will be built against the precompiled SDK without losing any functionality….
:)
While improving the doc string documentation (I’ve removed excess leading whitespace and wraped text so it looks/fits better when we generate html documents) I discovered a couple (OK, 6) variables in the Ogre module that equate to boost::recursive_classes and couldn’t be exposed — if you try to access them you get a boost python error. This is now fixed in the SVN…
I’m going to release the documentation in a seperate package on SourceForge (over the next few days) so people have a more options (and it’s rather large)…
Decided it was time for a Python-Ogre overlay in the demos.. Now part of the SVN
It’s release time again with Python-Ogre 1.6.0 available here
Sorry about the size of this release (it’s hitting 100Meg) — however there are a ‘number’ of modules and their supporting media files included 
I will look to split this for the next release.
Modules included are:
Known problems:
Additional information on Python-Ogre will go here — just need to write it..
Copyright © Python-Ogre VibrantCMS Theme by 
