I'd like to dynamically change the tick rate based on user activity.
If someone is actively modeling / moving the viewport camera around / etc - I want it to run the full 120 FPS (or faster, within reason). But once they're idle in the app I want to scale down the tick rate to ~60 or lower, with probably a setting for it. This should solve the minimizing issue in #36 as well as free up some CPU cycles when the user isn't really doing anything in the app but it's connected nonetheless.
McManning
commented
2 years ago
From my rant in #36 -
I'd like to dynamically change the tick rate based on user activity.
If someone is actively modeling / moving the viewport camera around / etc - I want it to run the full 120 FPS (or faster, within reason). But once they're idle in the app I want to scale down the tick rate to ~60 or lower, with probably a setting for it. This should solve the minimizing issue in #36 as well as free up some CPU cycles when the user isn't really doing anything in the app but it's connected nonetheless.