16-07-2021, 10:31 AM
(This post was last modified: 16-07-2021, 10:33 AM by josemendez.)
Hi!
It is indeed a case of death spiraling, but still the amount time consumed by Obi is far from normal or acceptable, and could very well be causing death spiraling by itself. I believe there's something else going on here. In the worst possible scenario should not take more than a millisecond.
What I'd suggest to do: try disabling constraints in the solver one by one. Start by disabling particle and collider collisions, then bend, then distance. See if it makes any difference along the way. Eventually disable all constraints. If performance hasn't improved considerably by then, disable the ObiRopeRenderer. Report back the results you get, this way we can determine if simulation is the culprit and if so, which kind of constraints. If it isn't, maybe rendering (mesh generation) is.
It is indeed a case of death spiraling, but still the amount time consumed by Obi is far from normal or acceptable, and could very well be causing death spiraling by itself. I believe there's something else going on here. In the worst possible scenario should not take more than a millisecond.
What I'd suggest to do: try disabling constraints in the solver one by one. Start by disabling particle and collider collisions, then bend, then distance. See if it makes any difference along the way. Eventually disable all constraints. If performance hasn't improved considerably by then, disable the ObiRopeRenderer. Report back the results you get, this way we can determine if simulation is the culprit and if so, which kind of constraints. If it isn't, maybe rendering (mesh generation) is.