27-05-2025, 07:19 PM
(This post was last modified: 28-05-2025, 08:57 AM by josemendez.)
(27-05-2025, 03:53 PM)quent_1982 Wrote: I have a single medium length ObiRope with ~35 attachments, that costs around 22 FPS, but hole pure rope somehow costs around ~38 FPS, so the hole solver with single rope uses ~60 FPS, that is too much.
TimeStep in project is 0.015f, I've played a bit with ObiSolver values but it didn't help at all. If I set all solver's constraints to 1 and parallel it gives only ~12 fps.
These FPS numbers are not normal. They suggest that either the Burst compiler is disabled, or the jobs debugger is enabled. You must enable Burst and disable the debugger for normal performance inside the editor, as explained in the manual:
https://obi.virtualmethodstudio.com/manu...kends.html
Also keep in mind that Synchronous Fixed mode is very costly, and it may trigger death spiralling if combined with a small timestep. Try switching to Synchronous, if performance suddenly improves then consider adjusting your project’s max allowed timestep.
Kind regards