@kisak-valve Sorry, I uploaded the wrong logs. I just updated them above. Interestingly, somehow I was able to partially load into a multiplayer match this last time, but the game crashed before I could choose a character.

I am also crashing to desktop when trying to load into a multiplayer or singleplayer match, even with DX12 turned off and all low settings.

Here are my system specs, I am using an NVIDIA GPU:
https://gist.github.com/ipkpjersi/8f3de38b976e513026622957a08d2300

I confirm that the game crashes when I try some kind of gamemode.

steam-1237950.log
steam-1237950-crash.log

Gamepad is also not working. Some inputs are swapped, others aren't there.

This might be a Proton exclusive issue, because I play the Origin version just fine through Lutris.

@ptkato What version of Wine are you using with the Origin version through Lutris? I'll test tonight with older versions of Proton to see if maybe that's the issue...

I had flawless performance using Staging 4.14. I wish I could test with a more recent version, but I'm having problems to download the game; which is kinda ironic, the game works fine but Origin messes up everything.

4.11-13 won't even install origin, so I'm guessing 5.0.9+ is required.

I can confirm that the Origin version works. AMD users usually have to edit the dxvk.conf file to spoof an Nvidia GPU, but that's it, and either way that's not the issue here, because the game won't launch at all without doing that on the Origin version, so this is a separate issue.

I tried running Proton and Battlefront II manually with: STAGING_SHARED_MEMORY=0 WINEPREFIX=/media/user/SSD/SteamLibrary/steamapps/compatdata/1237950/pfx /media/user/SSD/SteamLibrary/steamapps/common/Proton\ 5.0/dist/bin/wine /media/user/SSD/SteamLibrary/steamapps/compatdata/1237950/pfx/drive_c/Program\ Files\ \(x86\)/Origin/Origin.exe and it did not work. I also disabled Steam in-game and Origin in-game which also did not help. I think this is an issue with Proton itself, hopefully it can get patched some day to fix this.

Battlefront II requires a lot more than just that. Look at everything
Lutris does to run it, and even then sometimes it still takes manual
intervention.

On Mon, Jun 22, 2020 at 9:49 PM ipkpjersi [email protected] wrote:

I tried running Proton and Battlefront II manually with: STAGING_SHARED_MEMORY=0
WINEPREFIX=/media/user/SSD/SteamLibrary/steamapps/compatdata/1237950/pfx
/media/user/SSD/SteamLibrary/steamapps/common/Proton\ 5.0/dist/bin/wine
/media/user/SSD/SteamLibrary/steamapps/compatdata/1237950/pfx/drive_c/Program
Files\ (x86)/Origin/Origin.exe and it did not work. I also disabled
Steam in-game and Origin in-game which also did not help. I think this is
an issue with Proton itself, hopefully it can get patched some day to fix
this.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3971#issuecomment-647857712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333KF5SWJFC7YYH4IYLRYAC2NANCNFSM4N34XG3Q
.

Using the latest GloriousEggroll release, I was able to start a couple SP games with no game crash.

I get stuck on updating origin (literally, it loops until it errors, I close out, same thing) using the latest GloriousEggroll release, that's a shame.

Edit: I relaunched Steam and tried again with the latest GloriousEggroll release, I was able to get in-game and get into an arcade match without crashing. I was also able to play Heroes vs Villains online multiplayer as well. Awesome!

Using the latest GloriousEggroll release, I was able to start a couple SP games with no game crash.

Were you having micro stutters as well? In Glorious Eggroll I can play but micro stutter constantly.

Were you having micro stutters as well? In Glorious Eggroll I can play but micro stutter constantly.

I don't think I noticed any, I'll have to see as I play more. This fix mentioned here, making the Origin folder read-only, might eliminate the stutters.

The command for reference:
chmod -R 555 your/path/to/steam/steamapps/compatdata/appid/pfx/drive_c/users/steamuser/Application\ Data/Origin

Were you having micro stutters as well? In Glorious Eggroll I can play but micro stutter constantly.

I don't think I noticed any, I'll have to see as I play more. This fix mentioned here, making the Origin folder read-only, might eliminate the stutters.

The command for reference:
chmod -R 555 your/path/to/steam/steamapps/compatdata/appid/pfx/drive_c/users/steamuser/Application\ Data/Origin

I don't seem to have an application folder? I have Appdata or ApplicationData do you happen to know the appid? The appids I have in the compatdata folder don't match the steamdb id for the game...

Were you having micro stutters as well? In Glorious Eggroll I can play but micro stutter constantly.

