Demo of the Steam UI behavior, in case it helps in some way
https://github.com/user-attachments/assets/447c4602-d9ce-44c3-98f2-b978c6bd69ec
Ok, so when proto:setup_prefix is trying to create a the sym-link, it's at working path SteamLibrary/steamapps/compatdata/2674590/pfx and the drive_c is present in the /pfx/ folder, but not in the /2674590/ so it fails to create the link.
What is the intended path that it should be in that's a child of /pfx/ that it isn't actually in? Or is the /drive_c/ in the incorrect location and should be at the app-root of /2674590/?
Hello @CalebMorris, this is a general filesystem issue instead of a game-specific issue which is already being tracked at #5168.
The general recommendation is to use a Linux native filesystem with the Steam libraries that you use Proton with.
You might have some luck with the community written workarounds in https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows, but your mileage may vary.
Closing in favor of the older issue report.
Ah, it appears when I was testing another game to see if it was just Beltmatic, that that game had direct Linux support so it wasn't going through Proton.
Installed to an EXT4 drive, confirmed that this error is no longer showing up
proton 10.0x1 2026-02proton 10.0-4x1 2026-02proton experimentalx1 2026-02proton hotfixx1 2026-02
Compatibility Report
Beltomatic2674590System Information
GeForce GTX 970nvidia driver 535.288.01-0ubuntu0.24.04.16.14.0-37-genericProton Experimental,Proton Hotfix, andProton 10.0-4as selected from Steam. All have the same behaviorI confirm:
Proton Log
steam-2674590.log
Symptoms
The game doesn't start. No windows open. Steam never leaves progresses past
Launchingbefore failing.Reproduction
Playfrom SteamLaunchingstatus as the game begins start processa. There are no windows that pop
Personal Notes
Possible oddity that is contributing to this is that I have my steam lib on an external drive. Other games work fine though.
When running Steam from terminal to try and get any crash info that wasn't showing up on Proton log, I get the following error: