test content
Logo
What is the Arc Client?
Install Arc
Key bind set not applied when switching between ground RPG and shooter mode
zegnowaor
Member Posts: 3 Arc User
Hello,
For new characters, I encounter problems with the switching between the RPG and shooter key bind sets for ground action. It seems like the other binding set is not cleanly (or not at all) applied when I switch between the two modes (/ToggleShooterMode). It does not make any difference whether I assign the key binds via the options > key binds window or the chat box commands (/bind, /bind_load_file).
For a test, I "Reset to defaults" the key binds both for RPG and shooter mode. The game was in RPG mode. I opened the key binds options and assigned Q to "Switch Weapon" for RPG mode, and to "Roll" for shooter mode. Then I closed the options window. Still being in RPG mode, I pressed Q and the weapons were switched, which is correct so far. Then, I toggled to shooter mode (by pressing B ) and pressed Q again. Instead of rolling, the weapons were switched again! Looking back in the options window, the key binds were still as I assigned them a few moments earlier. At some point, after further trying with the options window, the game suddenly switched to shooter mode unprovokedly after closing the window (it was in RPG mode before closing the window) and Q caused the character to roll. However, after toggling back to RPG mode, Q still made him roll, instead of switching the weapons.
The options window would sometimes show the wrong mapping until I changed back and forth the selection of the key bind set between RPG and shooter key binds at the top. At one point, the effective bindings got changed as intended after toggling from one mode to the other, but after some more toggling between the modes, the misplaced bindings became effective again.
Since the day I encountered this issue for the first time, I have found out that I can get the correct bindings to come into effect by doing the following:
1. have the key binds window open
2. switch the mode
3. change the key bind set selection between RPG and shooter in the window back and forth once or twice. When gone back to the actually active mode, the correct bindings should be in effect.
But I have to repeat that every time when I want to use the other mode, so this is not an option on a mission, let alone during a fight. It might help to find the issue, though.
One of the new characters in question is Gitek@zegnowaor. But the same issue appears for all new characters that I create. However, the switching does currently work correctly for my older characters, such as Karl@zegnowaor. For new characters, ground action is essentially broken for me.
I have already posted this via the Arc support channel (# 180121-000642). In a reply, I was advised to also post the issue here, so here it goes (actually this is my second attempt because my first post apparently did not appear here). Also I am interested if anyone else has encountered the same problem.
Please let me know if I can assist any further in tracking this down.
Best regards,
zegnowaor
For new characters, I encounter problems with the switching between the RPG and shooter key bind sets for ground action. It seems like the other binding set is not cleanly (or not at all) applied when I switch between the two modes (/ToggleShooterMode). It does not make any difference whether I assign the key binds via the options > key binds window or the chat box commands (/bind, /bind_load_file).
For a test, I "Reset to defaults" the key binds both for RPG and shooter mode. The game was in RPG mode. I opened the key binds options and assigned Q to "Switch Weapon" for RPG mode, and to "Roll" for shooter mode. Then I closed the options window. Still being in RPG mode, I pressed Q and the weapons were switched, which is correct so far. Then, I toggled to shooter mode (by pressing B ) and pressed Q again. Instead of rolling, the weapons were switched again! Looking back in the options window, the key binds were still as I assigned them a few moments earlier. At some point, after further trying with the options window, the game suddenly switched to shooter mode unprovokedly after closing the window (it was in RPG mode before closing the window) and Q caused the character to roll. However, after toggling back to RPG mode, Q still made him roll, instead of switching the weapons.
The options window would sometimes show the wrong mapping until I changed back and forth the selection of the key bind set between RPG and shooter key binds at the top. At one point, the effective bindings got changed as intended after toggling from one mode to the other, but after some more toggling between the modes, the misplaced bindings became effective again.
Since the day I encountered this issue for the first time, I have found out that I can get the correct bindings to come into effect by doing the following:
1. have the key binds window open
2. switch the mode
3. change the key bind set selection between RPG and shooter in the window back and forth once or twice. When gone back to the actually active mode, the correct bindings should be in effect.
But I have to repeat that every time when I want to use the other mode, so this is not an option on a mission, let alone during a fight. It might help to find the issue, though.
One of the new characters in question is Gitek@zegnowaor. But the same issue appears for all new characters that I create. However, the switching does currently work correctly for my older characters, such as Karl@zegnowaor. For new characters, ground action is essentially broken for me.
I have already posted this via the Arc support channel (# 180121-000642). In a reply, I was advised to also post the issue here, so here it goes (actually this is my second attempt because my first post apparently did not appear here). Also I am interested if anyone else has encountered the same problem.
Please let me know if I can assist any further in tracking this down.
Best regards,
zegnowaor
0
Comments
I reinstalled the game today and the issue persists. Moreover, it also affects all of my characters now. The problem appeared only after the second toggling, though.