I asked it a very long time ago. The topic kinda died off when we realised that the library would probably need direct access to the object's data; I sincerely doubt it works by object numbers
However, if I were clever enough to write a physics engine I'd make it non-dbp reliant in such a way that you could create pseudo objects. Basically, instances of object classes whereby member variables are calculated and member functions either progress or report on the object in question's simulation. As the DBP coder creates new objects, they're simply pushed onto a STL Vector array (god I'm lazy) and each pseudo object is essentially an addressable set of numbers & functions.
I don't know much about rigid body physics, but I reckon you could just assume everything is a box with a mass and shock-absorption rating (or whatever). There's no real need for direct access to the object's definition data if we're gonna make a quick n dirty physics engine.
But then again, someone else is already doing it, so we can just wait
Can I ask you a Question?
What is it?
It's an interrogative form of sentence, used to test knowledge. But that's not important right now.
