4 ms·
Why does it need to emulate every possible input, rather than emulating a single path assuming that the controller state remains unchanged? You can only display
by mikeash 10y ago
Why does it need to emulate every possible input, rather than emulating a single path assuming that the controller state remains unchanged? You can only display one future frame to the user, after all, and that seems like the best one to display.
- pjc50 10y agoThe point would be to render the frame(s) before the input arrives, to reduce latency. You can only display one frame, but you don't know which frame until the user actually inputs something.
- mikeash 10y agoOooh, I see! I was thinking of running the simulation forward by N frames optimistically, and then fixing it up when something else comes in, but the idea here is just to precompute every possible result. Nifty!
- byuu 10y agoI realize a lot of the 4096 states are extremely unlikely (especially Up+Down or Left+Right ... not physically possible on an unmodified controller); but if the inputs you predict end up wrong, then you have no choice but to run the frame again normally. This is going to cause an extreme jittering where the input lag doubles for some frames. Imagine audio stuttering from a scratched CD, or a framerate that suddenly dips from 60fps to 30fps for a moment and then resumes. With input, the effect is going to be even more jarring. If you're going to do this, you absolutely can't have a miss. Ever.
- mikeash 10y agoYep, makes total sense to me now. I was thinking of optimistic prediction, not deterministic precomputation.