I don't think I noticed any, I'll have to see as I play more. This fix mentioned here, making the Origin folder read-only, might eliminate the stutters.
The command for reference:
chmod -R 555 your/path/to/steam/steamapps/compatdata/appid/pfx/drive_c/users/steamuser/Application\ Data/Origin

I don't seem to have an application folder? I have Appdata or ApplicationData do you happen to know the appid? The appids I have in the compatdata folder don't match the steamdb id for the game...
I found the origin folder, forgot it was on another drive still didn't have an application folder I will try that command see if it fixes

@yurgburg then you're looking in the wrong place. It's possible you installed the game somewhere else.

Open Steam, go to the game properties, and look at the local files. You can click to view the local files and it'll open your file manager so you can see where the game is installed. That'll be where you can find the compatdata/appid directory.

You definitely have one matching SWBF2, there's no way you don't (unless you have the origin version, of course).

Run ls /path/to/library/steamapps/compatdata/1237950/pfx/ and paste the output

@yurgburg then you're looking in the wrong place. It's possible you installed the game somewhere else.

Open Steam, go to the game properties, and look at the local files. You can click to view the local files and it'll open your file manager so you can see where the game is installed. That'll be where you can find the compatdata/appid directory.

You definitely have one matching SWBF2, there's no way you don't (unless you have the origin version, of course).

Run ls /path/to/library/steamapps/compatdata/1237950/pfx/ and paste the output

Yeah I found it in my other drive (how silly of me to forget). is there a way for me to copy the path?

What do you mean copy the path? Where is it located?

What do you mean copy the path? Where is it located?

Yeah copy the folder path so I can just paste it into the command ( I am new to ubuntu sorry)

I'm not sure what you're asking...

What are you wanting to copy? What terminal are you using? If you're using regular Ubuntu, it's probably gnome-terminal. You can highlight and right-click and you'll see the menu and you can copy and paste that way in gnome-terminal.

Otherwise, most terminals (also including gnome-terminal) use CTRL+SHIFT+C and CTRL+SHIFT+V for copy and paste, respectively.

I'm not sure what you're asking...

What are you wanting to copy? What terminal are you using? If you're using regular Ubuntu, it's probably gnome-terminal. You can highlight and right-click and you'll see the menu and you can copy and paste that way in gnome-terminal.

Otherwise, most terminals (also including gnome-terminal) use CTRL+SHIFT+C and CTRL+SHIFT+V for copy and paste, respectively.

I want to copy the location of the folder So I don't have to manually type it out in the command prompt. In windows I could just click the path and CTRL + C but it doesn't seem I can do that here. Does that make sense?

@yurgburg You can copy the path to the directory you're in by using pwd.

@kedodrill I don't think that's what they're asking. They're asking how to physically copy (I think?)

@yurgburg In Linux, terminals use CTRL+SHIFT+V for paste (and CTRL+SHIFT+C for copy). But gnome-terminal, the default Ubuntu terminal, you can just right-click and then click paste.

Or you can just open your file browser, go to the folder, and right click on it and hit "Copy." Then go to the terminal and hit CTRL+SHIFT+V, that'll also paste the path.

Look:

Otherwise, like I said, CTRL+SHIFT+C is copy, CTRL+SHIFT+V is paste.

I'm not sure what you're asking...

What are you wanting to copy? What terminal are you using? If you're using regular Ubuntu, it's probably gnome-terminal. You can highlight and right-click and you'll see the menu and you can copy and paste that way in gnome-terminal.

Otherwise, most terminals (also including gnome-terminal) use CTRL+SHIFT+C and CTRL+SHIFT+V for copy and paste, respectively.

I tried copying the path from an open in terminal window and then tried the command and I got this output https://imgur.com/a/k3S8Pjf. Any suggestions?

I did have not great performance and I believe even some microstuttering when I first ran the game, but after I went through a few matches, performance was great and I did not have any other issues when using the latest GloriousEggroll release.

@yurgburg You can copy the path to the directory you're in by using pwd.

Yes that is exactly what I meant! I used the path given and I got no file or directory found. I posted the error in terminal above.

@yurgburg, that's because you can't use spaces in path names.

Put quotations around the path.

so chmod -R -555 "/mnt/New Volume/steamapps/compatdata/1237950/pfx/drive_c/users/steamuser/Application Data/Origin"

For future reference, you can't type spaces with no quotes or escape characters, because that's viewed as a new command/input.

