Compatibility Report

I'm getting an error when launching: "Launch Error. Failed to get the process' path". Have to force quit the application.
This is with an up to date Arch Linux install. Tried various proton versions, GE proton, etc.

GPU: RX 7800XT
Video driver version: Mesa 25.0.4
Kernel version: 6.14.4-zen1-1-zen
Proton version: GE-Proton9-27

Proton log: steam-2427520.log

[EDIT] Another error pops up sometimes:

Fatal Error

The game has crashed, and terminated with exitcode: 208.

SID: d090se3afpm02932gukg
TID: 937923501768735400

[EDIT 2]

Moving the game from an NVME drive to a SATA drive seemed to fix this error, for some reason. Now I have crashes during tutorial.

I get the same freeze after about 1-2 minutes.

Arch Linux/RX 7800xt. Tested with Proton 9.0-4, 10.0-1, Experimental, Hotfix and Proton-GE

It seems to happen ~10s after you kill the first enemy.

It doesnt seems to matter what you do before encountering that enemy (or the time taken doing so)

froze right away when starting the tutorial for me

I'm getting a "Failed to install dependencies" error when launching the game with proton 10 & experimental, with EAC's windows being all black.

I've tried moving the game to an ext4 drive but it changed nothing
Maybe it's an nvidia issue?

System Information

• GPU: RTX 2080
• Video driver version: nvidia 575.51.02
• Kernel version: 6.14.4-zen1-1-zen
• Link to full system information report as Gist: https://gist.github.com/Lifeismana/47f9a8d37fad001e76f1b7e41f562e05
• Proton version: Proton 10 Beta
  steam-2427520.log

For me, it freezes anything from a few seconds to almost 5 minutes into the tutorial, i think the issue might be related to these log messages:
6056.345:01e4:0234:trace:seh:sigsys_handler SIGSYS, rax 0x95, rip 0x70000153067e.
6056.345:01e4:0460:trace:seh:sigsys_handler SIGSYS, rax 0x2f, rip 0x7000006b9578.
6056.346:01e4:0460:trace:seh:sigsys_handler SIGSYS, rax 0x85, rip 0x700000765258.
6056.346:01e4:0460:trace:seh:sigsys_handler SIGSYS, rax 0xd7, rip 0x700001423361.
6056.346:01e4:0460:trace:seh:sigsys_handler SIGSYS, rax 0x85, rip 0x700000765258.
6056.346:01e4:0460:trace:seh:sigsys_handler SIGSYS, rax 0xd7, rip 0x700001432cdf.
6056.346:01e4:0460:trace:seh:sigsys_handler SIGSYS, rax 0x15, rip 0x70000140a746.
6056.346:01e4:0460:trace:seh:sigsys_handler SIGSYS, rax 0x15, rip 0x7000015493b1.
6056.360:01e4:01f8:trace:seh:sigsys_handler SIGSYS, rax 0x84, rip 0x700000765258.
6056.361:01e4:01f8:trace:seh:sigsys_handler SIGSYS, rax 0x36, rip 0x70000159871b.

altho not sure.
Im using fedora 41 and ive tried Hotfix, Experimental, GE, (all the same issue) and stable (didnt boot at all).

Getting the same hard freeze 2-5 minutes in. Managed to get past the first tutorial enemy but nothing more. Other than the freeze, game runs smooth as butter.

Pop!_OS/RTX 4070. Tried 9.0, Experimental and Hotfix

Crash a minute into the tutorial.

CPU: AMD Ryzen 9 5950x
GPU: NVidia RTX 3090
OS: Fedora 42 Workstation
Kernel: 6.14.4-300.fc42.x86_64
Runner: stable, proton10.0-1

Notable logs from dmesg:

