Cloud save did not sync after remotely closing game

[hardbrocklife]

Laptop is at my girlfriends house. I was playing Rimworld. I did not exit the game when I left. At home I launch Rimworld on my desktop. I get a warning saying I will be exited out of Rimworld on my Laptop. I acknowledge the warning as I obviously want to play Rimworld. Rimworld closes out on my laptop. It never updates saves to the cloud. Now there is no reason to play Rimworld.

When I launch the game it says "upload not started" pertain the save file no uploading from the laptop. Why would it not upload the save upon closing on the laptop? Does cloud sync only work if you close the game locally?

If so, that seems like a bit of an oversight. If you are playing a game on a different PCs the probability of it being open on the previous PC you played on is very high. Is there a hidden setting to make it cloud sync no matter what?

Also, when did remote play start requiring a PIN? If it did not require a pic I could have remote into the computer and resolved the issue, but when I tried to us remote play it asked for a pin. If my account is already logged in why would I need a PIN? If I was close enough to the PC to retrieve a PIN I would just be playing on that PC.

[cSg|mc-Hotsauce]

Remote Play started requiring a PIN a while back. Early last Summer.

But what is happening is it is essentially alt-F4 the game on on the other PC which stops everything, kills the process.

[hardbrocklife]

Originally posted by cSg|mc-Hotsauce:

Remote Play started requiring a PIN a while back. Early last Summer.

But what is happening is it is essentially alt-F4 the game on on the other PC which stops everything, kills the process.

:nkCool:

Which I am assuming is also stopping the cloud sync process for the closed game as well?


If anyone else reads this post in the future and is on Linux(manjaro) a roundabout resolution outside of steam was to install rustdesk, a free and opensource remote desktop client:

1. Add rustdesk as a service so it autostarts with your OS - can be done with systemd or through KDEs autostart applet, just search for autostart

2. Create bash script to check the status of the rustdesk service, mine was named monitor_rustdesk.sh and I put it in /opt/scripts and looked like this:

#!/bin/bash

# Check if RustDesk is running
if ! pgrep -f "rustdesk" > /dev/null; then
# If RustDesk is not running, start it
/opt/appimages/rustdesk.AppImage &
fi

3. Added a cron job that will run that bash script every 5 min to make sure rustdesk is running

My cronjob looked like this:

*/5 * * * * ~/bin/monitor_rustdesk.sh


If you arent sure how to do this dump some of the information with details about your setup into any recent LLM and it should do a pretty decent job of explaining how to do it for your OS or whether you are using a rustdesk flatpak, appimage, etc... Any Linux OS is going to have roughly the same operation to do this. Ask the LLM how to see if you have cron installed, how to install it on your OS, how to enable it, etc...

crontab can be a but wonky if you are new so installing crontab-ui with npm makes it really easy to install cron jobs and kind of learn how they work.