Can you share a few more details? What exactly do you mean by "doesn't work consistently"? Does that mean the game drops inputs or maybe the controller is not detected on each run?

What controller are you using?

Can you attach a log with WINEDEBUG=+seh,+loaddll,+plugplay,+hid,+xinput when the controller works and when it doesn't?

Answering those questions would help me a lot as I cannot reproduce the problem locally. I've logged about 150h playing repentance with Xbox Series X controller and I never had any issues with it. Thanks in advance!

I am not sure what the exact problem is but maybe it is the one I have. When a controller disconnects with Proton 6.3 it will not be listed in Binding of Isaac: Repetance anymore until the game is restarted. Can I add the variables in the Steam settings or do I need to start the application from the terminal?

@TheFrozenDuck can you describe in a bit more detail what do you mean by "will no be listed"? Maybe it behaves the same on Windows? I can check that.

I have no problem with disconnecting and reconnecting the controller during gameplay. The game prompts me that the controller was lost. After reconnecting and pressing a button I am back to the game.

To get the logs you have to: right click on the game in your library -> properties -> general -> launch options:

PROTON_LOG=1 WINEDEBUG=+seh,+loaddll,+plugplay,+hid,+xinput,+dinput %command%

After starting the game and messing around with the controller you should see a file named steam-250900.log in your home directory. You can just clear "launch options" field afterwards.

will no be listed

When going into the settings of the game you can choose an input method; be it a keyboard, xinput controller, etc.
The controller (a Dualshock 4 in my case that is commonly listed as xinput controller using proton) is not listed in the available input options, if the controller is disconnected and reconnected to the computer.

p.s. logs are following

a Dualshock 4 in my case that is commonly listed as xinput controller