For spaces, either put quotations around the entire path, or use an escape character. Like this: chmod -R 555 /mnt/New\ Volume/steamapps/compatdata/1237950/pfx/drive_c/users/steamuser/Application\ Data/Origin.

Notice how before the space, I put a \. Use either that, or quotations around the full path.

@yurgburg, that's because you can't use spaces in path names.

Put quotations around the path.

Ah okay thank you, that makes sense. I cannot get the game to launch now. Origin will launch and say cant install to this folder, choose new folder or cancel. (usually the game will start by now) and then origin will close and I can hit play again.

@yurgburg It's possible that the game requires more than read-only access to Origin files. Do you know what the permissions were before you changed them? I returned the game, otherwise I'd look for you.

If you aren't sure what the permissions were and the game is still broken after you play with permissions, you can try deleting that folder and re-validating the files on Steam.

@kedodrill every other Origin game runs fine by disabling write permissions to that folder.

@yurgburg It's possible that the game requires more than read-only access to Origin files. Do you know what the permissions were before you changed them? I returned the game, otherwise I'd look for you.

I do not know I tried again and got it to launch but its not responding and looks like this https://imgur.com/a/7Esflaz

@kedodrill every other Origin game runs fine by disabling write permissions to that folder.

I wasn't aware of this, so I guess it's unlikely if that is true, but it's still possible that the permission changes are introducing breakage.

@yurgburg It's possible that the game requires more than read-only access to Origin files. Do you know what the permissions were before you changed them? I returned the game, otherwise I'd look for you.

I do not know I tried again and got it to launch but its not responding and looks like this https://imgur.com/a/7Esflaz

I would try deleting that folder and re-validating the files for the game. If that doesn't work, I'm not really sure. You could try a reinstall as a last option.

I did have not great performance and I believe even some microstuttering when I first ran the game, but after I went through a few matches, performance was great and I did not have any other issues when using the latest GloriousEggroll release.

This is great news! Did you need to restart the game a few times, or was it a single launch with multiple play sessions?

@yurgburg you can just run chmod -R +w /path/to/Origin to undo what you did, that should work until we can figure out why it won't launch after the other command.

@kedodrill every other Origin game runs fine by disabling write permissions to that folder.

I wasn't aware of this, so I guess it's unlikely if that is true, but it's still possible that the permission changes are introducing breakage.

@yurgburg It's possible that the game requires more than read-only access to Origin files. Do you know what the permissions were before you changed them? I returned the game, otherwise I'd look for you.

I do not know I tried again and got it to launch but its not responding and looks like this https://imgur.com/a/7Esflaz

I would try deleting that folder and re-validating the files for the game. If that doesn't work, I'm not really sure. You could try a reinstall as a last option.

Third attempt got it to launch but stuttering is still there. Also strange issue where game will minimize itself unless I double click fast enough inside the window.

This is great news! Did you need to restart the game a few times, or was it a single launch with multiple play sessions?

It was just a single launch, it was much like any other game I've run through Wine - slow at first but as you keep playing, more assets get cached and then the performance is good.

@yurgburg what's your hardware? AMD or Nvidia?

Also, the minimizing should be able to be solved by just alt-tabbing back into the game, right?

@yurgburg what's your hardware? AMD or Nvidia?

Also, the minimizing should be able to be solved by just alt-tabbing back into the game, right?

I have an Nvidia RTX 2080Ti with amd 2700x 32gb ram
The minimizing is NOT fixed by alt tabbing because it minimizes again. I can only get it to stop minimizing if I spam click in the window until it stops. Usually takes about 5 attempts. Multiplayer stuttering isn't too bad just sometimes gets me killed.

Try enabling a virtual desktop, I had troubles with the game window also (Origin version), until I enabled the virtual desktop. You can do so with proton by running winecfg on the game's prefix and setting it from there.

Try enabling a virtual desktop, I had troubles with the game window also (Origin version), until I enabled the virtual desktop. You can do so with proton by running winecfg on the game's prefix and setting it from there.

Am I doing this in default proton cfg or Eggrolls?

There's no such thing as proton's cfg, or Eggroll's, for that matter; you need to use the system wine.

I have the minimizing issue too, I find it's not too bad and other Origin games do it, and it was already happening before these games came to Steam and Proton. Try using Borderless Windowed mode and see if that helps at all, it helped a bit for me.

I have the minimizing issue too, I find it's not too bad and other Origin games do it, and it was already happening before these games came to Steam and Proton. Try using Borderless Windowed mode and see if that helps at all, it helped a bit for me.

