cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Controller stops working in Destiny

Hi, Weird bug here where the controller stops responding in destiny. I can still hit the stadia button to see the stadia menu, and I can navigate that fine, but in game nothing responds. This happens frequently, and if I’m in the middle of turning the camera, when it disconnects it will continue the previous input as if I’m still performing it. Any help with this?
8 Kudos
41 Replies
Community Member

Same here only on metro really weird

0 Kudos
Community Member

I've had a similar problem in Grid. It thinks the controller is disconnected and pauses the game, but the controller is still marked as linked in the Stadia menu, the Stadia button and menu works, and the light is solid white
1 Kudo
Community Member

@GraceFromGoogle  can you raise that to your support team please it seems to have been encountered by multiple users. Thanks.

0 Kudos
Community Member

I've had more chance to play today and can reproduce this 100% of the time. 

The controller has been successfully linked with the Chromecast. However, each time I start up a game, within 30-90 seconds, the game reports that the controller is disconnected. However, I can still access the Stadia overlay with the controller. To fix it, I have to shut down and relink the controller reach time I start up a game

2 Kudos
Stadia Guide
Stadia Guide

Please be sure to also report this through the Send feedback option in the Stadia app so that the developers can review logs to look into this problem. 👍

2 Kudos
Community Member

Same issue here, any news? My WiFi signal is good and chromecast is wired connected. Home is fiber connected (800mb/s). How can I connect  Stadia support, I think the controller is the issue since some people don’t have the issue. Thanks!

0 Kudos
Community Member

I've reported via the Send Feedback tool, but it seems to have got worse in some cases. On some occasions the game stopped detecting the controller 2 or 3 times within the first few minutes of a game. As ever, I could still access the Stadia menu
0 Kudos
Community Member

I did reset the controller let’s see it this happens again.

0 Kudos
Community Member

The issue is still there, I will contact the support. This annoys me a lot, cannot play an online game if you have to quit stadia each time the bug appears!

0 Kudos
Community Member

The support advised me to move the controller to the 2.4ghz WiFi band in order to remove a distance cause but I am not confident since the WiFi box is not far from the controller less than 8 meters. Let’s test it!

By the way the support was not aware of such issue so the others that have the same problem, please contact Google! Thanks.

1 Kudo
Community Member

In the mean time I noticed that my nvidia shield is broadcasting direct WiFi at the same band as my router so I switched off the shield, more testing to come! I’ll keep you updated.

0 Kudos
Community Member

Unfortunately the issue is still present :(. Let's get back to 2.4 Ghz.

0 Kudos
Community Member

So far so good, it's still working but weird that on the same place the 5ghz does not work.

 

EDIT: There is no wall or a far distance between the wifi router and the controller

0 Kudos
Community Member

I've since had the issue go away. I have a dual band router that puts out two networks, rather than automatically switching between the two. Everything, including the controllers, were on the 5GHz network. I factory reset my controller and connected it to the 2.4GHz network. I've not had any problems since.
0 Kudos
Community Member

And you still have the 5Ghz active?

0 Kudos
Community Member

@yef Yes. Everything else, including the Chromecast, is on the 5GHz network. Just the controller is on the 2.4GHz
0 Kudos
Community Member

The wifi band doesn’t make a lot of sense since it still works in the menus.

 

I don’t actually have the option to switch. My router broadcasts both bands as the same name. To change that I’d have to reconnect every single wifi device in the house which is unreasonable

0 Kudos
Community Member

I agree it does not make sense, why not just rename the 2.4 Ghz and all others wifi clients stay at 5Ghz with the current SSID name?

0 Kudos
Community Member

Same issue with my controller during the last 3 sessions in Destiny 2, two days apart. The reticle will suddenly drift and controller is unresponsive. After 15-30 seconds it reconnects automatically and I can continue. This happened on two different Chromecast Ultras, one wireless and one wired. Controller was fully charged. It did not disconnect again during the same sessions.
1 Kudo
Community Member

5Ghz or 2.4Ghz for the controller?

0 Kudos
Community Member

I've done some reading up on this. In my environment, I am running Google WiFi mesh network, which will automagically switch clients from 2.4 to 5 Ghz if they are dual band. After some spot-checking of other clients, I see they are running 2.4 where previously they had been running 5. So, I believe the sporadic drops are probably Google WiFi switching bands for better performance and doing so in a less than graceful manner. I will attempt to reach out to Stadia support and/or Google WiFi support for confirmation of this anomaly, and hopefully they can do something about it in a future firmware update.
0 Kudos
Community Member

Same here, RDR2 and Metro.

0 Kudos
Community Member

Same problem but on Ghost Recon Breakpoint, controller doesn't respond to the game but I am able to press Stadia button and play in the menu.

 

Edit: problem fixed when I switch to 2.4ghz instead of 5ghz

0 Kudos
Community Member

I am having the same problem with Red Dead and Borderlands. Can we have an official response on this?
0 Kudos
Community Member

I was able to fix the issue by ensuring that Stadia used different Wifi network or used wired connection. I think the issue is somehow related to having both Chromecast and stadia controller in same wifi network
0 Kudos
Community Member

I disagree since I have the issue from the beginning and my chromecast is wired connected.
0 Kudos
Community Member

@FOlavo The controller is a wireless device unto itself, so whether or not the Chromecast is wired will not make a difference. For the record, both CCUs I have are wired. The phenomenon occurs whether or not my CCUs are wired or wireless. In my situation, as I've stated above, I'm on Google Wifi (pre-Nest) so wireless devices (such as the controller) will attempt to connect via 2.4 or 5 GHz (or possibly between multiple wifi access points), depending on what *it* thinks is a stronger signal. It is my belief that the controller is switching between the two bands and that's what causes the temporary disconnect. The phenomenon is not consistent enough to predict and occurs even if I'm 5 feet from the router/access point. My hope is Google will push a controller update which will prevent it from switching bands/points once it locks on for the first time.

1 Kudo
Community Member

@LovecraftTapes I understand the chromecast is a wireless device by itself. I was thinking maybe somehow they interfered?! I had exact same symptons and I fixed them by going wired on the chromecast. Doenst make much sense to me, but this is what I observed and am able to reproduce it everytime.

For the record, I have a 5Ghz wifi network only (no 2.4Ghz).

I am sorry if this doesnt work for you - I was just trying to share what worked for me.

0 Kudos
Community Member

@FOlavo Thanks for the feedback. Do you have a separate SSID for 2.4 and 5 GHz channels? This is the Achilles heel for me, I think, because Google Wifi's mesh system has the *same* SSID for both channels, so wireless devices can't differentiate and, as far as I can tell, switch between the two signals as it thinks it needs to. There's no way to force the Stadia controller onto a certain band. It may be of interest to note, too, that I've only seen this happen while playing a FPS. Wondering if maybe the controller automatically switches between channels if it detects some sort of input lag while managing that monstrous throughput?

1 Kudo