Bindings

[Draeka3]

I currently have an azerty keyboard.

When rebinding, i came upon a problem :

By default (querty)
Walk forward and acceleration are "w"
The equivalent on an azerty keyboard is "z"

However, i can't seem to be able to rebind both to "z"
The same goes for other things that have the same key for two different things.

Weapon slots can't be binded to numbers under the F keys.

[Kyral]

same problem here

[AxHellRetro]

I have the same problem, and for some reason binding the Q key to "walking left" just doesn't work. Anything else works though

[LaW.hp]

same, cant choose dialogue or menu

[AxHellRetro]

Originally posted by Professeur-StrausS:

same, cant choose dialogue or menu

to choose dialogue, use the numbers row above your letters

[Kyral]

Originally posted by AxHellRetro:

Originally posted by Professeur-StrausS:

same, cant choose dialogue or menu

to choose dialogue, use the numbers row above your letters

doesn't work

[Draeka3]

Originally posted by AxHellRetro:

Originally posted by Professeur-StrausS:

same, cant choose dialogue or menu

to choose dialogue, use the numbers row above your letters

Not working for me.
Until fixed all i can do about it is use the controller.

[Amene]

Yea, the only workaround for now is a keyboard with hardware rebinding (like e.g. K70) or AHK (or similar).

There are other issues as well, for example if you are using other key than 'w' for walking forward (I use 'space' or 'ralt' depending on the scheme) you won't be able to move forward during scanning.

[CosmicD]

- using the 1-0- keys for dialog options in azerty doesn't work because these are internally hardcoded to the American keyboard layout, and even though you can change these keys for weapon slots and they work, they don't work for dialog options, those are in other binding categories.

Same with vehicle hotkeys, you can't bind the forward key to the same forward key as FPS movement. because not only will they switch to a weird key, if you try to manually bind accelerate in the file AHGameSettingsSubsystem.ini , it won't work, and the left key is hardcoded to Q, because when you're in a vehicle, the game uses another bind scheme that isn't even defined in that ini file so you can't change it.

I often notice that these things happen in beta versions because developers have other priorities than, but it's a bit annoying when a released game, the developers haven't made all bind options player-facing.

Menu navigation is often not reconfigurable either, but I've gotten used to the fact that I have to often press Q and E to navigate through menu tabs.

But I feel that they have to make vehicle movement rebindable and make sure that, if you don't have hotkeys for left and right when you are in a vehicle, at least let's adopt the keys you have set on foot.

Also weird: if you rebind the weapon slot, you see yellow "missing" symbols for where the &, é,, ",( and § keys are supposed to be. Thank god they do work but, some work has to be done in unreal engine to make the rebinding user experience comfortable for other keyboard layouts.

[Korinth]

I just put my keyboard on qwerty with shift + alt and then everyone works perfectly fine when I play on my azerty, you just need to reember for QTE when they ask you to press Q, it's A

Rebending is a mess so just do that instead

[CosmicD]

it's only a mess because they don't provide all binding options to be playerfacing and half of it is just hardcoded and can't even be configured in the ini file. It's just a bit frustrating because vehicle left and right also seem to belong to another category of bindings that you can't alter, left and right in a vehicle is hard coded to the qwerty configuration. Also when choice dialogs are going on, you can't move right, because, for some reason, movement keys are also qwerty in that "dialog" state.

I'd find it much more confusing to always have to think about QTE events being other keys because it happens fast. This shouldn't become a routine. I'm just very pragmatic about this.