So I've hit some funkyness with the conservation of energy during simulations.
Windows 10
Window focused
Conserves all energy (even with rounding errors)
Minimizing frequently
Conserves rather well (extreemly rare are the cases when it dips and by very little, dip != floating errors)
Mac OS (latest ventura)
Window focused
Dips randomly
Minimizing window / swapping active workspace
Dips often and way harder to the point at which it stops all movement eventually in ~5-10 min
All forces (restitution, dampening, gravity, friction etc) are configured to keep the system going forever but in reality the ball eventually stops completely.
I'm aware that the window in bevy may be throttled but by default it runs as fast as it can.
Tried using fixed timestep, increasing frequency etc. nothing really worked.
Saw integration parameters but from reading about them not sure what I could try.
What I noticed is that swapping workspaces, minimizing windows exhacerbates the loss but it happens regardles, extreemly noticeable on mac.
So I've hit some funkyness with the conservation of energy during simulations.
Windows 10
Mac OS (latest ventura)
All forces (restitution, dampening, gravity, friction etc) are configured to keep the system going forever but in reality the ball eventually stops completely. I'm aware that the window in bevy may be throttled but by default it runs as fast as it can.
Tried using fixed timestep, increasing frequency etc. nothing really worked. Saw integration parameters but from reading about them not sure what I could try.
What I noticed is that swapping workspaces, minimizing windows exhacerbates the loss but it happens regardles, extreemly noticeable on mac.
main.rs
recording log-release-workspace-switch.txt log-release-same-workspace-but-minimizing.txt