SoldierX
11-10-2008 18:09:35
What are the reasons to use NxOgre with Ogre3D instead of PhysX directly? I'm sure there are reasons, but I havn't seen any, yet...
reptor
11-10-2008 20:00:17
Potential reasons why you might not want to use NxOgre are at least:
- it is not a complete wrapper for PhysX (yet)
- and it isn't a stable API, while PhysX is a stable API (The public interface of the library. It changes --> you must change your code if you are using those features of the library).
if you can accept those things then you can use NxOgre.
NxOgre can get you a physics scene running with less effort from you. That would be the benefit #1 as I see it.
At the moment helping with the development of NxOgre is rather difficult, because the source code repository is not public. So that is another minus for NxOgre. So you have to wait that a source code package is released to see what has been done to it. And in the mean time you will be guessing if it is worth it to do any work to develop NxOgre because you don't see what betajaen has been doing to the codebase. I recommend that this be changed soon, betajaen
- it is not a complete wrapper for PhysX (yet)
- and it isn't a stable API, while PhysX is a stable API (The public interface of the library. It changes --> you must change your code if you are using those features of the library).
if you can accept those things then you can use NxOgre.
NxOgre can get you a physics scene running with less effort from you. That would be the benefit #1 as I see it.
At the moment helping with the development of NxOgre is rather difficult, because the source code repository is not public. So that is another minus for NxOgre. So you have to wait that a source code package is released to see what has been done to it. And in the mean time you will be guessing if it is worth it to do any work to develop NxOgre because you don't see what betajaen has been doing to the codebase. I recommend that this be changed soon, betajaen