This should work with the just updated Proton Experimental bleeding-edge Beta branch (https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge).
Unfortunately it still didn't work here, the same -6 on the upper left side behavior as before. Here is the steam log:
Latest experimental bleeding-edge.
Eh, I wasn’t ever seeing any error -6, with or without the fix, I was seeing puzzling root directory listing instead of server connection exactly as described in the issue report and fixed the issue in lsteamclient responsible for that. Error -6 probably relates to native version where Proton is not involved.
Eh, I wasn’t ever seeing any error -6, with or without the fix, I was seeing puzzling root directory listing instead of server connection exactly as described in the issue report and fixed the issue in lsteamclient responsible for that. Error -6 probably relates to native version where Proton is not involved.
I know, it's the very same symptom of the native version. But you can see from the proton log of today that I sent that it's not the native version. The proton experimental string appears there too. And of course, the game is set this way:
Then when it's like that:
it's the windows version that's been running via proton:
The game opens locally stored web page through Steam interface. Before the fix that was failing with Proton due to Proton's lsteamclient's reasons. Now with that fixed that shows the same error as the native version. That 'error -6' is probably coming from Steam which cannot open that page for some reason (which I cannot immediately guess). Here both native and Window version (with fixed Proton) works... so something is different in your setup which triggers that error which would be interesting to know. Do you have anything special running Steam, like flatpak or else? As I a rather arbitrary guess, could you try with PROTON_SET_GAME_DRIVE=1 %command% launch options?
Tried PROTON_SET_GAME_DRIVE=1 %command% and nothing different happened. I have the normal steam package on arch, no flatpak or modified version in any way. My internet does not have anything special, maybe having ipv6 besides ipv4 but I think that's pretty common. In any fashion, I disabled ipv6 to see if it was interfering and still no change. I have a local intranet with 192.168.0.x and an external IP on my provider's modem.
ipv6 is better to be enabled always, many games these daya depend on ipv6 per se been available locally even if the network / provider doesn't support it (that's the case on Windows).
We'll need some broader testing probably to narrow down the conditions which trigger this problem to make some sense of it (I couldn't repro on 2 different machines here). Could you please attach PROTON_LOG=+steamclient,+file,+path ? What if there is some clue, but I guess this specific issue, seemingly common to fixed Proton and native game version, is not Proton related.
Yes, thanks. Notice that I am still running the game with Proton Experimental bleeding-edge.
proton experimentalx3 2025-10ge-proton10-17x1 2025-09proton 10.0x1 2025-09proton 9.0-4x1 2025-09PROTON_LOG=+steamclient,+file,+pathx1 2025-10PROTON_SET_GAME_DRIVE=1x2 2025-10PROTON_SET_GAME_DRIVE=1 %command%x2 2025-10
Compatibility Report
System Information
I confirm:
Symptoms
Reproduction
Attached are logs with Proton 9.0-4 and Proton 10.0 beta2
steam-1128860-proton10.log
steam-1128860-proton9.log
Notes