I cant actually alt tab in borderless it seems. Instead I have to move the borderless to a secondary desktop

There's no such thing as proton's cfg, or Eggroll's, for that matter; you need to use the system wine.

Not quite sure how to do that then

So I think the issue is still the read and write permissions. It keeps writing local.xml files even after doing the chmod -R 555 command. I can't delete the files either, keeps saying directory not found.

There's no such thing as proton's cfg, or Eggroll's, for that matter; you need to use the system wine.

Not quite sure how to do that then

Just

WINEPREFIX="/path/to/steam/directory/steamapps/compatdata/1237950/pfx" winecfg

Well I realized it was because it wasn't on an ext4 partition and I reinstalled under a new partition I made. But now it won't even install the thinclient of origin its just stuck at 0 of 1.

I have a problem. A giant problem. The game crashes with Proton 5.0.9; I already tried Proton 5.9-GE-3-ST, Proton 5.11-GE-1-MF and Proton 5.11-GE-3-MF. The first one tells me to update my drivers that are already updated, the second does not start at all and the third tells me that the game isn't installed even if it is. Already tried clean reboot, verification of game files and reinstallation, nothing worked. What should I do? Why GE betrays me like this?

Edit: I got the farthest with Steam Proton 5.0.9, that opened the Battlefront II main menu but makes the game crash when I join multiplayer or singleplayer matches. The others GE Proton versions start the Origin client but not the game itself.

I'm playing with 5.9-GE-3-ST with some stuttering but very playable!

How is the playability for everyone on 5.13-1? On my end it's slow as molasses.

On one of my PCs with a 5820k @ 4.3GHz and GTX 1070, I am getting around 140 average FPS at 1080p low settings using GloriousEggroll Proton release 5.9 version 8. It is very playable for me.

@cow-killer I'm playing it smoothly with Proton 5.13-1

i seem to have controller not working issues with games using origin launcher, same as mentioned here #4186

edit: with proton-tkg 6.0rc1.r0.gd7b71f0b the right stick works for the cursor, but buttons do not work. still need to try proton-ge

Has anyone gotten the Origin overlay working with this game? The game launches and I can play, but I can't seem to join friends games because the origin overlay does not load, resulting in error code 4932. Quick way to check is try to press Shift + F1 while in game, but you can also click on your profile in the top left, and then 'View Profile'. It should give the 4932 error.

EDIT: You can join friends from Origin if they invite you.

Playing on Arch Linux kernel 5.10.3 with nvidia-vulkan drivers on Proton 5.13.

Game runs very very well for about the first 3/4ths of a match but near the end (and I think after dying and respawning) performance drops to about 20-30 fps from 70-80 fps. I noticed this because after a dying near the end of the a match the character select screen exhibited degraded performance and upon respawning the rest of the match (and even the main menu after quitting the match) ran at ~20 fps.

A memory leak maybe?

It seems like for some reason all my steam games that require origin have stopped working. Attaching the log for this one, but I cant seem to be able to launch any of the origin based games. I can see origin getting launched and then minimized but then it just crashes. The game never launches. Thanks

steam-1237950.log

Update: Switching steam to the beta client, made all the origin games launch again.
Here is the log of the successful launch with the steam client beta.
steam-1237950.log

Hey i'm currently trying to install this game, because it should run well in theory.
My problem is, the game download with Steam worked well and really fast, but the installation of Origin takes ages before it finally crashes in the middle of the download/ installation progress.
It's looking like this:

Here is a log which i already got while downloading (i manually closed the installer later on).
steam-1237950.log

I will upload another one which should contain the crash then
Edit: Here is the complete log that contains the crash/ exit of the Origin installer
steam-1237950.log

Edit 2: I tried once again and supervised the whole process this time, it took really long but finally the setup went through. I don't know what was wrong before...

I would like to add to my previous comment. I've tried playing a couple more matches in Linux and it doesn't seem like there's a memory leak and it's not a session's playtime that makes the framerate drop. What I THINK is the source of the problem is when the game switches from normal gameplay to either the character select screen, the match results screen or the main menu. In other words, screens that have the vertical light slots like in this screenshot, behind Obi-Wan:

When loading up the game the main menu will run at about 60fps. Then, when playing a a new match my framerate will be a very playable >100fps until I die in-game for the first time. When the game loads the character select screen, for some reason, the framerate will drop to about 20fps. Then, when selecting a character and spawning it's a gamble on whether the game will stay stuck at 20fps or go back to regular performance.

