Slave Zero X (1903910)

[m0rb]

Compatibility Report

• Name of the game with compatibility issues: Slave Zero X
• Steam AppID of the game: 1903910

System Information

• GPU: nVidia GeForce RTX 3080ti
• Video driver version: nvidia 550.76
• Kernel version: 6.8.6-200.fc39.x86_64
• Link to full system information report as Gist:https://gist.github.com/m0rb/dc3ca33eb903868ebb12bc0e88435ca6
• Proton version: Experimental, 9.0 Beta, 8.0-5...

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

I've been having a heck of a time trying to figure out why this game continues to have issues saving its configuration and savestates to the Proton VFS.

Post-installation, and after a few gameplay sessions over time, the game will eventually start displaying an error message "Could not save settings. Please check that you have some free disk space. (> 50 Mb)"

Said error message appears when trying to change settings in-game, as well as trying to start a level / load a savestate.

This happens regardless of whether I've set the PROTON_SET_GAME_DRIVE=1 environment variable in launch options.

It also seems that the game isn't syncing saves/settings with Steam Cloud.

Reproduction

1) Install the game through Steam on a Linux distribution 2) Attempt to play numerous sessions over time 3) Error message eventually appears

steam-1903910.log

[simifor]

@m0rb I played for 40 minutes, completed the first three stages and loaded the fourth one, changed some settings and didn't get that error. Checking on a second device, the save file was synced as expected. Just to be clear, after the error started popping up you became unable to keep playing the game, save settings and get cloud sync? How long or how many levels would you say were needed for the error to start happening?

Also, I would appreciate it if you capture new logs as it seems you have WINEDEBUG=-all set somewhere in your system, which affects proton logs as well.

[m0rb]

The issue started after the second time I loaded up the game after the original installation.

Afterwards, I wiped and reinstalled varied versions of Proton as well as the game itself. The error eventually reappeared after a few sessions. (Wasn't sure if I hosed any of my prior Proton installs, wanted a clean slate)

Found that setting PROTON_SET_GAME_DRIVE=1 before first launch got me further along, but it eventually started erroring out again after a few sessions.

--

... capture new logs ...

Forgot I had WINEDEBUG=-all in my profile. D'oh. Sorry about that. Unset it for this round. (Popped the error up in Settings, popped the error up on level load / continue);

steam-1903910.log

[m0rb]

Earlier I upgraded my distro and decided to give this another round of attention.

I made backups of my previous prefix and szx directories for yucks.

Uninstalled.

Set "Compatability -> Run other titles with [Proton 8.0-5]"

Reinstalled the title

For some reason it didn't create the dosdevices directory and its softlinks under the prefix. No big deal.

Title ran after remedying that.

...and apparently it synced with Steam Cloud after this run.

steam-1903910.log

I'll be ecstatic if it continues working.

[m0rb]

Update: Celebrated too soon. Still cropping up with the same error.

Anyone have $0.02 on which extra WINEDEBUG traces I should consider without making it log excessively? Can't see anything obvious with the current ones.