That should not be a thing. It should be recognized as "Wireless Controller" (that's the name Sony gave it). Also hotplugging both xbox and DS4 controllers works for me with Repentance on Proton 6.3-5.

You seeing a DualShock 4 as a xinput controller can mean one of two things:

1. You don't have access to the raw HID device. Steam ships with udev rules (/usr/lib/udev/rules.d/70-steam-input.rules on Arch) that should tag DS4's hidraw* special file with "uaccess". It still should work just fine though.
2. You are using Steam Input (aka Steam's controller mapping) which creates a virtual xinput device. If that's the case you may be hitting this bug. Try waiting ~60s and the device may reappear. You can also try disabling Steam Input (controller tab in game's preferences).

Hello, I would also like to raise an issue for Binding of Isaac: Rebirth - Repentance DLC (Non-native).
Should I use this ticket or create a new one? It's not related to controller specifically, but overall input freezes and FPS drops.

Compatibility Report

• Name of the game with compatibility issues: Binding of Isaac: Rebirth - Repentance DLC (Non-native Win x64 version)
• Steam AppID of the game: 250900

System Information

• GPU: nVidia GTX 1080
• Driver/LLVM version: nvidia 470.63.01
• Kernel version: 5.13.11-1-MANJARO (also tried 5.13.arch)
• Link to full system information report as Gist. (XFCE [Manjaro] / KDE Plasma [Arch], both X11)
• Proton version: 6.3.6., Experimental, (additional note - unofficial Proton GE)

Game log

https://gist.github.com/malfunctioning-object/e4ffeadb304ed17e1a062113d94217f6

Symptoms

Game is being processed differently somehow. It is not as stable as on Mac using CodeWeavers.
Changing rooms takes significant amount of time. Any additional sprite change causes FPS to drop. There are levels that have dropping sprites of leaking water, which also cause FPS drop. When FPS drop, input is not being processed or is just ignored/dropped. It's one of the games that should not belong to "heavy" category, yet caused the most issues.

Disabling V-Sync or lowering the quality doesn't help. Changing nvidia-settings, amount of screens or refresh rates doesn't help.

Reproduction

No additional specific details other than playing the game.

I feel like I got hung on the "FPS drop" terminology. It feels more like a freeze/game being stuck either loading or processing stuff. I used overlay's built-in FPS monitor, even a slight drop (3-15) caused issues with game sense, movement, render.

I would like to post an update to my report.

I guess it is time to put some disclaimers that NTFS driver is not as supported as it may seem. It took a lot of tries and errors, pilling amount of issues, googling, browsing reddit, searching linux gaming discords to finally find those rare comments where people really oppose using NTFS at all.

I had similar symptoms in other games. For example the frame issues or loading issues (initial boot could be counted in minutes, changing levels took literal ages considering the speed of the game) in BPM: Bullets Per Minute? Gone, game is blazing fast. Overall performance issues? Gone. Binding of Isaac: Repentance doesn't suffer from input lag, no loading delays, no stutters or dropped frames. Flawless gameplay. It wasn't an easy choice but at the end a worthy one.

I'm having trouble with this game on the steam deck.

1. Constant crashes, sometimes when entering a new room or floor, or starting a new game
2. Freezes consistently when entering a specific level (the womb on greed), there's still a slight animation on one of the sprites and the background music still plays but the game is unresponsive to any and all inputs and doesn't load the next floor even after >20 minutes.

I've tried disabling all mods and it still happens, tried verifying game integrity, used 3 different proton versions (including Experimental, 7.0-1 and 6.3-8) and even reinstalling the game.
Nothing seems to fix this.

Is there any way to grab logs from the steam deck when it "freezes" like this?

If you need any more information, I'll gladly try to help. Thanks

Edit: managed to find a related dump and I also noticed the logs were absolutely filled with the following:

[ASSERT] - gfx/001.000_Player.anm2: No layer with Id 14

isaacv1.7.7a.0000-20220318-022436-312-316.zip

Compatibility Report

• Name of the game with compatibility issues: The Binding of Isaac: Rebirth
• Steam AppID of the game: 250900

System Information

• an Optimus laptop (Intel GPU + Nvidia GPU), using prime-run to start games and tools
• GPU: GeForce GTX 760M
• Driver/LLVM version: mesa 22.1.2-1 / nvidia 470.129.06-10
• Kernel version: 5.18.7
• Link to full system information report as Gist:
  • without prime-run: https://gist.github.com/bkosowski/4cfe561d35a31d49c9b04ca519ec7b22
  • with prime-run: https://gist.github.com/bkosowski/124aca8f6db6658914047c8425609ea5
• Proton version: 7.0-3
• __GL_THREADED_OPTIMIZATION=1 LOG_PROTON=1 prime-run %command%

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

After clicking "Play", the button changes for a while (10-15 seconds), then goes to "Play" again. The game doesn't even show up.

Reproduction

I wouldn't know how to reproduce on other systems. If happens to me every time.

steam-250900.log

So the problem happens only when running via prime-run? Looks like it creates a weird mix of GL libraries:

        "glx/gl" : {
          "messages" : [
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-wflinfo: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)",
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-check-gl: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)"
          ],
          "renderer" : "Mesa Intel(R) HD Graphics 4600 (HSW GT2)",
          "version" : "4.6 (Compatibility Profile) Mesa 22.1.2",
          "library-vendor" : "glvnd"
        },
        "egl_x11/gl" : {
          "messages" : [
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-wflinfo: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)"
          ],
          "renderer" : "Mesa Intel(R) HD Graphics 4600 (HSW GT2)",
          "version" : "4.6 (Compatibility Profile) Mesa 22.1.2",
          "library-vendor" : "glvnd"
        },
        "egl_x11/glesv2" : {
          "messages" : [
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-wflinfo: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)"
          ],
          "renderer" : "Mesa Intel(R) HD Graphics 4600 (HSW GT2)",
          "version" : "OpenGL ES 3.2 Mesa 22.1.2",
          "library-vendor" : "glvnd"
        }

        "glx/gl" : {
          "messages" : [
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-wflinfo: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)",
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-check-gl: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)"
          ],
          "renderer" : "NVIDIA GeForce GTX 760M/PCIe/SSE2",
          "version" : "4.6.0 NVIDIA 470.129.06",
          "library-vendor" : "glvnd"
        },
        "egl_x11/gl" : {
          "messages" : [
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-wflinfo: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)"
          ],
          "renderer" : "Mesa Intel(R) HD Graphics 4600 (HSW GT2)",
          "version" : "4.6 (Compatibility Profile) Mesa 22.1.2",
          "library-vendor" : "glvnd"
        },
        "egl_x11/glesv2" : {
          "messages" : [
            "/home/user/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/libexec/steam-runtime-tools-0/i386-linux-gnu-wflinfo: /home/user/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3: no version information available (required by /usr/lib32/libgamemode.so.0)"
          ],
          "renderer" : "Mesa Intel(R) HD Graphics 4600 (HSW GT2)",
          "version" : "OpenGL ES 3.2 Mesa 22.1.2",
          "library-vendor" : "glvnd"
        }
      },

