Got a brief bug (on PC) where, if you get disconnected and reconnected back into the mission, it killed my controller functionality for crouching. I checked multiple controllers and verified it wasn't a controller issue. Crouching still worked through my keyboard. After a second disconnect/reconnect, it came back. I didn't get any other bugs during the mission or disconnected again after that, so the issue never returned.
A weird bug, for sure. Figured I'd report it. I'll admit I didn't notice the disconnect error code since I'm so used to getting disconnected (I have kinda crappy internet).
-
Hello there[url=https://cdn.discordapp.com/attachments/902560216871239752/989591085506515074/Hellothere.gif],[/url] Thank you for your report, Bungie is aware and investigating this. Stay tuned to the [url=https://www.bungie.net/en/News]TWaB[/url] and [url=https://twitter.com/BungieHelp]official Twitter[/url] for updates
-
Same issue with controller on Steam. I've been trying for days to get the solo flawless and 30 min triumphs, and every single time, this bug pops up. Unfortunately for me, none of the fixes folk here have suggested worked for me. Tried pulling the battery pack, using another controller, switching layouts, switching subclasses. None of it did anything. And since I'm trying to go for flawless, dying to respawn defeats the purpose.
-
I also have the same issue, running on an Xbox One S - doesn’t seem to be any rhyme or reason as to why it happens, just suddenly I can’t crouch in that room.
-
Happens on playstation too. I checked a couple times and once my crouch was unbound. Not only crouch but warlock rift wouldn't work either
-
I have the exact same issue. For me it occurs in the small Scanner rooms, suggesting the transition between them may be causing a delay with input devices.
-
Edited by Defaced_Reality: 12/22/2022 3:57:00 AMI was literally looking to post this myself glad to see I'm the only one Edit. I had to back out of the mission and went to the helm and it worked again. It happened to me three other times but usually restarting my controller worked this time it didn't. I'm on PS5
-
This happened to me except no disconnection
-
Happens to all platforms from what I've seen. Try switching subclass and then switching back to what you had originally. It worked for me and a few friends on xbox.