Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My understanding is that the controller supposedly connects directly to Google through WiFi rather than going through the device you're playing on.


Right. The idea seems to be that the controller directly talks to Google via WiFi to minimize the input latency, while the display device also directly talks to Google to minimize the output latency.


Hmm. Does this mean that the controller is the "brains", and after sending and receiving the game play data, then needs to beam it to your device? Or do the two devices (controller + screen) work together to handle some of this?

I fear for the latency in general.


Neither device is the brains. The controller uploads inputs. The Chromecast downloads outputs.

The brains is Google’s cloud.


I would think it's just sending data on your inputs to the data center directly to reduce latency, but otherwise has no other brains.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: