[0.12.29] DeSync - Autosave issue
Posted: Thu Apr 21, 2016 12:17 pm
Good Afternoon All,
I have recently encountered an issue with one of our save files.
I will try my best to describe the situation/issue, I'm currently in work so I do not have access to the files.
Scenario
Server is an AWS EC2 Instance with 2GB RAM with 2 Cores running Linux Debian I believe.
Save File Size is around 13MB and has 40 ish hours of gameplay (Will try and upload the files + DeSync report tonight)
I had exited the game a few seconds before an auto save initiated (The autosave notification popped up in the background just as I was logging out).
Tried to log back in and it would then download the map and then create a DeSync report. After this it then was trying to upload the map from my machine of which it had successfully completed the action.
When looking through the log the error seems to relate to the CRC check that is performed.
Things I have attempted to remedy the DeSync (I still have the original save file backed up);
Loaded the save up locally and have ran "/c remove_offline_players" from the console using my account and a friends in the attempt to remove all offline users data from the save.
Started the game up as a multiplayer session locally of which it ran without a hitch. (Yet to see if friends account will also connect to the session)
Uploaded the Save game to the server which has had the offline players removed to have it still desync everytime either of us tried to connect.
Also tried copying the save file from the server and renaming it mp-download.zip (including theinternal folder of the save file) and replacing the mp-download in %appdata%/roaming/factorio/temp
My Personal System (Just to rule out specification requirements)
Intel i5 6600K 3.5Ghz
Nvidia GTX 980ti
250GB SSD
40MB Fibre Connection
Friends machine
Intel I7 4710
Nvidia GTX 970M
250GB SSD
76MB Fibre Connection
Summary
I am yet to attempt replicating this as it will be difficult to time the logging out before an Autosave. If this is the cause I have a suggestion to help prevent this issue arising. Having a form of cooldown 5-15 seconds before autosave preventing people from exiting until the autosave is complete should prevent this from arising.
Hopefully I will be back with some files later this evening.
Bye All
I have recently encountered an issue with one of our save files.
I will try my best to describe the situation/issue, I'm currently in work so I do not have access to the files.
Scenario
Server is an AWS EC2 Instance with 2GB RAM with 2 Cores running Linux Debian I believe.
Save File Size is around 13MB and has 40 ish hours of gameplay (Will try and upload the files + DeSync report tonight)
I had exited the game a few seconds before an auto save initiated (The autosave notification popped up in the background just as I was logging out).
Tried to log back in and it would then download the map and then create a DeSync report. After this it then was trying to upload the map from my machine of which it had successfully completed the action.
When looking through the log the error seems to relate to the CRC check that is performed.
Things I have attempted to remedy the DeSync (I still have the original save file backed up);
Loaded the save up locally and have ran "/c remove_offline_players" from the console using my account and a friends in the attempt to remove all offline users data from the save.
Started the game up as a multiplayer session locally of which it ran without a hitch. (Yet to see if friends account will also connect to the session)
Uploaded the Save game to the server which has had the offline players removed to have it still desync everytime either of us tried to connect.
Also tried copying the save file from the server and renaming it mp-download.zip (including theinternal folder of the save file) and replacing the mp-download in %appdata%/roaming/factorio/temp
My Personal System (Just to rule out specification requirements)
Intel i5 6600K 3.5Ghz
Nvidia GTX 980ti
250GB SSD
40MB Fibre Connection
Friends machine
Intel I7 4710
Nvidia GTX 970M
250GB SSD
76MB Fibre Connection
Summary
I am yet to attempt replicating this as it will be difficult to time the logging out before an Autosave. If this is the cause I have a suggestion to help prevent this issue arising. Having a form of cooldown 5-15 seconds before autosave preventing people from exiting until the autosave is complete should prevent this from arising.
Hopefully I will be back with some files later this evening.
Bye All