[ 3443.351877] warn_bad_vsyscall: 7 callbacks suppressed
[ 3443.351880] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:be880a
[ 3443.430904] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c069a0
[ 3443.451591] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c04aea
[ 3443.488490] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c0658b
[ 3443.589879] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c06c0f
[ 3443.839153] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c69a48
[ 3443.882132] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c54e84
[ 3443.973668] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c5a43b
[ 3444.144186] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c62982
[ 3444.210152] PioneerGame.exe[63155] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000006c1f8c cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c5958f
[ 3462.357999] umip_printk: 21 callbacks suppressed
[ 3462.358002] umip: wine_threadpool[63498] ip:700001530b62 sp:ee69d340: SMSW instruction cannot be used by applications.
[ 3462.358006] umip: wine_threadpool[63498] ip:700001530b62 sp:ee69d340: For now, expensive software emulation returns the result.
[ 3464.455719] umip: wine_threadpool[63334] ip:700001530b62 sp:844ed340: SMSW instruction cannot be used by applications.
[ 3464.455725] umip: wine_threadpool[63334] ip:700001530b62 sp:844ed340: For now, expensive software emulation returns the result.
[ 3466.459561] umip: wine_threadpool[63497] ip:700001530b62 sp:eb39d340: SMSW instruction cannot be used by applications.

For me it freezes in the intro cutscene after about a minute.
If I don't go forward on the initial welcome page, it freezes there instead.
I think the original description is accurate : it doesn't matter what you're doing, the game just freezes after some time, even if you just don't touch anything after launching the game and stay on a menu.

@Lifeismana that is a different issue, try the solutions on https://www.reddit.com/r/linux_gaming/comments/1cvrvyg/psa_easy_anticheat_eac_failed_to_initialize/

@mrvictory1 Thank you! that indeed fixed that error. forgot that eac doesn't like the wayland sdl video driver config unsetting it fixed my issue

I am also freezing 2-3 minutes after launching the game, doesn't matter where in the game I am.
Currently running Fedora on a 5900x, 7700xt, and 64gb 3000mhz ram.

It's not the end of the world if it doesn't get fixed as I have a fairly up to date Windows partition, but it's definitely an issue.

Not sure what would be relevant, but here are some lines I picked out:

20008.597:0204:0250:fixme:process:NtQueryInformationProcess (0xffffffffffffffff,info_class=88,0x2b68e6c0,0x00000038,0x2b68d6c0) Unknown information class
20010.511:0204:0328:trace:seh:dispatch_exception code=c0000005 (EXCEPTION_ACCESS_VIOLATION) flags=0 addr=00006FFFFBCB3BD0
20010.908:0204:0234:fixme:process:NtQueryInformationProcess (0x4a4,info_class=64,0x2650e6c0,0x00000060,0x2650fbe0) Unknown information class
20042.537:0204:03cc:warn:vkd3d-proton:vkd3d_view_map_create_view: Intense view map pressure! Got 1024 views in hash map 0000000013cfd4b8. This may lead to out-of-memory errors in the extreme case.

steam-2427520.log.gz

Notable logs from dmesg:

Doesn't seem relevant, I can get the same warnings with The Finals (most similar game to this, tech-wise)

I got into the tutorial, was able to search a couple of containers then the game crashed after I got shot at by an npc

From my own multiple tries, action or state in the game is not relevant, only timing. The game seems to crash around 5 minutes after launch, regardless if you're still in the menu, in the video or playing the tutorial (no matter how far you go).

Ubuntu 24.04.1 LTS, AMD Ryzen™ 9 7940HS, RTX4060 mobile max-q.
Tested on proton hotfix, on wayland and x11

Same issues, tried changing the settings from the default and it locks up no matter what changes I make. Also, the changes don't save between crashes.
Proton GE 9-27 and Proton Experimental (testing more and crossing fingers)

i5-9600K
RX6600
Nobara 41
(The Finals has ran mostly smoothly for me since day 1 on same machine.)

edit - switched to Proton Hotfix.
made it through the opening cinematic, made no settings changes and got past the first enemy, breeched the door, got knocked, started the bandage part of the tutorial... then crashed out trying to search the dumpster in the first room.