Recently I played a match where after dying, I played another character with 20fps. Then I died again, got to the character select screen (which still ran at ~20fps), selected the same character again, clicked to respawn and this time the game went back to full performance. After the match ended and the game results were shown (the results screen uses the same scene as the main menu and character select screen) framerate once again dropped to about 20fps. There's just something about this scene.

I managed to get the game, the single player campaign, starting. However, the entire game, everything, freeze up when I move the mouse. It makes the game unplayable.
Is anyone else experiencing this? Is there a fix to that?

Game was working fine with Proton 6.3 and 7.0, but now it crashing on the main menu. Origin update issue ? I've tried deleting the prefix and perform a clean install, but the problem remains. Unplayable at the moment.

steam-1237950.tar.gz

Specs:
GPU: GTX 970 4Gb
Driver: 510.68.02
Kernel: 5.15 (fsync patched)
O.S: Manjaro

For me it worked before and it still works. There was also an Origin update when i started it today.

GPU: AMD RX 6600 XT
OS: NixOS 22.05
Driver/LLVM version: Mesa 22.0.1
Kernel version: 5.15.34
Link to full system information report as Gist: https://gist.github.com/davidak/448d5bc0f9c2554f6eac300518decabd
Proton version: 7.0.2

I was able to alleviate all performance issues (and most stability ones) by disabling every possible notification from Origin, and Steam Overlay.

Sadly, it seems that since few months, disabling Steam Overlay does NOT disable "achievement" pop ups intruding the lower right corner of the screen space. It used to do so, before. What is worse, the specific way the popups force themselves on the screen cause the game to crash with very high probability (not always, but most of the time).

Please Valve, bring back the possibility to banish the super-irritating and harmful notifications. Preferably, separately from disabling the overlay at all (achievement popups are irritating, and possibly harmful in games where overlay works well), but for fixing the specific issue, even restoring back old behavior of them being gone when overlay is gone, would do.

I have the same problem, the game works with more than 100FPS in Windows, but in Ubuntu with Photon from Steam the game drops a lot of FPS, it becomes unplayable.
I have an RX 6400

The game fails to run the game under a Steam gamescope session:

env ENABLE_GAMESCOPE_WSI=1 MANGOHUD_CONFIGFILE="$XDG_CONFIG_HOME/MangoHud/MangoHud.conf" gamescope -e --nested-refresh=60 -w 3840 -h 2160 -f -R --rt --hide-cursor-delay 3000 --fade-out-duration 200 --prefer-vk-device --adaptive-sync --hdr-itm-enable --mangoapp -- steam -bigpicture

Otherwise, the game launches for me.
Steam Input doesn't work though under Big Picture Mode (Wayland), for some reason, so that's not good. :/

• System Info: Gist
• steam-1237950.log
• steam-crash.log
• steam-logs.tar.gz
• Gamescope Version: 3.16.2
• Proton Version: 10.0-1f

I tried collecting a backtrace for this, but I'm not sure if it's useful information:

• gamescope_backtrace.log

@kisak-valve

Anyone else having issues with large usage of swap being needed for the game to run? Wayland + Fedora KDE, I had to create a 32G swapfile to actually have this game run. I have the game open as im typing this and its using about 15G of swap.

Anyone else having issues with large usage of swap being needed for the game to run? Wayland + Fedora KDE, I had to create a 32G swapfile to actually have this game run. I have the game open as im typing this and its using about 15G of swap.

Yes, I'm running 16 gigs of memory with 4 gig ZRAM and the process is killed within 30 seconds for using too much memory.

Any help or something? In extremely desperate to get this just one game running....

Anyone else having issues with large usage of swap being needed for the game to run? Wayland + Fedora KDE, I had to create a 32G swapfile to actually have this game run. I have the game open as im typing this and its using about 15G of swap.

Yes, I'm running 16 gigs of memory with 4 gig ZRAM and the process is killed within 30 seconds for using too much memory.

@Whayme I actually managed to resolve this issue by full uninstall (probably wasnt neccesary, clearing the prefix is probably enough), swapping to proton experimental, then going through setup and letting the steam process shaders stuff actually finished rather than clicking skip/cancel. Might be worth a shot? Now the game boots up every time without fail

@tunityguy do you still have this issue? I tried with a clean prefix with proton 8, 9 and experimental bleeding edge and they all had EA launcher install fine and the game launch afterward

It's a problem I occasionally see under Proton 10, personally; not sure why EA Origin does this

