Obi Collider Performance

[josemendez]

Hi,
I just bought Obi Softbody and the test scenes work great.
Unfortunately thoug I have a major problem with the general usability for our project. I was - after carefully reading the documentation - under the assumption, that the limiting performance factor of the asset are the quantity and quality of the softbodies on screen. I have a medium size free roamable world where I wanted to drop softbody phssics entities around. But even if I just drop a single softbody I still need to assign Obi Colliders to every collider in the scene that the softbody could come in contact with. This on the other hand lead to an immense drop in fps from 60 to 2 with not even any softbody in the scene. Am I missing something or is this a limitation? Did I miss it while reading the documentation?

Best regards,
Daniel

Hi,

Unity does not allow for native code to interface directly with its own colliders. For that, having access to Unity's source code would be required. The next best thing is to have our own collider representation, and keep it in sync with Unity's. This is what the ObiCollider component does.

As long as a collider is static, the overhead of having a ObiCollider is zero. However if a collider moves around, ObiCollider must copy all collider properties (position,orientation,bounds,etc) to Obi's internal engine every time they change. While extremely cheap, the cost of this copy can add up if you have several hundreds/thousands of non static colliders moving every frame.

May I take a look at a profiler pic of your game?

kind regards,