Can you try downloading the Proton EasyAntiCheat Runtime in steam, and setting the path manually with PROTON_EAC_RUNTIME=actualpath

Can you try downloading the Proton EasyAntiCheat Runtime in steam, and setting the path manually with PROTON_EAC_RUNTIME=actualpath

Still freezes after the 5 minutes mark no matter what.

made it past the tutorial somehow, still freezes after x minutes though. (latest patch)
Bazzite and downloading the Proton EasyAntiCheat Runtime in steam, and setting the path manually with PROTON_EAC_RUNTIME=actualpath + Proton Hotfix

made it past the tutorial somehow, still freezes after x minutes though. (latest patch)

I played a bit on Windows, and cleared the tutorial. You can load back up on Linux, and queue up for actual games, but even then you will still freeze after a few minutes.

I played a bit on Windows, and cleared the tutorial. You can load back up on Linux, and queue up for actual games, but even then you will still freeze after a few minutes.

I did the same thing thinking that the tutorial itself was causing some issues as it is brand new, and I saw that Tech Test 1 performed well on Linux. Was still crashing for me in the main menu afterwards.

Issue is clearly not tied to doing something specific, seems to just crash at random moments.

+1 For this issue

https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845152349

https://steamcommunity.com/app/2073850/discussions/0/601903207934868986/ same there on THE FINALS

This seems to be working on the latest Proton Experimental bleeding-edge. https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845615254

This seems to be working on the latest Proton Experimental bleeding-edge. [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845615254)

Thanks for update

FYI Proton Hotfix also has the needed fix to fix the crash
if you don't have it already installed, copy paste this in your web brower: steam://launch/2180100

Tested it and i was able to play for more than 5 min

The game isn't freezing anymore, but performance has taken a major hit compared to Windows. I'm running 1440p high with FSR on quality on Windows, getting around 90 to 100 fps, but on Linux on the same settings(but with FSR on balanced) I am getting around 30 to 40 at the same settings.

The game isn't freezing anymore, but performance has taken a major hit compared to Windows. I'm running 1440p high with FSR on quality on Windows, getting around 90 to 100 fps, but on Linux on the same settings(but with FSR on balanced) I am getting around 30 to 40 at the same settings.

amd, nvidia or intel?

amd, nvidia or intel?

All AMD, 5900x and 7700xt

I'm having the same window mouse focus issues in ARC Raiders as I have in Hunt Showdown, running Proton Experimental/10

https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2844906571

Proton 9 working ok. But still has the crash

It seems like also voice chat is broken? I can't hear or speak in VC. Icons next to players, including myself, show a crossed out speaker symbol. The game defaulted to "PulseAudio Input/Output" in the voice chat settings. Tried changing it to my headset speaker/mic, but that didn't work either.

I'm running NixOS with pipewire, and pipewire-pulseaudio:

services.pulseaudio.enable = false;
security.rtkit.enable = true;
services.pipewire = {
    enable = true;
    alsa.enable = true;
    pulse.enable = true;
};

Replying to https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-2846755139

Works fine for me.

Works fine for me.

What is your audio setup? Pipewire, Pulse?

Works fine for me.

What is your audio setup? Pipewire, Pulse?

Pipewire, pretty much standard as it comes in fedora 41.

The game isn't freezing anymore, but performance has taken a major hit compared to Windows. I'm running 1440p high with FSR on quality on Windows, getting around 90 to 100 fps, but on Linux on the same settings(but with FSR on balanced) I am getting around 30 to 40 at the same settings.

Do you have 2 EAC windows popping up at start instead of just 1?

Do you have 2 EAC windows popping up at start instead of just 1?

Yes, I do, two terminals and one game window

Do you have 2 EAC windows popping up at start instead of just 1?

Yes, I do, two terminals and one game window

