3 ms·
The server will know what frame you were seeing when you pressed your button. So it rewinds it's state machine the appropriate number of frames (hopefully jus
by bryanlarsen 8y ago
The server will know what frame you were seeing when you pressed your button. So it rewinds it's state machine the appropriate number of frames (hopefully just 1), applies the input, and fast forwards again.
This may result in a visual glitch, but you won't have missed your target.
- stordoff 8y agoI wonder if you could use something like the RetroArch rollback solution[1] - render multiple versions of the stream, then pick the closest one based on player input. With a fast enough Internet connection, you could let the _client_ pick, then there is no lag. Of course, the hardware you have to throw at it to do that quickly becomes ridiculous, unless you can come up with a way of efficiently rendering the multiple versions. [1] https://www.libretro.com/index.php/retroarch-1-7-2%E2%80%8A-%E2%80%8Aachieving-better-latency-than-original-hardware-through-new-runahead-method/ https://www.libretro.com/index.php/retroarch-1-7-2%E2%80%8A-...