Nan/Inf collider Transform security ? #431
Description
While making a level editor, I had an error with my camera projection calculation, resulting in nan/inf positions that where given to the Transform of rigid bodies and colliders.
I was surprised to see that RP3D didn't gave any warnings in that situation (I'm using a debug build of the lib), instead the world update function failed random asserts and crashed the whole application (incorrect broad phase id, incorrect normal collision etc...). This made the debugging effort quite difficult on my part. Because the ECS (and trust me, I love ECSs) is very hard to read when trying to pin point the exact source of a problem. The only thing I could see was that a lot of vector calculation had incorrect values.
I think the debug builds would greatly benefits from having asserts or warning specifically when the user tries to give incorrect transform information such as nan or inf inside the position or quaternions.