Do you remember if only 1 instance was opening before?
I'm asking this because I'm having the same issue on THE FINALS, and I don't know how I did avoid it, but I managed at some point (closing the game through steam, restarting, closing it from menu, etc. I really don't know which combo made it through), to make it start with only 1 EAC launching. And on this particular gaming session, I had zero stutters (this is what I personally face since 2 days), just like always before.
So I'm really wondering if EAC isn't the culprit for my case (and maybe yours?), be that was just a blind guess to be honest.
If I find anything, I'll share it!

Do you remember if only 1 instance was opening before? I'm asking this because I'm having the same issue on THE FINALS, and I don't know how I did avoid it, but I managed at some point (closing the game through steam, restarting, closing it from menu, etc. I really don't know which combo made it through), to make it start with only 1 EAC launching. And on this particular gaming session, I had zero stutters (this is what I personally face since 2 days), just like always before. So I'm really wondering if EAC isn't the culprit for my case (and maybe yours?), be that was just a blind guess to be honest. If I find anything, I'll share it!

I don't think it was happening before, but I'm not sure. I wasn't having any issues with The Finals, although I haven't played the mid season update on Linux yet as I have been staying on Windows for the Arc Raiders Playtest.

Does anyone else experience weird texture loading issues like trees or rocks despawning, then spawning again, changing texture to different LOD levels right in front of you etc?

I also do on THE FINALS since those same last 2 days (in addition to the slight cyclic stutters)! Like the trees rendering well only when getting closer, despite setting view distance to epic.
Seems something is wrong with proton/EAC

Does anyone else experience weird texture loading issues like trees or rocks despawning, then spawning again, changing texture to different LOD levels right in front of you etc?

Does anyone else experience weird texture loading issues like trees or rocks despawning, then spawning again, changing texture to different LOD levels right in front of you etc?

+1 for this, I almost experiencing this. Someone posted on the Arc Raiders subreddit that mentions LOD issues so might not be fully a proton issue

From my experiments this is what I found for THE FINALS:

• Proton 10 beta, Proton latest stable, Proton experimental bleeding-edge, Proton Hotfix:

  • no game crash
  • but EAC launching twice, leading to stuttering

• Proton experimental bleeding-edge-9.0:

  • game crashes after game launch, or even in the lobby
  • no double instance of EAC, so no stuttering, the game runs butter smooth as it should

• Proton 9.04:

  • game doesn't launch at all

• Weird textures/blurring issue:

  • isn't Proton-dependent
  • distance level has no effect
  • trees LOD has no effect
  • CNN vs Transformers has no effetc
  • can be a bit mitigated by setting global illumination detail to epic, but remains still

Actually tested with 10.0-1 Beta and it didn't crash (at least after a few minutes in the main menu). But double EAC still, idk what's going there.

Ok, seems to confirm thx for the feedback!

ALL OTHER VERSION OF PROTON (GE, 9, 10.0 Beta, Experimental, Bleeding Edge, etc) = Crash within 1-5 minutes.

Proton Hotfix = Crash within 5-20 minutes.

Okay for some reason Proton Bleeding Edge seems to be working when it wasn't yesterday.

Can confirm the game runs fine on bleeding edge. 3h without a crash, no noticeable instability and performance is decent.

Trying the latest playtest i am getting a eac error , i don think it is on my end as i was just playing the finals for 5 hours and had no issues with that game, RX 6700 10GB, Cachyos, Kernel 6.17.3, Mesa 25.2.5, Proton Experimental, Experimental(bleeding edge), Latest GE-Proton and Cachy Proton, have all the same problem.

Logs

steam-2427520.log

EDIT: FIXED, had to uninstall and redownload the game

Not let in through Steam yet. Via Epic / Heroic and Proton-GE that it defaults to, seeing crashes too.

Played one round just fine till extraction.
The next round I played barely 2 minutes and crashed.
Rejoined twice and immediately crashed again.

So possibly it's triggered by a specific location / game state?

What's the best source to download alternative Proton builds to test?

Replying to https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3415799164

Grab bleeding edge proton experimental, put it in the heroic runner folder if you can and try that would be best for now

