Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Solver is too performance heavy
#3
(27-05-2025, 07:19 PM)josemendez Wrote: 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

Hello, thanks for reply!

I've noticed that Unity enable Burst's Safety Checks, Jobs Debugger and Leak Detection every time I want to relaunch Unity Editor, so disable it all back gives much better result.
But still in async. mode 1 solver (I've changed it a bit so I've attached several screenshots) with same rope costs ~40 FPS, inside of Profiler FixedUpdate not call more than once per frame so Time settings is set good and I really do not want to change Time because of project size.


Attached Files Thumbnail(s)
       
Reply


Messages In This Thread
Solver is too performance heavy - by quent_1982 - 27-05-2025, 03:53 PM
RE: Solver is too performance heavy - by quent_1982 - 28-05-2025, 11:10 AM