7 ms·
> The tick loop waits at least 3 centiseconds per frame, giving an effective rate of about 33.33 Hz 3 centiseconds instead of 30 miliseconds, totally not a rob
by not-a-llm 2mo ago
> The tick loop waits at least 3 centiseconds per frame, giving an effective rate of about 33.33 Hz
3 centiseconds instead of 30 miliseconds, totally not a robot
- SamBam 2mo agoWhy would AI say that, when nearly every piece of training data is ever been fed would use milliseconds? I think much more likely that this is how the author thinks of it. 3 hundreds of a second == 33 Hz is very clean in my human brain.
- nnevatie 2mo agoNo one, ever, uses centiseconds in this context.
- tom_ 2mo agoCentiseconds was one of the ways time was measured on the BBC Micro. Your convenient options for accurately measuring the passage of time were vsyncs (50/sec), centiseconds (100/sec), microseconds (1,000,000/sec), or cycles (2,000,000/sec).
- jamesrandall 2mo agoIt's actually in the commented original disassembly and used in some of the original BBC documentation / writing. Which is how it ended up here - the article is a mix of things I wrote and things I asked an AI to write for me from the notes / findings from the archaeolgy.
- nnevatie 2mo agoOk, that makes sense. I was commenting from a modern gamedev context.
- jamesrandall 2mo agoThe weird world of retro game archaeology - it's genuinely fascinating.
- deleted 2mo ago[deleted]