Edit: Better way, in heroic go to settings, advanced, allow using valves proton builds to run games

At the moment starting up from Heroic seems to have issues with Proton Hotfix and Experimental

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
0024:err:steamclient:steamclient_init unable to load native steamclient library
0024:err:msvcrt:_wassert (L"!status",L"../src-lsteamclient/steamclient_main.c",375)

Edit: could not get regular Valve Proton builds to run. Probably to do with UMU vs steam runtime issues, or steam flatpak runtime discovery, or being Epic Game Store auth tokens.

Got the playtest invite on Steam now, so trying from there. 🤞

Through Steam it defaults to Proton Experimental, so far no crashes on that.
That said, I think the game also got a new version released. Can't be sure which addressed it.

But so far so good out-of-the-box on Steam.

Unsure if I should be concerned over this graphical bug or not.

Ok, I have no idea what is going on. I added and removed the flag PROTON_USE_WINED3D=1 and it uhh, got a little better?

And this is with Proton 10.2 Beta with the flag removed

Replying to https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3417686113

What is the hardware on this machine? The distro, mesa or nvidia driver version and kernel

And this is with Proton 10.2 Beta with the flag removed

What is the hardware on this machine? The distro, mesa or nvidia driver version and kernel

Somehow this runs on onboard graphics smoothly

• OS: Kubuntu 25.10
• Kernel: 6.17
• CPU: Intel i5-11500
• GPU: UHD Graphics 750 (Integrated)
• RAM: 32GB DDR4 Dual Channel
• Mesa Version: 25.2.3

Replying to https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3417964061

It would be good to report this issue in mesa aswell as a anv bug so intel developers can take a look, since this is a test i doubt they will be able to solve this issue in time but still would be good to report it so when the game does release it can be fixed quicker

https://gitlab.freedesktop.org/mesa/mesa/-/issues

Mostly works fine but crashes every 2-3 runs for me. Not sure how to effectively debug it.

CPU: AMD Ryzen 7 5800X3D 8-Core
GPU: NVIDIA GeForce RTX 4070 Ti SUPER
GPU DRIVER: NVIDIA 580.82.09
RAM: 32 GB

Mostly works fine but crashes every 2-3 runs for me. Not sure how to effectively debug it.

CPU: AMD Ryzen 7 5800X3D 8-Core
GPU: NVIDIA GeForce RTX 4070 Ti SUPER
GPU DRIVER: NVIDIA 580.82.09
RAM: 32 GB

PROTON_LOG=1 %command% wait till it crashes, post the log here that will be in the home folder

EDIT: there was a update for the game fixing some crashes so maybe see if that fixes the issue or not

Pop!_OS 22.04 LTS
Proton Experimental & Hotifx

Yesterday the game was running fine albeit there was a couple of crashes when opening settings.
After today's patch the game crashes on launch with the following error:
Wine C++ Runtime Library
Expression: "!status && "vkCreateComputePipelines""

I think I had the same issue as @imthatgin, was getting a consistent crash every 30-40 minutes regardless if I was in-game or in the menu, I got the Proton log and noticed the crash looked to be related to mapping memory, I then saw the warnings at the top:

WARNING: Low file descriptor limit: 4096
WARNING: Low /proc/sys/vm/max_map_count: 65530 will prevent some games from working

I'm on Gentoo so these are not setup by default. After setting them up, all is good.

If anyone is getting a consistent time based crash, make sure these are set properly and don't be a fool like me.

For completeness sake here is the log for when it crashes: steam-2427520.log.gz

@misterj05 Can confirm, also on gentoo and also crashes every 30-40 mins. I only have

WARNING: Low /proc/sys/vm/max_map_count: 65530 will prevent some games from working

in the Proton log, unfortunately can't double check if it works fine with increasing that value anymore now that the server slam is over.