The game crashes somewhere in libexpoxy that's compiled into the game binary.

Backtrace:
=>0 0x00000000 (0x00e6fa34)
  1 0x009b0eb1 epoxy_gl_version+0x26b31() in isaac-ng (0x00e6fa80)
  2 0x00881db8 epoxy_handle_external_wglMakeCurrent+0x47ab28() in isaac-ng (0x00e6fee8)
  3 0x009d3576 epoxy_gl_version+0x491f6() in isaac-ng (0x00e6ff30)
  4 0x7b62ddb0 ActivateActCtx+0x23420() in kernel32 (0x00e6ff48)
  5 0x7bc5d2e7 A_SHAFinal+0x3ccc7() in ntdll (0x00e6ff5c)
  6 0x7bc5da90 A_SHAFinal+0x3d470() in ntdll (0x00e6ffec)

Can you capture logs with prime-run and PROTON_LOG=+opengl,+wgl? Is any other OpenGL game actually working for you with prime-run?

I cannot run the game both win prime-run and without it.

The logs:
__NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus="NVIDIA_only" __GLX_VENDOR_LIBRARY_NAME="nvidia" __GL_THREADED_OPTIMIZATION=1 PROTON_LOG=1 PROTON_LOG=+opengl,+wgl PROTON_USE_DXVK=1 prime-run %command%: https://gist.github.com/bkosowski/6eeaedb8d0fae5bd299cfe1dbea48e14

PROTON_LOG=+opengl,+wgl %command%: https://gist.github.com/bkosowski/4fb4ab8ea6d07a4a8de4d1cd2a5e63cc

I can run:
Enter the Gungeon (OpenGL, Linux native)
Mark of the Ninja: Remastered (OpenGL, Linux native)
Never Alone (Kisima Ingitchuna) (OpenGL, Linux native)

I cannot run:
Brothers — A Tale of Two Sons (DirectX 9)
Age of Empires 2: Definitive Edition (DirectX 11)
Spelunky (DirectX 9)

So it looks like I cannot run DirectX games :thinking:

[SOLVED]

(My solution, of course, applies only to my problem, not to the entire thread.)

I removed these two files:
/etc/X11/xorg.conf.d/20-intel.conf
/etc/X11/10-nvidia.conf

The contents of which were:

/etc/X11/xorg.conf.d/20-intel.conf:

Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "TearFree" "true"
EndSection

/etc/X11/10-nvidia.conf:

Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    ModulePath "/usr/lib/nvidia/xorg"
EndSection

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "iGPU"
    Option "AllowNVIDIAGPUScreens"
EndSection

Section "Device"
  Identifier "iGPU"
  Driver "modesetting"
  BusID "PCI:0:2:0"
EndSection

Section "Device"
  Identifier "dGPU"
  Driver "nvidia"
  BusID "PCI:1:0:0"
EndSection

Section "Screen"
  Identifier "iGPU"
  Device "iGPU"
EndSection

Additional information

I backed up and removed these two files (but I did this before and this did not fix the issue):
/usr/share/vulkan/icd.d/intel_icd.x86_64.json
/usr/share/vulkan/icd.d/intel_icd.i686.json