I'm experiencing similar issues, EA app installs and "Preparing game..." is displayed, and then nothing.
I've tried to debug the issue by turning on proton logs with PROTON_LOG=1, but for some odd reason the game starts correctly whenever I have logging enabled. But when logging is disabled I get nothing.
Extremely odd.

I've tried Proton 10, 9, Experimental, Hotfix and 6. Deleted prefixes between tries. I have also tried to completely uninstall the game and reinstall it.

Until now my Battlefront 2 install on Steam launched without issue.
But i saw more and more people on Lutris Discord that recently installed this game on Steam and can not launch it.
So I renamed my Steam BF2 wineprefix "compatdata/1237950" to "compatdata/1237950.good".
Then I launched BF2. I don't use a special compatibility configuration nor a special Proton version, I let all Steam options for this game to default.
Proton created a new wineprefix, installed EA app and...after several minutes, nothing more happened, Play button appeared again in green.
So I compared my old BF2 wineprefix and the new one.
After several searches and tests, it appeared that when I replaced "drive_c/Program Files/Electronic Arts/EA Desktop/StagedEADesktop/EA Desktop/" folder from the new wineprefix by the one in old BF2 wineprefix, the game launched again.
So I compared again this two folders and it appeared that there were far much files in new "compatdata/1237950/pfx/drive_c/Program Files/Electronic Arts/EA Desktop/StagedEADesktop/EA Desktop/" than in the old one.
So I deleted the supplementary files to obtain the same files in the two folders and...the game launched.

This is the files I kept in "compatdata/1237950/pfx/drive_c/Program Files/Electronic Arts/EA Desktop/StagedEADesktop/EA Desktop/"

bf2.txt

I tested this solution several times with success.

@legluondunet I've deleted every single file which wasn't in the list within that directory, leaving only 49 files, but it didn't fix the issue. The game was working fine yesterday, I hadn't updated anything or deleted the prefix, yet today it's not working anymore. I tried reinstalling the game completely along with its prefix, but that didn't fix it either.

@Yilmaz4 could mean we don't have same issue for this game. Did you post a Steam log here?

@legluondunet I suppose so. There's nothing seemingly interesting in my logs: https://pastebin.com/1DgfwD4b

EA app says preparing game, and after 3 minutes, the EA app opens for a split second and closes.

I can run the game smoothly until it hangs.
If the game hangs — GPU utilization drops and remains around 17%, CPU utilization also drops to about 11%.
The splash screen never finishes loading.
If I close the game using Alt+F4, the screen remains black with the cursor visible along with my KDE terminal.
The cat /proc/kmsg output shows:
"bus error"
followed by: _p9k_dump_state:sysopen:6: can't open file (...) - file system is read-only

If I switch to TTY2, I see the SDDM login screen with the password field filled. Switching to TTY3 through TTY7 shows only a blinking cursor. If I attempt Ctrl+Alt+Del, the system outputs:

[FAILED] Failed to start Generate shutdown-ramfs
[FAILED] Failed to start Show Plymouth Reboot Screen.
If I keep pressing Ctrl+Alt+Del, eventually this message appears:
[!!!!!!] Failed to execute shutdown binary.

I tried moving the installation to my root partition and now the game launches, before I had my installation on one of my NTFS partitions that I share with my windows installation.

I'm still confused as to why the game launched from the NTFS partition with PROTON_LOG=1 set.
But anyway, if anyone else is in the same situation as me and has their game installed onto a NTFS partition, try moving the installation to your root (/) partition instead

Uninstalled game today and delete compatdata/1237950".
Then reinstall game and launch it:
all worked out the box.
Proton version: default

When attempting the first launch of the game after installation, the desktop can become unresponsive for a short amount of time and the game does not start. After closing Steam and restarting the computer, the issue appears to be fixed and the game launches.

The game uses much more system RAM than it should and it can cause performance issues in-game. It appears that performance is improved after playing the game for some time during the first launch of the game.

Arch Linux 64-bit
Steam Flatpak

AMD Ryzen 5 5600H
NVIDIA GeForce RTX 3060 Mobile 6 GB, NVIDIA Driver 560.35.03
16 GB RAM

Intel Core i3-4150
AMD Radeon RX 550 4 GB, Mesa 24.2
8 GB RAM

With both systems, the system RAM and swap partition are filled. This issue does not happen with other games.

Hopefully this issue will be fixed soon.

Replying to https://github.com/ValveSoftware/Proton/issues/3971#issuecomment-4470985449

Sound fixed with 19 May version.