19-01-2022, 05:18 PM
I see another strange thing when the gameobjects are instantiated : https://imgur.com/a/kScsSBR
In the 2 cases it seems to come from the the ApplyConstraint (see https://imgur.com/a/8XIcdFG).
The interpolation costs only 3 ms, while fixed update costs 13ms.
(17-01-2022, 08:14 PM)josemendez Wrote: Never seen something similar, tbh. The cost of a FixedUpdate call is independent of where in the frame it happens. Could you get deeper into the calls tack and see where is this coming from?
Profile to see whether the culprit is simulation (very unlikely) or mesh generation/rendering, which happens during solver.Interpolate(). If that's the issue, using simpler rendering method and/or making use of aggressive mesh decimation will help. Decimation can be enabled in the ObiPathSmoother component.
In the 2 cases it seems to come from the the ApplyConstraint (see https://imgur.com/a/8XIcdFG).
The interpolation costs only 3 ms, while fixed update costs 13ms.