I eradicated a bug which was calculating incorrect transforms for GeomTransform objects. If you use GeomTransform from XODE (this is when you have a which is a child of a and it has an offset ) you may notice some differences if you do a cvs update. Please read my cvs log message for details.
The method signature of XODEParserDOM has also changed - no need to create a XODETransform object, just pass the Matrix4f directly in. You’ll soon see what to do if you checkout and recompile.
The XODE parser has had some rather major internal changes - apart from the two previously mentioned these are all under the hood so unless you tinker with the XODE objects directly you don’t have to worry. Again, read the commit log message for details.
Will.