21-01-2022, 03:57 PM
(This post was last modified: 21-01-2022, 04:03 PM by josemendez.)
(21-01-2022, 03:50 PM)lufydad Wrote: With only 3 actors (instead of 12) the problem seems similar : https://imgur.com/a/r2mQwZy. It looks like the death spiral is triggered by the function AddActor of ObiSolver (see https://imgur.com/a/eYkvepv).
Is there a way to improve it ? by changing some parameters for example ?
For only 12 actors, AddActor() should be quite fast. I see no reason for it to trigger this.
I'm out of ideas at this point. Would it be possible for you to share with me a scene/project that reproduces this? You can send it to support(at)virtualmethodstudio.com, I will take a look and hopefully find the culprit.
(*)Edit: How many colliders do you have in your scene? in particular, how many MeshColliders? When a backend is first initialized, collider data is generated. If you have many different mesh colliders, the cost of building BVHs for all those can add up. That would explain that the amount of actors in the scene does not seem to affect performance, but this is just a guess.
kind regards,