#Cloud sync not working as expected

1 messages · Page 1 of 1 (latest)

unreal crag
#

I've been trying to play on my Steam Deck and PC, and cloud sync says it's up to date, but it most definitely is not - unlocks are not synced.

slow marlin
#

I'm having the same issue with two separate PC's, so not limited to Steam Deck.

frigid swan
#

Try verifying files. I can show you if needed

unreal crag
#

Tried, says all files successfully verified. Still don't have my unlocks from the Steam Deck.

#

I have the achievements thhough

slow marlin
#

Logged into my other computer again after doing a few things on the first one, and it still has my older save. So there is a sync issue

lavish musk
#

Just loaded and played this on my deck for first time after playing 16 hours on PC. Had zero progress on deck so I decided to try and stream from my PC to my deck see if it would fix the issue and it over wrote the 16 hours of progress with the deck ZERO progress!! WTF. Beyond annoyed.

slow marlin
#

Not as bad but I just lost a good bit of progress from the same issue. I played it on the one that had the most recent unlocks, unlocked a lot more, then later tried on the other machine and sure enough I was back to few things unlocked. I went back to the other machine and loaded the game and it now reverted down to the out of date one.

This is pretty much a game breaker, I'm not playing this anymore until it's fixed.

blazing citrus
#

Thankfully I found workaround for this issue. Access your local files on PC(username\AppData\LocalLow\Fiveamp\NIMRODS) and on the Steam Deck(Steam button > Power > Desktop Mode > Dolphin > search for 'Fiveamp' or 'NIMRODS'). You should see that the 'fiveamp######.json' file sizes are ascending in size. The larger the .json files are, the more you have unlocked. The idea is to delete the 'bad' saves, disconnect from the internet, start NIMRODS and make sure it loads the correct save, re-connect to the internet and force that file to sync to the cloud.

frigid swan
pastel sparrow
#

We have recently made a backend update to our Steam Cloud Save config that may have resolved the issue. I am no longer able to reproduce the issue on my setup, please let us know if you still encounter issues!