WASD inputs kick me out of console

[SCREAMING RAT!!!!]

When I interact with a console and I press any directional WASD key to input a button it kicks me out of the console, making it basically impossible for me to complete objectives that require interactions with one.

[Rua]

Same question, now I cant play by myself anymore
Reinstall game / Delete cache config file / Verify game, none of them can solve the problem.
NEW: Unplug my xbox controller, it fixed.

[Emberwen]

I changed the key to press and it worked for a little bit and failed again

[Deonix]

I have the same issue and what i did was to change the interact button from E to F(and changed melee to Q). maybe doing something like that will fix your issue
EDIT: nvm, it broke again

[A Corpse]

I had the same issue. In Options - Controller - Deadzone, crank it to max (0.99) and it stopped the drift and the console disconnections for me.

[76561199634380757]

We've gotten some reports about this. Do you have an analog keyboard by any chance?
It looks like Steam recognizes the keyboard as a controller, causing this bug.

Work around:
You can either change the deadzone, like the "A Corpse" suggested. Or change your Steam settings to mark it as a keyboard (I don't know exactly how, sorry).

[Deonix]

Originally posted by Arrowhead Developer:

We've gotten some reports about this. Do you have an analog keyboard by any chance?
It looks like Steam recognizes the keyboard as a controller, causing this bug.

Work around:
You can either change the deadzone, like the "A Corpse" suggested. Or change your Steam settings to mark it as a keyboard (I don't know exactly how, sorry).

funny thing, that actually fixed it, but my main keyboard wasn't analog, the issue was created from the razr tartarus that i had connected for work reasons; disconecting it returned things to normal

[Burn]

Originally posted by Arrowhead Developer:

We've gotten some reports about this. Do you have an analog keyboard by any chance?
It looks like Steam recognizes the keyboard as a controller, causing this bug.

Work around:
You can either change the deadzone, like the "A Corpse" suggested. Or change your Steam settings to mark it as a keyboard (I don't know exactly how, sorry).

I know this thread is more than a month old, but the issue is active for me too. I don't have an analog keyboard.

Everything was doing fine for my first 20 hours into the game, now suddenly, it does it as being told by OP.

I will try to fix it with modifying the deadzone to 0.99, but it's still an ongoing issue to keep in mind for future quick fixes or patches.

Wish I could help better than that, but that one is a weird problem

[Areliah]

I use a Razer Huntsman V2 Analog Keyboard and i had the same problems. I changed the USB Port from USB 2.0 to USB 3.0 and it works without any problems.

Sorry for my bad english :-)

[El Tigre Stare]

I just had this issue today. What I found was that I had an Xbox Controller plugged into my PC and it was the problem. I could pick up the controller and use the terminal normally. I unplugged the controller mid-mission and tried my keyboard again and it immediately corrected the issue. I saw this Discussion when I was researching the issue. I hope this helps some of you!

[CruisinDelusion]

El Tigre solved my problem - I had an errant xbox controller that even though it wasn't doing anything, it was enough to stop me from using terminals. Unplugging it solved it for me.

[CommanderTom]

Had the same problem with Razer Huntsman V3 pro. Even I play Keyboard only I changed controller deadzone setting. The console input at the terminal works, but the whole game switch to controller mode and the menue can only be used with controller.
Then I disabled the Xbox 360 Controller in the windows device manager. Then the game turns back to keyboard mode and now everything works fine.