Before the fix, I could run:
Enter the Gungeon (OpenGL, Linux native)
Mark of the Ninja: Remastered (OpenGL, Linux native)
Never Alone (Kisima Ingitchuna) (OpenGL, Linux native)

Before the fix, I could not run:
Brothers — A Tale of Two Sons (DirectX 9)
Age of Empires 2: Definitive Edition (DirectX 11)
Spelunky (DirectX 9)

Now, I can run all games with either of these command run options:
__GL_THREADED_OPTIMIZATION=1 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only PROTON_USE_DXVK=1 %command%
or
__GL_THREADED_OPTIMIZATION=1 prime-run %command%
With the latter allowing Age of Empires 2: DE to run without crashing.

Now, tree /etc/X11 is:

├── mhwd.d
│   ├── intel.conf
│   └── nvidia.conf
├── xinit
│   ├── xinitrc
│   ├── xinitrc.d
│   │   ├── 40-libcanberra-gtk-module.sh
│   │   ├── 50-systemd-user.sh
│   │   ├── 80xapp-gtk3-module.sh
│   │   └── 90xbrlapi
│   └── xserverrc
└── xorg.conf.d
    └── 00-keyboard.conf

Replying to https://github.com/ValveSoftware/Proton/issues/4868#issuecomment-1107648935

Got the same problem on Steam Deck. The issue does not occur with Afterbirth+ though (this DLC works fine), but with Repentance (1426300). Launching the game via Desktop Mode causes the game to crash as well. Log.

Can confirm this with other gamepads (some generic usb gamepad and xbox elite)

The above also happens on my end on my main PC (Arch) with an xbox-like USB gamepad attached, as well as on my Steam Deck without anything plugged in.

This seems to have been fixed by a recent steam update to the game. Dunno what's that about, but hey.

Can confirm its working again

Compatibility Report

• Name of the game with compatibility issues:Binding of Isaac Repentance dlc
• Steam AppID of the game:1426300
  /

System Information

• GPU: intel hd 3000
• Driver/LLVM version: Mesa 23.1.1
• Kernel version: 6.3.6-arch1-1
• Link to full system information report as Gist: hardware-info
• Proton version: Proton Experimental

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

The game has started crashing at random places in the game. This doesn't happen in Proton 7

Reproduction

There doesn't seem to be a predictable pattern, other than when a layout of a level is generated, you get to a certain point, do some action like place a bomb it'll explode and it will crash there. When you hit "new game" the game will no longer crash in the same spot. If you play a lot it will crash pretty consistently, i've had about 10 crashes so far.

steam-250900.log

I've had the above happen to me as well, but only on Proton 8. Switching to Proton 7 fixed it. I have not tried experimental. Running on a Steam Deck in my case.

Don't know if it can be related or not :
#https://github.com/UnderscoreKilburn/repentance-issues/issues/1905

I did not yet open a bug on this repo. Some advice on the best thing to do if this finding is relevant ?

I've got multiple successful runs both via the alternative mother (dross, ashpit) route and the normal one, blowing rocks left and right and I for sure created at least a few bridges and I still could not repro :-(

If someone has reached a point where you can reproduce the issue can you:

1. reach the room that has the repro (AFAIU if you crash you should restart the whole floor, so that should be easy)
2. quit the game
3. backup your rep_persistentgamedata1.dat or similar, you can find it in ~/.steam/root/userdata/$ACCOUNT_ID/250900/remote/ where $ACCOUNT_ID is a set of numbers.
4. make sure that the issue repros when you start from this save
5. attach the save file and describe exactly what to do to crash

Thanks in advance!

@ivyl here you have, is always crashing when you defeat the floor boss, using Proton Experimental.
files.zip

@Relwi is it just me or Binding of Isaac Proton Experimental Bleeding Edge is even more broken, like every proton version, Isaac is getting even more broken

I can't get the game to consistently crash, every time it does, reentering the game it doesn't crash again. The most consistency I get is that it crashes almost always on Ashpit/Mines, usually by pushing a button that creates tiles on the room to walk over, by exploding bombs or when spawning an Angel Deal after beating a boss. It also happened once when entering a previously beaten boss room.

