The original retro 64 timing loop reset numticks (logic loop iterations) if >500 in case of alt+tab or whatever, this was too long so for Easter Bonus changed it to 50 numticks, this meant that, yes the game would run slower than it should, but was actually playable, albeit at 3-5FPS, on really slow PCs.
Now I've changed it a bit so that if app is suspended OR titlebar is dragged, it doesn't "catch up" it resets the timing routing. And I've left the 50 loop iterations in now for slower machines. This may even be too high. My debug stats output the number of ticks and for a normal 60Hz display with a 200Hz logic, the number of ticks is around 3, so 50 could be pretty slow and to be honest, if it's that slow I think the PC isn't suitable anyway, so I might drop it to 20 or so. I'll do some testing on crap machines when my final game is ready. I'm not sure you can set a value that's fine for all PCs, it depends on the game imho.
Now I've changed it a bit so that if app is suspended OR titlebar is dragged, it doesn't "catch up" it resets the timing routing. And I've left the 50 loop iterations in now for slower machines. This may even be too high. My debug stats output the number of ticks and for a normal 60Hz display with a 200Hz logic, the number of ticks is around 3, so 50 could be pretty slow and to be honest, if it's that slow I think the PC isn't suitable anyway, so I might drop it to 20 or so. I'll do some testing on crap machines when my final game is ready. I'm not sure you can set a value that's fine for all PCs, it depends on the game imho.