The VM Max map count has been changed on many Linux distros to compensate for games that need a lot of that, on Gentoo you the user should know how to change this if this problem occurs, this happens on the finals aswell and to increase it manually this what you do, this value is what the steamdeck uses so it has no problems.

To increase your vm.max_map_count do this

Open your terminal

sudo nano /etc/sysctl.d/vm.max_map_count.conf

Add this value to this config

vm.max_map_count=2147483642

Ctrl-x, y, enter to save the file

Reboot your system

For Gentoo this might be different and so you should be checking the Gentoo documentation for how to increase it manually if available.

Playing on Friday (see https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3416521816 for timestamp) I hadn't encountered the mapping limit issue even after longer sessions.

Being on Fedora my limit is higher than the 65k.

$ cat /proc/sys/vm/max_map_count
1048576

Also not encountered the yellow screens from https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3417647423

With my setup being

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Graphics Platform: Wayland

Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon RX 6800 XT
    Driver: amdgpu
Kernel Version: 6.16.12-200.fc42.x86_64 (64-bit)
Mesa: 25.1.9 (LLVM 20.1.8)

Under "Proton Experimental" with steam release info

App ID: 1493710
Build ID: 20432161
Installed content updated: Oct 18, 2025 at 12:02 PM

Build link

Replying to https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-2842109929

On Arch + Wyland (Omarchy) hat to add this to the launch options to avoid "Failed to initialize dependencies"

unset SDL_VIDEODRIVER; %command%

Pop!_OS 22.04 LTS Proton Experimental & Hotifx

Yesterday the game was running fine albeit there was a couple of crashes when opening settings. After today's patch the game crashes on launch with the following error: Wine C++ Runtime Library Expression: "!status && "vkCreateComputePipelines""

Hello @lsahnicne, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

The issue persists on release version. Attaching previously requested information.

steam-1808500.zip

https://gist.github.com/lsahnicne/dd7bc5d20a68d9aa918cca6483344287

@kisak-valve should we rename this issue now that the game is out, or open a new thread? The full game is a different app id too.

Constant crashes after a few minutes. Can't play. Void Linux. Tried Hotfix, Experimental, and Experimental Bleeding-Edge. Tried Steam overlay enabled/disabled.

# /etc/sysctl.conf
fs.file-max = 524288
vm.max_map_count = 1048576

$ ls /var/service/
NetworkManager  agetty-tty1  agetty-tty2  agetty-tty3  agetty-tty4  agetty-tty5  agetty-tty6  alsa  bluetoothd  dbus  elogind  libvirtd  nanoklogd  polkitd  socklog-unix  udevd  virtlockd  virtlogd

Running PipeWire at user level, Herbstluftwm (Xorg).

steam-log.tar.gz

Steam Runtime System Information

Played quiet a lot yesterday using Proton Experimental, including longer sessions (>3h) and in raid everything worked fine after setting the file descriptor limit and max_map_count as indicated by the error message from the proton log.
I used the settings as configured by Arch (https://gitlab.archlinux.org/archlinux/packaging/packages/filesystem/-/blob/044995ce4cc6704e315d285dc2828cc0d026789a/sysctl). They include links to rationales for the values in case someone wants to know more.

I only have two remaining issues:

• I can't select FSR(3) as the Resolution Scaling method in the graphics settings. Only TAAU and TSR can be selected even though the pop-up on the setting says FSR 3 should work on supported hardware (I'm using a RX 9070, Mesa 25.2.2, kernel 6.16.7).
  Is this something that should work in general and is an issue with the game or is FSR not supported at all via Proton? I couldn't really find any clear info on this.
• Significant audio crackling during cinematics. Ingame seems fine, but all cinematics suffer from this. Is there a specific log type I can capture to try to figure out what's causing this?

Replying to https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3472822555

Working for me on a RX 6700 10GB on cachy with normal experimental on mesa 25.2.6, i dont experience audio crackling, i do use LAVD as the scheduler so maybe thats why i dont experience any problems with that as it prioritizes the game over other processes and tries make it low latency as possible with the frame time