Batman Arkham Knight

Batman Arkham Knight proton open 4 matching

• Hupro · 2026-05-15 · Batman Arkham Knight
  @kisak-valve I added the logs. I did a run with each Proton 10 and 11 [steam-208650.log](https://github.com/user-attachments/files/27807484/steam-208650.log) [proton11-steam-208650.log](https://github.com/user-attachment...
• kisak-valvemaintainer · 2026-05-15 · Batman Arkham Knight
  Hello @Hupro, please add [`PROTON_LOG=1 %command%`](https://github.com/ValveSoftware/Proton#runtime-config-options) to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log ...
• Hupro · 2026-05-15 · Batman Arkham Knight
  Arkham Knight launches fine for me on Steam Deck OLED and Bazzite however I've noticed some regressions with proton 11 compared to proton 10. First (minor) issue is now when launching the game it flashes a solid full scr...
• Ralkero · 2025-06-13 · Batman Arkham Knight
  > Replying to https://github.com/ValveSoftware/Proton/issues/558#issuecomment-2968700349 Update: I decided to just stop running up against a wall and go with a solution I know works. I reinstalled Windows 10 on a new par...
• Ralkero · 2025-06-13 · Batman Arkham Knight
  > If you look a few posts above you’ll see I had this exact same issue. The fix was doing a clean reinstall of Steam in my case, as it was setting the game’s working directory incorrectly for some reason. After that, the...
• Ralkero · 2025-06-12 · Batman Arkham Knight
  > If you look a few posts above you’ll see I had this exact same issue. The fix was doing a clean reinstall of Steam in my case, as it was setting the game’s working directory incorrectly for some reason. After that, the...
• DeVelox · 2025-06-12 · Batman Arkham Knight
  If you look a few posts above you’ll see I had this exact same issue. The fix was doing a clean reinstall of Steam in my case, as it was setting the game’s working directory incorrectly for some reason. After that, the g...
• Ralkero · 2025-06-12 · Batman Arkham Knight
  > Game works fine here, clean prefix, GE-Proton10-4, Nobara 42, no launch options, AMD gpu. Maybe nvidia specific driver bug? I'll revert to an earlier NVIDIA driver and try again then. Here's hoping.