It’s super weird. They made a big deal about it being wi-fi, which meant it wasn’t tethered at all to the specific device you were using, it sent commands over wi-fi to the Google server which then sent the video to the device you were using. That meant that you could play on any device and the controller would work.
Now it sounds like it’s just a normal controller that communicates through the device you’re using, but worse since you can’t even use it wirelessly on your PC/laptop/phone/tablet.
I wonder if wi-fi just added too much latency to the experience so they’ve abandoned that.
The controller having bluetooth makes sense since I’d imagine they want the controller to work for general PC gaming and not just the Stadia platform.
Most likely scenario - they created a generic controller setup flow to cover both Stadia & Non-Stadia configurations and forgot that their own hardware didn’t have Bluetooth. Whoops.
It was a key part of their original presentation, that the latency introduced from bluetooth connecting your controller to the game console and then out to the internet was a problem. I immediately fingered that to be bullshit, but it’s surprising if they completely back off.
The controller isn’t required for Stadia though - it’s just a nice to have. I’d imagine they want to position it as a high-end gaming controller that is optimized for Stadia so that its pricepoint ($69) is roughtly inline with other controllers (i.e. “you only pay $20 more than a standard controller for the best experience!” type of deal) .
Another possibility is that the wifi controller adds too many technical hurdles. Synchronizing packets when everything comes from one device (your computer or tablet) is one thing. Doing it with multiple devices from multiple sources is a more complicated story.
I’m confused. Why do people think the Wifi thing isn’t working, and it’s using Bluetooth?
The problem described in the articles is that the Wifi option only works for Chromecast Ultra. Since Bluetooth is not an option, for anything else you need to use a cable. Given that, it doesn’t sound like the problem with Wifi is anything really fundamental like power consumption or synchronization. Can’t imagine what it’d be though. Or how they’d discover it this late.
I don’t see why the chromecast would work any differently than a Stadia app on a FireTV or Roku. Either way it’s just streaming media from a Google datacenter somewhere.
The interface for “how do I connect my stadia controller to my wifi” isn’t complete across all platforms
They had to make that interface possible on the chromecast ultra because maybe it’s not powerful enough to read and pass along inputs (much higher data stream than the remote).