Page MenuHomeFeedback Tracker

Configure Keybinding screen not functional
Acknowledged, NormalPublic

Description

The Keybinding screen apply button does not work. Further, it clears the controls that were changed and persists this so they are no longer accessible in game, unplayable.

I did this:
Fire mode, X -> Z
Jump, Space -> X
Freelook modifier, Left Alt -> Space

Apply

The error occurs upon clicking Apply. The changed fields are cleared on-screen.

Workaround: Delete local files using Steam -> Verify game files interface

Details

Severity
Block
Resolution
Open
Reproducibility
Always
Operating System
Windows 7
Category
Controls
Steps To Reproduce

Go to keybinding screen

Make changes:
Fire mode, X -> Z
Jump, Space -> X
Freelook modifier, Left Alt -> Space

Click Apply

The error occurs upon clicking Apply. The changed fields are cleared on-screen.

Additional Information

Version: 1.02.150980

Workaround: Delete local files using Steam -> Verify game files interface

Event Timeline

ace402 created this task.Mar 31 2019, 12:23 AM

The keybinding screen is definitely bugged and has been so in all the 1.02 Experimental builds in my experience.

I've had success with saving the keybind changes in the screen after a few tries without having to delete my local files each time. Mainly, I believe, by making the keybind change and then LMB click elsewhere on the screen before pressing Apply. So it's not completely unsuable, but just quite dysfunctional in its current state.

In addition to the problem described by @ace402, I've found that if I change a keybind in the left column while there's a secondary keybind in the right column, the new keybind from the left column is ADDED to the secondary keybind in the right column. I've only been able to fix this by deleting the secondary keybind in the right column first.

Vitdom added a subscriber: Vitdom.Mar 31 2019, 1:39 PM
Geez changed the task status from New to Acknowledged.
Geez added a subscriber: OSH.
Geez added a subscriber: Geez.

Hello ace402.
We have confirmed the issue and it has been scheduled for a fix.
Regards,
Geez