|
|
|
|
|
|
by googlag878
1513 days ago
|
|
|
Just today I ended up giving up on HTML5 gamedev because of the Chrome extra frame of lag issue: https://www.vsynctester.com/ If you have Godot or Unity or some other game engine that does web exports, try playing the native and web versions back-to-back of any game that draws a software mouse cursor, and don't hide the native hardware cursor so you can compare how much the software cursor lags the hardware cursor. The cynic in me says Google deliberately adds lag to browser games to guard the multi-billions of Play Store game revenues. Web audio has 300ish millisecond latency on many (not all) Android devices. |
|
|
And while I understand your cynicism, I don't think it's deliberate as much as it's complacency, given that it's latency issues all the way down when it comes to modern user interfaces.
A literal decade ago Microsoft Research uploaded a video highlighting how much of an effect minimizing latency for touchscreens had on the user experience[0]. The vast majority of tablets still utterly suck in this regard a decade later, and I wonder if any manage to get below the 10ms barrier.
And of course there is Dan Luu's famous 2017 article on computer latency in general[1].
[0] https://www.youtube.com/watch?v=vOvQCPLkPt4
[1] https://danluu.com/input-lag/