Switching between M+KB and controller occasionally fails to correctly update the on-screen button guide, leading to mixed displays as seen below. This always only affects the runes line. The button guide corrects itself on the next button press, unless the button pressed triggers a rune attack. Inputs work as expected throughout.
I have not figured out how to reproduce this bug. I suspect that the method of triggering the bug is related to rune keys not toggling the layout, but since I can’t reliably reproduce the bug, further testing is difficult.
The bug occurred in Sacrament near the target dummies while testing runes. Not sure if it’s been reported before; the only similar topic concerns rebound rune keys not being displayed correctly.
I am playing through Proton Experimental and using a Nintendo Pro Controller. As such, I cannot furnish a dxdiag file. If further system information is needed, I could supply Steam’s system information.
For the sake of testing, I have played with the Steam overlay on and off, which effected no change. Player.log, Player-prev.log and DataStore can be found here [link], though I have redacted my username, Steam ID, and Amplitude ID from the files.
For other Linux users reporting bugs, it may be of interest to add the location of the requested files to the stickied post:
~/.steam/steam/steamapps/compatdata/1371980/pfx/drive_c/users/steamuser/AppData/LocalLow/Moon Studios/NoRestForTheWicked/