-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloud saves lost with a native Linux game release #7464
Comments
Hello @flibitijibibo, the majority of this issue is already being tracked at #7023 / #5736. Let's use this issue report to focus on the lost cloud saves. |
yes i have tha same problem |
Someone has just reported this same issue to me. To elaborate on "missing savedata": they reported that the new savefile created by the newly added native Linux version has overwritten the Cloud savefile created by the Proton version. Is there a known workaround? Would uninstalling the Proton version and then installing the Linux version work better than toggling the "Force compatibility tool" option? |
Sadly the way Steam currently mixes up the depots makes it hard to work around consistently - generally the way I tell customers to safely transition to native is by backing up the save data and manually poking it into the right spot, and thankfully PCGW makes it easy to look at both paths on a single screen (example). |
We just had this happen in the opposite direction today! When Valve overrode Salt & Sanctuary to use Proton (and nobody was told...), a bunch of Deck users lost their save files for seemingly no reason. Luckily the cloud feature was just incomplete enough to where we were able to find the files backed up, but there's an extremely good chance those files will be wiped when it gets flipped back to native! |
This works fine for games like Half-Life 2 and friends. Sounds like an app config error on your side perhaps? Looks like Steam Cloud is only enabled for the Windows version of S&S? This list wouldn't account if you are using the SteamRemoteStorage API manually on the Linux version and not the Windows version for saves though, but if you are doing that, then yes, that would be broken. I also would imagine the game would get overriden to Proton if the Linux version was not compatible with users' cloud saves from Windows. |
Someone appears to have reverted the change to sync them rather than publish, for the 1.0.0.9 release - this has now been pushed. Still: You have a game running fine on a system, Valve forcibly takes that version away without the customer's consent, and suddenly their saves are gone... seems like a bad user experience in my book! As far as I know, this bug still is not resolved - I fully expect this to persist when Rogue Legacy 2's native release comes out soon, so it would be good to have some kind of assurance that the root issue has been investigated. |
Could we get this looked at? |
Added a second guide to the OP that specifically shows a repro case with the Deck Verified override program. This shows the bug explicitly affects Steam Deck customers with what is supposedly the long term goal of SteamOS, which is (again, supposedly) to produce more native Linux binaries. This has a negative impact on all customers as well as developers attempting to optimize their game for Steam Deck, and should be treated as a highly-accessible data loss bug. |
A translated version of the workaround, now that Salt is back on the native version... https://steamcommunity.com/app/283640/discussions/8/3714937078835463398/ I have at least one more title in the pipeline that will be hitting this, so even a single shred of evidence that someone on the Steam team has seen this a nonzero number of times would be wonderful - it doesn't even have to be a post of substance, a no-context picture of Squidward with no text whatsoever would be enough at this point! |
Same problem here i lost all my arma 3 saves, its posible make a buttom to force proton in all games? |
Your system information
Please describe your issue in as much detail as possible:
For Windows-only games, the Steam client will correctly assume Proton as the compatibility tool. This is fine until a native Linux version is made available, where the client will keep the Windows depot but use the launch options cloud saves from the native client, resulting in 'missing executable' errors and potentially lost save data since the saves get lost in the Wine prefix and are not transferred to the proper location.
While Linux native releases post-launch are not an everyday occurrence, this still adds a tremendous burden on developers by introducing tons of bug reports that include save data being completely lost, all due to an issue that the developer has nothing to do with and cannot control.
Steps for reproducing this issue:
Reproducing requires having a Steam app as a developer, with cloud saves implemented via Steam Auto-Cloud:
Steps for reproducing via Deck Verified:
The text was updated successfully, but these errors were encountered: