Linux users, read! This release requires a change to your Steam.sh! This is not being pushed out as an automatic update through the Flatpak repo/posted to the Linux release tag that h3adcr-b uses pending an update!
Here's what's new:
-
Windows: Fixed OneDrive sign in issue on Windows
-
Linux: Switched Linux injection from LD_AUDIT to LD_PRELOAD for broader distro compatibility. All distros/setups should work now.
If you manually edit your steam.sh, remove cloud_redirect.so from your LD_AUDIT and specify it as an LD_PRELOAD. If you don't edit it by hand, wait for a h3adcr-b update. This should not happen again and future updates should be smooth. Apologies.
-
Linux: 'Derive root tokens from AutoCloud rules when stored tokens are missing'. This fixed issues restoring saves for certain games, in certain scenarios. Most commonly native Linux games. Hard to reproduce the problem in the first place but easy to fix once I was able to reproduce it.
-
Linux: 'Use fixed port for Google Drive OAuth callback in Flatpak' fixes issues involving Arch installs of questionable quality.
-
Windows & Linux: Accuracy improvements for Steam Cloud behavior. One that is minor, one that is major. Minor one is a house keeping fix regarding change number tracking in the cloud metadata/when the tool bumps that number up. The major issue could cause a sync conflict and a failed restore in a scenario involving cross-OS usage. Please update if you do play on both Windows and Linux in the same game(s). The issue requires cross-os play and some edge cases to trigger, but it could cause a user to have to go into Google Drive and use file versioning to grab their correct save. The issue also is really a SteamTools bug that I had to work around. Getting tired of those.
There is still more work to do to better support multi-machine scenarios. Some foundational hacks I did to get this working on Windows need to be removed and replaced with the real Steam Cloud behavior. Implementing that behavior is fairly easy now; those hacks comes from very early in the development of this tool, when I didn't understand as much about how Steam Cloud works as I do now. Issues that could realistically cause silent data loss are gone now. I am only left with issues that could cause a failure to sync, which are bad but not quite as bad. But rather than fixing each edge case one by one, I'm just going to remove some horrid hacks and do a lot of validation. Standby!