You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2021. It is now read-only.
So dt is calculated using os.time or whatever. When you use the home menu to pause out, dt is done properly. As in dt = 5 when you homemenu, you wait five seconds and then you go back to the game, dt = 10 now since it's using the OS time. I mean obviously this is expected by nature, but is it intended? I feel like there are situations where this might be wanted or unwanted. If it's intended, then I should make my own dt, say gt (gameTime). And have it go in the update like if dt > .1 then gt = gt + .1 dt = 0 end
Or is it unintended, and I shouldn't mess with my code lol. It's not a big deal, it just caused some funny bugs lol.
The text was updated successfully, but these errors were encountered:
I kinda figured. But honestly in some cases that effect might be desired. I think I'll go ahead and modify my game code, unless your hard set on fixing it lol.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So dt is calculated using os.time or whatever. When you use the home menu to pause out, dt is done properly. As in dt = 5 when you homemenu, you wait five seconds and then you go back to the game, dt = 10 now since it's using the OS time. I mean obviously this is expected by nature, but is it intended? I feel like there are situations where this might be wanted or unwanted. If it's intended, then I should make my own dt, say gt (gameTime). And have it go in the update like
if dt > .1 then gt = gt + .1 dt = 0 end
Or is it unintended, and I shouldn't mess with my code lol. It's not a big deal, it just caused some funny bugs lol.
The text was updated successfully, but these errors were encountered: