>>716518045
>you can literally have negative input lag,
No, you can't, and you are stupid as fuck.
Run-ahead skipping frames of animation is not negative input lag, you absolute retard
>>716518469
Only if you have a high refresh-rate monitor. I've tested extensively on 60Hz and there is no way to get both low-lag and no frame-tearing, so most poorfags emulating on 60Hz monitors or cell-phones or Steamdeck, or chinkhelds will have tons of input lag. There is additional V-Sync lag not part of the inherent display lag. For my 240Hz VRR monitor, it's not an issue. Test it yourself and see.
>>716518906
It's not been debunked at all, not even one part, unless you consider garbage like
>>716521979 where retards just shit their diaper and scream "WRONG WRONG WRONG REEEEEE"
I've done literally thousands of input lag tests on emulation/run-ahead to come to this conclusion about run-ahead not being worth it, the only person in the world to do so.
It's so much more important to have a low-lag environment with low-lag controller, low-lag monitor, and no buffering/laggy V-Sync. Run-ahead is a shitty cope that causes more issues than it helps and absolutely does not help the core problem of a laggy setup. Most people just emulate on cell phones or their old shitty laptop and wonder why it's a laggy mess.
I'm not hating on emulation at all btw, when you have a proper low-lag setup, you don't NEED (or want) run-ahead because lag is very similar to original hardware. But very few people emulating actually achieve that and cope with run-ahead.