(09-12-2019, 04:23 PM)josemendez Wrote: Hi,
7 ms for a few ropes is not normal at all, so there must be something off. How big is the particle pool of your solver? In the rod screenshot I saw you were using 5000 particles... surely your rope/rod is not that dense? Try reducing it to somewhere around 500 (even less if your rod does not use up that many particles). That should save some time.
Anyway, I'm unable to reproduce this performance drop. I can take a look at your project if you wish. If possible, send a repro scene to support(at)virtualmethodstudio.com.
Hey,
I reduced the max particle count to 600 for the solver but this did not have any notable effect. Used particle count is 165 (noticed this information inside the Solver's inspector).
Sometimes ObiSolver.LateUpdate() and ObiSolver.FixedUpdate() taken up roughly the same amount of time (4ms each) but most of the time LateUpdate() takes around 6ms and FixedUpdate() 2ms.
What should the ms stay at? Doesn't this depend on little bit on the hardware? CPU is 7700HQ and GPU GTX 1070, if that helps. And these measurements are taken from inside the Editor. Perhaps the calculation time is reduced in a build.