02-12-2024, 08:57 AM
(This post was last modified: 02-12-2024, 08:57 AM by josemendez.)
Hi,
I'm unable to reproduce this. Which simulation backend are you using? Asking because baking works slightly differently depending on whether mesh data is already on the CPU (When using the Burst backend) or when it needs to be read back from the GPU (Compute backend).
Note that baking a mesh is extremely expensive, so not generally used at runtime. This is more of an editor tool. The typical approach to stop updating a simulation is to set the solver's maxStepsPerFrame to 0. This will keep rendering all actors managed by the solver, but will completely stop the simulation. This does not however allow to stop the simulation of specific ropes, only entire solvers.
kind regards,
I'm unable to reproduce this. Which simulation backend are you using? Asking because baking works slightly differently depending on whether mesh data is already on the CPU (When using the Burst backend) or when it needs to be read back from the GPU (Compute backend).
Note that baking a mesh is extremely expensive, so not generally used at runtime. This is more of an editor tool. The typical approach to stop updating a simulation is to set the solver's maxStepsPerFrame to 0. This will keep rendering all actors managed by the solver, but will completely stop the simulation. This does not however allow to stop the simulation of specific ropes, only entire solvers.
kind regards,