Controller Interface: Action Inputs Disabled

While using the a controller to talk to a NPC, all actions get locked out and disabled. This happens when you walk out of range from the NPC causing the dialog box to auto-close. It does not seem to happen if you manually close out of the dialog box by selecting the dialog text. However, it did happen twice to me right before a boss fight. Both times were during the main scenario quests. The first time was at the start of the cultist boss fight and the second time was during the Architect boss fight.

Situational Notes:
I was using a Primalist Beastmaster.
I was in Spriggan form.
I was using a Razor Wolverine Ultimate controller.
My computer uses windows 10 with an Intel Core i7-10700F.
I was able to replicate the bug using the NPC located at the start of the first quest for the “Fall of the Outcasts” Monolith zone.

We are making some adjustments to our controller settings next patch. Please let me know if you are still experiencing this issue after 0.8.3.

Thanks.

I need to make a correction to my Bug Report. It appears that it occurs when you use the joystick “mouse movement” and A button to select a response to a NPC chat dialog.

Hello!

I had the same bug, also using a Primalist Beastmaster, but not transformed. I’ve had the bug randomly on and off throughout the game, and don’t know what’s caused it before. However, I have now had the issue after talking with the npc that went with me to get… Heorot’s Spear? (Sorry, forget the name) I then got the issue again when talking with 2 of the 5 civilians you save in the harbor after getting the spear. Talking to another one fixed it one of the times, but not the next. Very odd bug.

I’m using an Xbox 360 controller, and occasionally also my mouse and keyboard. When the keys get disabled, they are disabled for the controller, but also the keyboard. Also worth noting is that most of the time when it happens, I can still use my wolf and raptor’s moves, but no other actions.

Hey, Welcome to the forum…

Probably a good idea to see if the same thing still happens after the 0.8.3 patch dropping on Friday… No point in debugging it now that the devs have confirmed that they are including controller updates then…

Obviously if this still happens after, then it would be good to confirm here…

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.