5 ms·
>proprietary communication stack for latency reasons. How would it being proprietary reduce latency? That mostly sounds anticompetitive to me
by water-your-self 4y ago
>proprietary communication stack for latency reasons.
How would it being proprietary reduce latency? That mostly sounds anticompetitive to me
- sudosysgen 4y agoThey connect directly to the Stadia servers over WiFi.
- aaronax 4y agoIn general, it would be because they can skip "things" that are required by a standard to support a wide variety of use cases, yet unnecessary for their specific use case. Skipped steps plausibly leads to higher performance.
- ethbr0 4y agoAnd specifically because they can skip entire components. Controller -> Stadia device -> router -> Stadia is a helluva lot slower than Controller -> router -> Stadia And also drastically simplified the "Stadia runs on all kinds of devices" requirements. It seems like a smart architectural decision.
- Nullabillity 4y agoOn the other hand, you're now stuck on wi-fi even when the client device is wired. And you've made the setup process a lot more complicated.
- ethbr0 4y agoYeah, but for low bandwidth use cases I'd guess that direct wi-fi still offers lower latency over wired-to-hardware-wired-to-router. The data trip through unoptimized stacks on the hardware would really hurt. And optimizing a diversity of different hardware devices (some of which predate Stadia) sounds like a support nightmare.
- simonjgreen 4y agoThere was no open format in place, it was pretty uncharted territory to have your console controller talk direct to a cloud game service