Ever wondered why the FPS meter read 36 instead of 35? Randy specifically explained this in a post that I was going to link to here, but I can't find it and I specifically remember it was in off-topic, so it probably got deleted because the thread that he posted in was too old. In fact, I sent a PM to Randy.Gez wrote:I still want an explanation on that 35.725 tics per second thing. TICRATE is defined as an integer.
And Octics aren't exactly 1/8th of a second because I had severe timing problems with my moving camera while assuming so, trying to get it to align with a script I was writing. I noticed that, assuming an octic was 1/8.0 of a second, my events were slowly desynchronizing, the script firing off too late as the camera was drifting slightly faster than I expected it to, implying that it was shorter than 1/8.0. So I did some quick math, comparing how far along the path the camera was to the first desynchronized event, and the math wound up giving me 1/8.57 instead of exactly 1/8.0.
Using 1/8.57 as a base for my calculations, my script's events now time perfectly with the movement of the camera.
So knowing this is important concerning synchronizing time of events.
