2 ms·
I'm too tired to look it up right now (I'm in DC, check the news), but I believe the WebVR implementations are trying to remove triple-buffering, because entire
by moron4hire 11y ago
I'm too tired to look it up right now (I'm in DC, check the news), but I believe the WebVR implementations are trying to remove triple-buffering, because entire frames of latency are bad news. I don't want to put words in Brandon Jones' mouth, but I seem to remember him talking about having it implemented in Chrome, which came part-and-parcel with unhinging requestAnimationFrame from the "default" refresh rate of 60hz and using the actual, target display's refresh rate. Mozilla apparently has some hurdles to get over before it's able to do this, so Firefox is lagging in a pure performance standpoint (though it is slightly more stable).