Hi, I've been using Stadia for a while now, one if the gripes i have with the connectivity of the controller is, when you're playing via chrome, and your controller disconnects (dead battery or idle time), its not possible to reconnect unless you exit the game, or switch the game to another screen, as you need access to the main screen to get the controller option back up.
The controller auto connects when playing on CC ultra, but not while using browser.
Is there a workaround for this please?
Thanks
@Lankiebd Oh I don't think it's something wrong with your controller either, and you're right, it sounds like just a limitation playing Chrome browser. Yeah I'm not sure if there's a workaround in this case. Best is just not to let the controller go idle (which from my experience is quite a generous time limit). Apologies that I don't have a better answer.
@Lankiebd So I haven't really be able to replicate it, but I'm curious when you're experiencing this. If the controller disconnects because dead battery, you will have to plug in the cable anyway right? And Stadia session will log out when it's idle after 15 minutes. Are you experiencing constant controller disconnects in short period of time?
So if my controller died and disconnected, id have to charge but it won't reconnect wirelessly, you're right. On the Stadia app, the button input prompt appears but not on chrome, desktop or mobile version (Ive tried using desktop mode on mobile browser as well).
There isn't anything wrong with my controller, and I have 2 and same thing happens to both. I think its a flaw with the chrome browser.
The best way to replicate is whilst in a game, hold down the stadia button on the controller to turn off, and you should see an in-game message that a controller has been disconnected but not the stadia button prompt
This happened to me about an hour ago whilst playing rdr2, i left to go do something and came back 20 mins later, expecting the game timeout but it was still active but controller was not connected
@Lankiebd Oh I don't think it's something wrong with your controller either, and you're right, it sounds like just a limitation playing Chrome browser. Yeah I'm not sure if there's a workaround in this case. Best is just not to let the controller go idle (which from my experience is quite a generous time limit). Apologies that I don't have a better answer.
I think that the reason why it's not showing a button prompt on Chrome is because it will fall back on HID input.
Nowadays as I can remember the button code should not be regenerated while in the same session without logging of or switching location.
I've just tested it on my Win11 Chrome Browser, after shutting off the controller I also need to connect again while using the button code(Shift+Tab).