Quote:
|
It depends on when program reads input. Latency can be much smaller if input is read later than during vblank or input is read in "real time" (for example keyboard input may be processed instantly when key is pressed if keyboard read uses interrupts)
|
Great, that's a good improvement..
Just juggling thoughts.. Maybe some part of the methodology of this partial frame updating /slicing could be applicable to the non vsync mode as well?
I.e. by only applying the slicing and mid-frame updating, without the host beam racing part, non-vsynced mode could potentially get closer to real hardware response too?