If I ever get it to consistently crash I'll attach my save file here.

Another issue I'm having with the game that I don't know if is Proton related seems to be shader related I think. I used to have more than a 100 mods a couple of months ago and it worked fine. Now having as much as 30-40 mods is enough for the game to stutter briefly when a new effect comes into the screen, the less mods I have the shorter the stutter. I can get it to shorten even further by using Zink, but I doesn't go away, with no mods it plays perfectly. After an effect happens the first time, like entering a given room, spawning an enemy, exploding, etc, it doesn't happen again on the same session. Closing and reopening Isaac makes it stuttery again.

Artifacting in Binding of Isaac Repentance in Proton Experimental and Proton 8.0, the main menu screen is fine, but once you start a new game or load into a new game, a huge black box appears with graphical artifacts making it impossible to play.

@Nyabinary Additionally, you are testing on the steam deck with SteamOS Preview (3.5) (noting for future reference). We have been completely unable to reproduce the issue you are reporting. Could you please get a log by adding "PROTON_LOG=1 %command%" to launch options. By default, log will be located in ~/steam-250900.log.

Also seeing unpredictable crashes on Proton 8.0-4. Here's the log of one of those crashes:

steam-250900.log

@alasky17

Proton 7.0 also has this issue, the image is from Proton-Experimental though, in Proton 7.0 the issue exists, but the issue is much much much rarer than it is on Proton 8.0 and Proton Experimental. Also, it's random on how it works, sometime its artifacts like in the screenshot, or sometimes it's a blackbox covering the whole screen, sometimes it's just a glitchy part at the top.
steam-250900.log
Important to note this on my computer with an Intel CPU 12th gen, I installed and used gamescope though to make it as close as I possibly can to the Steam Deck.

Just updated Proton Experimental ([bleeding edge] branch, available to select on Proton Experimental tool options, BETAS page) has a possible "fix" for those random crashes. Can anyone who was reproducing those confirm if that indeed looks fixed? As I could never actually reproduce the crash even once, while found a possible reason for that.

Just updated Proton Experimental ([bleeding edge] branch, available to select on Proton Experimental tool options, BETAS page) has a possible "fix" for those random crashes. Can anyone who was reproducing those confirm if that indeed looks fixed? As I could never actually reproduce the crash even once, while found a possible reason for that.

I've done 1 run so far and haven't crashed with Proton Experiental - bleeding edge while going to Ashpit/Mines. I'll try 2 more runs after I wake up and report back.

I couldn't test yesterday, sorry for that, but I managed to do 2 other runs today going to the alt paths using Proton Experimental - bleeding edge and I have not crashed a single time, so far it has been pretty stable.

Replying to https://github.com/ValveSoftware/Proton/issues/4868#issuecomment-1751715096

Anyone could reproduce this?

Replying to https://github.com/ValveSoftware/Proton/issues/4868#issuecomment-1712721656

I'm having the same issue with mods

The controls are all semi-inverted when running Repentance+ DLC while using every Proton version (Experimenta, Hotfix, Next) except 9.0-4. Some older Proton versions work too, but they remove the ability to play new online beta

Anyone ever seen something like this or knows how to fix the issue? If I map keyboard keys to the controller buttons - it kinda works, but it's a messy solution and I wish there was something more proper of a fix :(

@omfgnuts could you specify what gamepad you're using? And does forcing steam input in the game properties change anything?

@omfgnuts could you specify what gamepad you're using? And does forcing steam input in the game properties change anything?

Any gamepad actually, I am playing on the steam deck. And even with connected dualsense it is the same. And googling this issue I see that others have it too, and they fix it by selecting the older Proton version, which is not suitable for me. I tried everything with all the Steam Input options available, no effect.

Any other logs I can provide?

