Hello @BreadlyUwU, we're using one issue report per unofficially supported game title. Closing as a duplicate of https://github.com/ValveSoftware/Proton/issues/167#issuecomment-2848697558.
Hello @kisak-valve , I think there is a misunderstanding because I directly mentioned #167 at the beginning of this issue and I apologize for the unclear way I did write this issue, but I stated that the problem doesn't affect only the game mentioned in the mentioned issue, but also another title such as Celeste (app-id: 504230) and now also Tinykin (app-id: 1599020) that I tested against Proton Experimental right after creating this issue, with the pretty same result as with Warframe.
And I have reason to believe that this list will grow pretty indefinitely if I decide to playtest every game on my Steam library against Proton Experimental (but I will gladly test a good sample of them if that can help)
Maybe https://github.com/ValveSoftware/Proton/issues/150#issuecomment-2849400921 is also affected by this?
I believe Rising Storm 2: Vietnam https://github.com/ValveSoftware/Proton/issues/2726#issuecomment-2848721547 and Hunt: Showdown 1896 https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2843809536 are also impacted by this (and probably many other games). For visibility - we are looking into this and hope to have a fix out soon :)
Thanks to all involved in fixing the issue.
I want to add that for Rising Storm I tested a QWERTY US layout, and I can reproduce the issue linked above too so it doesn't seem to be AZERTY specific in this case (I didn't test the other game with QWERTY layout yet).
@BreadlyUwU @Zorrototo There were a couple of missing patches that just got pushed to experimental-10-bleeding-edge branch -- could you please try the bleeding-edge branch and see if that fixes the keyboard binding issues with various layouts?
I have the same issue with "é" (on AZERTY) on deadlock where last week the keybind was working fine, and today it doesn't work anymore (work fine in console tho), i have the issue on the hotfix, experimental and 10 beta branch, proton 9 is working fine.
@trapping703 did you specifically try the experimental bleeding-edge beta branch? None of the other branches you mentioned have the potential fix I'm referring to.
@alasky17 Hello, sorry I needed one hour to figure out how I was supposed to get the bleeding-edge version of proton-experimental
And the answer is yes, the problem seems to be fixed with this branch, at least with #167 with Azerty (Alternative) 😀
Edit: Also fixed with Celeste, I can suppose that the fix will also do the work for #2726 and #3898
did you specifically try the experimental bleeding-edge beta branch
To use it, go to the properties of Proton Experimental in your library (use the search bar to find it), select the beta tab, and then select bleeding edge from the drop down. To revert, do the same but clear the beta dropdown.
@alasky17 Working fine on deadlock with the bleeding-edge version Thank you !
Rising Storm 2 still has the problem with all keys recognized as NUM LOCK, maybe it is a different issue then? Tested Bleeding Edge Experimental and latest Proton 10 https://github.com/ValveSoftware/Proton/releases/tag/proton-10.0-1d
Red Dead Redemption 2 and Hunt Showdown are working correctly now.
Thanks!
Using programmer DVORAK, I still can't map most of my number row in hunt. As outlined here: https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2856207972
I've also played into the Mycopunk Demo yesterday - and while it auto mapped the move buttons to my equivalents of wsad - I could not remap the number row, same as in hunt.
I know, that this was a problem in deadlock, some months back too, when I tried to play that. But I haven't circled back to that yet to test. Was kinda hoping the dvorak improvements would take care of it :)
For anyone who stumbles across this issue - there is a fix in Proton 10.0-1d and exerimental-bleeding-edge (and the next experimental release, currently it is not fixed in experimental-10.0-20250430 which is live on the main branch) which seems to fix most of the keyboard binding issues, especially with the French keyboard layout. I'm still investigating the remaining issues from @Zorrototo and @razzeee.
thanks for looking into this @alasky17
I've just tried deadlock again with Proton 10.0-1 (beta) and I'm also not able to map the number row, beside the some characters, I've mentioned above.
thanks for looking into this @alasky17
I've just tried deadlock again with Proton 10.0-1 (beta) and I'm also not able to map the number row, beside the some characters, I've mentioned above.
The fix should be within proton 10.0-1d which was released very recently
Proton bleeding edge behaves the same with Deadlock.
@razzeee I'm seeing the same behavior with Programmer Dvorak on 9.0-4 and 10 ... For me, the 2 key ([) works, but a bunch of the other number keys like 1 (@) 3 ({) 4 (}) do not work, but that is the same on 9.0-4 and 10. Are you seeing something regressive still or is this just a bug with keyboard bindings in Proton generally?
FWIW - I did check Windows and created a custom keyboard layout to match Programmer Dvorak and 1,3,4 etc could be mapped on Hunt Showdown, so I still think this is a Proton bug. I'm just trying to confirm if I'm seeing the same thing or if you are still seeing a regression between 9 -> 10 :)
It's a bug not a regression.
I kinda hoped that the recent wine Dvorak fixes would improve things.
@razzeee Ah I see - I misunderstood. The original regression in this case was actually a missed commit during the rebase -- we just reapplied the same commit we had before, so it was not expected to improve the behavior beyond 9.0. I did test this against Windows and confirmed this is a legitimate Proton bug, not just game behavior. Thank you for the report! We'll look into it :)
every games using proton layer and an AZERTY keyboard are affected, the issue is already present in proton 9
even in version 9.0-4
I'm not sure if it's the same issue, but I've seen something similar recently where any key I try to rebind only rebinds NUM LOCK no matter the key I pressed. This happened in COD: Black Ops, so not sure if this is a WINE bug with NTSYNC or some other issue.
This bug is present in yet more games : Deep Rock Galactic, DRG Rogue Core and C&C tiberian sun also
proton 10.0-1dx3 2025-05proton 10.0-1x2 2025-05proton experimentalx3 2025-05
As reported by @GuardianLiarus in [#167](https://github.com/ValveSoftware/Proton/issues/167#issuecomment-2848697558) about Warframe, on Proton 10 / Experimental a new bug is affecting AZERTY keyboard users, the numbers (except on the numpad) doesn't seems to be recognized anymore as they should.
The bug also seem to affect some other games, on Celeste I'm currently not able to bind any of the 1 to 3 and 5 to 0 keys, and 4 (') is recognized as (") for some reason.
The keybinding is working well on Wine 9-based Proton and the numbers are actually recognized as… numbers, not char (precision: I'm specifically speaking about Celeste here, not Warframe which the fact that it recognize the numbers as special character is (I believe) the expected behavior with this particular keyboard layout), so I don't believe it's a "caused by game" issue.