Posted October 01, 2022
I've rammed up against the 2GB limit on cloud saves so much now that the feature is more of an inconvenience than a useful feature for me personally, and I originally just wanted to disable it on Cyberpunk where it doesn't work properly at all, however it's so frustrating that I decided to just disable it globally.
The problem is that Galaxy just ignores the fact that you told it to disable Cloud Saves and keeps trying to sync anyway then saying cloud sync failed. Every time I start up Cyberpunk there is like a 1 minute delay of Galaxy trying to cloud sync even though it has been disabled.
I discovered last year that the only way to fix this, is to enable cloud saves, go into the game and manually delete save games one at a time for like 20 minutes in the slowest clunkiest user interface for this in-game ever. If you try to make it go faster by optimizing hitting the appropriate keys to delete a save, eventually you make a mistake and it loads the game, then go back into the menu, scroll to the bottom and wait 1000 years for it to display everything, then delete delete delete again. Very frustrating user interface, not user friendly.
So anyway, I did all of this and deleted so many save games that there are like 40 or so left which is way way below 2GB, however Galaxy still tries to cloud sync that and fails every single time. Sometimes for unknown reason and lately saying that the servers are busy. Doesn't buy a lot of confidence for the feature to be honest.
Anyhow, now that I deleted almost all of my save games (after making local backups on another drive instead), and it is no longer taking up 2GB of storage, it still will not sync to the cloud, and while I can disable cloud saves either just for this one game or globally in Galaxy, it absolutely refuses to stop trying to sync to the cloud.
Got me so frustrated this time around that I just want to permanently disable this broken feature and forget it ever existed. Perhaps I can have my firewall disallow traffic to the cloud storage server and return ICMP error with tcp-reset to force the client to bail trying to sync sooner or something.
Alternatively, give me the source code to Galaxy client and I will fix the problem myself...
The problem is that Galaxy just ignores the fact that you told it to disable Cloud Saves and keeps trying to sync anyway then saying cloud sync failed. Every time I start up Cyberpunk there is like a 1 minute delay of Galaxy trying to cloud sync even though it has been disabled.
I discovered last year that the only way to fix this, is to enable cloud saves, go into the game and manually delete save games one at a time for like 20 minutes in the slowest clunkiest user interface for this in-game ever. If you try to make it go faster by optimizing hitting the appropriate keys to delete a save, eventually you make a mistake and it loads the game, then go back into the menu, scroll to the bottom and wait 1000 years for it to display everything, then delete delete delete again. Very frustrating user interface, not user friendly.
So anyway, I did all of this and deleted so many save games that there are like 40 or so left which is way way below 2GB, however Galaxy still tries to cloud sync that and fails every single time. Sometimes for unknown reason and lately saying that the servers are busy. Doesn't buy a lot of confidence for the feature to be honest.
Anyhow, now that I deleted almost all of my save games (after making local backups on another drive instead), and it is no longer taking up 2GB of storage, it still will not sync to the cloud, and while I can disable cloud saves either just for this one game or globally in Galaxy, it absolutely refuses to stop trying to sync to the cloud.
Got me so frustrated this time around that I just want to permanently disable this broken feature and forget it ever existed. Perhaps I can have my firewall disallow traffic to the cloud storage server and return ICMP error with tcp-reset to force the client to bail trying to sync sooner or something.
Alternatively, give me the source code to Galaxy client and I will fix the problem myself...