@omfgnuts I don't get the issue on deck with its built-in controls on steamos 3.6.22, tried proton 9 and experimental. On desktop, I also didn't have issues with an xbox gamepad, however, when switching to a dualsense I saw the issue on proton 7 and up, this can be worked around by enabling steam input for the game (though you'll lose playstation glyphs).

On deck the dualsense worked for me by default as steam input was already enabled, but disabling it in game properties resulted in the game wrongly detecting that I was holding top left on the left stick.

Are you seeing something different from me? are the deck built-in controls broken for you?

@simifor Are you on the latest Repentance+ (specifically the recent multiplayer DLC)? Because regular Repentance works just fine, and the issue appeared only after Rep+.

I'm also on latest SteamOS 3.8 (but the issue was even on the older SteamOS 3.7 version) With Proton 9 i can play multiplayer but not the Online Daily specifically (which is the last achievement I need), and controls works just fine. When switching to Experimental or any other (even GE Proton) - issue with online daily disappears but controls are all scrambled and options button also connects a second player, without any other controllers connected, and the connected second player controls perfectly (that's crazy!)

I also just tried connecting via Remote Play and use a keyboard - and it works juuust fine, even on Experimental. It's definitely not a Steam Input/Gamepad/Game issue, but i bet it's somewhere in Proton

@omfgnuts I have the binding of isaac rebirth, and repentance dlc, I see no mention of multiplayer in-game

@omfgnuts I have the binding of isaac rebirth, and repentance dlc, I see no mention of multiplayer in-game

ahh, that's probably the issue. the Repentance+ DLC is free on Steam. If you have a chance - do check if you have the same issue (my friend has exactly the same prob). Maybe you'll find a workaround (playing on a keyboard via remote play is too laggy :( )

@omfgnuts yeah I can see the problem with deck's controls now. Dualsense worked fine with the game IF steam input is enabled (which would make the game display xbox prompts rather than playstation ones), this is something you can force from the game's properties as a workaround for the time being.

If you want playstation glyphs, which requires disabling steam input, I found that the controller behaved correctly when wired to the steam deck (you can use a usb c to usb c cable if you don't want to dock it), over bluetooth it would behave incorrectly.

@omfgnuts yeah I can see the problem with deck's controls now. Dualsense worked fine with the game IF steam input is enabled (which would make the game display xbox prompts rather than playstation ones), this is something you can force from the game's properties as a workaround for the time being.

If you want playstation glyphs, which requires disabling steam input, I found that the controller behaved correctly when wired to the steam deck (you can use a usb c to usb c cable if you don't want to dock it), over bluetooth it would behave incorrectly.

I also went into the Control Settings ingame, and it shows two virtual gamepads and a keyboard connected, when in reality nothing is connected.

DualSense wired/bluetooth produces the same effect, adds a second player that controls perfectly fine, while the main character all all weird and scrambled :(

Edit: disabling Steam Input and connecting DualSense via cable - works! woo!

The shuffled controller layouts are still present on experimental, and any other proton10 distribution I've tried. The only solution has been to roll back to proton 9. Disabling Steaminput is not an option, especially on the Deck

Same issues here.

Compatibility Report
Name of the game with compatibility issues: The Binding of Isaac: Rebirth (Repentance+ DLC)

Steam AppID of the game: 250900

System Information
GPU: AMD APU (Steam Deck)

Video driver version: Mesa (SteamOS default, latest stable as of June 2026)

Kernel version: SteamOS default (latest stable as of June 2026)

Proton version: Proton 10, Proton 11 (issue); Proton 9.x (works)

Symptoms

• Controller input behaves incorrectly when using Proton 10 or newer on Steam Deck.
• ABXY buttons do not function as expected
• Back button appears non-functional
• Some inputs appear inverted or incorrectly mapped
• Controls overall are inconsistent and unreliable
• The game behaves correctly with Proton 9.x.

Reproduction

• Launch The Binding of Isaac: Rebirth (with Repentance+ DLC) on Steam Deck
• Force compatibility to Proton 10 or Proton 11
• Start gameplay
• Attempt to use ABXY buttons and back button
• Observe incorrect or non-functional inputs