07-04-2021, 11:15 AM
(This post was last modified: 07-04-2021, 11:21 AM by josemendez.)
The "Interpolate" function call does two things: interpolate particles if needed (which is extremely cheap btw), then trigger the rendering callback.
So all cloth mesh updating / rendering will appear under the "interpolate" call in the profiler. Unfolding the "interpolate" call will show these.
In your case, 5ms spent there means the cost of updating mesh vertices/normals/tangents is quite high. Maybe you can use a cheaper tangent update mode in your cloth mesh renderer component.
Also keep in mind that you're not actually using Burst, as the warning in the solver is telling you. You don't have the required dependencies installed, so the simulation will fall back to the native backend (Oni).
So all cloth mesh updating / rendering will appear under the "interpolate" call in the profiler. Unfolding the "interpolate" call will show these.
In your case, 5ms spent there means the cost of updating mesh vertices/normals/tangents is quite high. Maybe you can use a cheaper tangent update mode in your cloth mesh renderer component.
Also keep in mind that you're not actually using Burst, as the warning in the solver is telling you. You don't have the required dependencies installed, so the simulation will fall back to the native backend (Oni).