3 ms·
As someone working on real time streaming, I find this both interesting and impressive, but I also cannot shake the feeling that WebRTC will be too slow for mos
by fxtentacle 6y ago
As someone working on real time streaming, I find this both interesting and impressive, but I also cannot shake the feeling that WebRTC will be too slow for most games.
At least in my experience, WebRTC even when using UDP was a lot slower than custom protocols, mostly because it responds badly to packet loss.
If I use plain UDP in c++, I can layer on forward error correction like Solomon Reed and just ignore lost packets up to a percentage. That, alongside with low level control of the transmission timings seems to be the difference between 60ms peak latency with WebRTC and 5-8ms in C++. Or noticeable input lag @60fps vs. exactly one frame.
- felipellrocha 6y agoHow would webrtc impact anything? It’s literally a udp socket with a couple of protocols built on top of it
- fxtentacle 6y agoYes, those protocols make a huge difference. Also, high throughput low loss UDP relies on ms-level timing control, which is all but impossible in Javascript.