The collision tree does not seem to work correctly?
from the official Newton forums (user: Julio Jerez)
The collision tree does not seem to work correctly?
There are many reasons that can make the collision tree to work incorrectly, among them:
- Rigid bodies been too small, or moving at too high speed
- Faces been passed with the incorrect winding, collision tree does not support double-sided collision (but you can use two faces at the same location to achieve double-sidedness)
- Too many small faces
- Incorrect coordinate system
- Incorrect placement
- Corrupt or otherwise errorenous transformation matrix
- Collision geometry of colliding body been scale wrong, or offset relative to the body
- In some case engine using Euler angles but not using a standard pitch-yaw- roll convention
- Using an unit system too large or too small. Due to floating point precision range, it is best to use newton with International System of Units units with 1 unit calibrated to 1 meter, this is very common and used in most games.
All or these are difficult to determine by mere inspection, the first step on fixing the is to implement the global debug display using the iterators functions provided with the api.
By implementing the Debug Display the user will be able to see graphically what the physics engine is doing internally.
back to the FAQ
