I am currently having an issue with Fortnite Battle Royale in that every time that I close the cloud rig I have to reinstall the game when I am ready to play it once more. I have downloaded it to steam and to the correct place on the rig itself but it is not working.
Before signing out it would be nice if there were a checklist that could be done to make sure all games downloaded would remain upon return to the rig. Just as a second measure to prevent any unnecessary hiccups.
Showing 1-8 of 8 comments
Game reviewerKryipt#1February 17th, 23:07
Until any big changes are in place I think it would be best to just leave it open if you can. Also make sure it is being saved to the D: drive.
Game reviewerKryipt#2February 17th, 23:09
Nevermind, I noticed the inactivity kick. Hopefully an update comes out.
lmk if u have any luck bc im experiencing the same thing
SnoobsterSullyQ#4February 18th, 19:12
Are you shutting it down correctly? To close it I tab out to my desktop, quit and restart Snoost, then hit the Turn Off button and let it run through the checklist.
As for the launcher, I had that problem with the Origin launcher. Make sure everything is on the D: drive including the launcher, since the only things that carry through (at least for me) are the contents of the Downloads/Documents folders and the D: drive.
MechanicWrongMan#5February 18th, 20:50
It has happened to me once in one month, losing everything on the D drive and user folder. This can happen if the rig loses connection to the backup server which should be a rare occurrence.
Ps: also has nothing to do with you, nothing you can do.
Last edited: February 18th, 20:50
StaffRuneDalton#6February 21st, 06:29
Hi guys. I just wanted to let you know that we are working on addressing this issue in a couple of upcoming patches. It's not always related to one specific event, but as @WrongMan says it also only happens in are instances, when the server gets an unexpected interruption during backup, shutdown etc.
We completely understand the frustration when this happens, but will be focussing on debugging and improving the backup procedure in the upcoming patches. Any details that might help us troubleshoot or reproduce the problem would be greatly appreciated.