Probably this is confusing you:
1 tick = 1 / 16 seconds = 62.5 milliseconds.
It means that one second has 16 ticks. So 1 Tick is one sixteenth of a second, which is (1/16) second = 0.0625 seconds = 62.5 milliseconds.
I guess the strange "tick" unit stems from old times where games used to run with about 16 fps.
Ahh okay, so that part makes sense... I thought it was an equation (1 divided by 16).
Although, after taking that and trying to apply it to the rest of the author's explanation, I'm still completely lost. I just cannot make sense of what's going on.
One thing I don't get is what is the relationship between FPS and the time_step value? What influence does one have on the other?
The whole thing just seems so arbitrary and obtuse to me right now because so long as I don't understand what
time_step is doing, I can't understand how it's doing it or why.
Maybe I should just chalk it up to not being wired for programming and stick to the creative stuff?
By another token, should that workshop just make perfect sense to someone who hasn't programmed before? Or is some knowledge of programming assumed when reading it?
