Hey Hans Kristian! Arc Raiders was released a few weeks ago and has been a huge success. The developers support Linux for its anti-cheat, and I've been playing it since its release, but I've noticed some performance issues compared to Windows. It's a UE5 game (in case that's relevant), and I play at 1440p with everything maxed out except for ray tracing. I haven't had any crashes.

I'm not sure if this belongs here since there's already an open thread: https://github.com/ValveSoftware/Proton/issues/9164. Since it's a DirectX 12 game, I'd like to post it here, just like I did with this one: https://github.com/HansKristian-Work/vkd3d-proton/issues/2671

The thing is, I'm using Proton GE 10-25, experimental (20251106), and Proton-Cachyos (20251107). The game runs well with all of them, but the performance is somewhat lower than on Windows. The main menu runs at around 96-100 FPS on Windows and around 114 FPS on other platforms. During gameplay, the FPS is higher on Windows and it's smoother with less stuttering. I haven't had any crashes and I've played for 60 hours, but it would be great if something could be done. Since I'm using version 20251107, I haven't received all the improvements from vkd3d-proton 3.0 that came out a few days ago, so I might wait to try those builds because they could improve performance. What do you think?

Another thing to keep in mind, which many people complain about, is that if you use the variable:

PROTON_ENABLE_WAYLAND=1

keys 1, 2, and 3 don't work to change weapons and you have to use the mouse. This doesn't happen if I run it without this variable. Finally, if you're searching for a match and you're on another screen and not the main focus of the game, it causes a crash, which is what you see in the image.

And lastly, the sound. There's a problem with the audio crackling in the main menu and during gameplay when game music or sound effects are playing. This can be fixed with the variable:

WINEDLLOVERRIDES="winepulse.drv=d;winealsa.drv=b"

But it would be nice if it worked without that variable. To give a little more information, here's my Pipewire configuration. I use 96kHz, and I think it didn't happen with 44kHz:

{
  "context.properties": {
    "default.clock.rate": "96000",
    "default.clock.allowed-rates": [
      "44100",
      "48000",
      "96000",
      "192000"
    ],
    "default.clock.min-quantum": "1024",
    "default.clock.max-quantum": "2048"
  }
}

That's about all I can say. I hope you can tell me something about this so I can... Fix it, thanks for your work!

Software information

Name of the game, settings used etc.

System information

• GPU: AMD RX 9070 XT 16Gb
• Driver: mesa 25.3.0
• Wine version:
• VKD3D-Proton version: Test on Proton GE 10-25, and Proton-Cachyos (20251107) and proton experimental (20251106)

Log files

Please attach Proton or Wine logs as a text file:

• When using Proton, set the Steam launch options for your game to PROTON_LOG=1 %command% and attach the corresponding steam-xxxxx.log file in your home directory.
• When using regular Wine, use wine game.exe > game.log 2>&1 and attach the resulting game.log file.