![]() ![]() If the process is supposed to kick off every 5 minutes, then it seem like the first one is, but never completes and resets the timer, so there never is another autosave after the first one starts. The files are only actually updated during a friendly shutdown. So is the "session snapshot" supposed to take place during periodic autosave? Otherwise the log doesn't show that the first periodic autosave is not functioning, but the files themselves are not updated and there is no subsequent autosave in the log. 09:00:01.150 - Thread: 6 -> Checking file access for files in target dir. 09:00:01.149 - Thread: 6 -> Session snapshot save - START 09:00:01.105 - Thread: 6 -> Making world state snapshot. I'll try today's evening an all-new world on the same server and try to remember to provide those files as well - maybe it may helpt to compare them. rar) withut having an account with google's. So it looks like the error to the autosave is somewhere in a special file or line of code maybe, that is otherwise not affected?Īs with Drui I'll give you the link to my google drive, so that you can access the files you need (zipped to. However, other updates' changes were accepted, as the fix to the assemblers' sound bug of the update 1.042 proved. (It's done via a button on the web interface, which also crates an (empty) (batch-?)file named "stop" and which is deleted when the server has started again.)Īfter then logging onto the server the status quo was reset to the 2 weeks old save status, all progress reverted. Also in the "event protokoll" no backup files were listed. Not the actual state is backed up, but the 2 weeks old status.Īnother thing I noticed: The changes I did last night were quite present in the morning. I did ramble around on the server for a total of more than some hours, but on stopping or/and restarting it via the webinterface, the "last known" save is loaded. ![]() The server keeps jumping back to the "last saved point", which is about 2 weeks old when speaking of any actual progress. Thus, the formerly applied fixes to the autosave function might not have worked therefore. ![]() At least none I have knowledge of or none which is obvious to me. Unfortunately the controllability aout the serves doings are almost nill, because there ist no console nor any application available to enter any commands whatsoever. Today's morning I wrote a PM to your colleague (if (s)he is such) "Drui" with an explanation what happens on my Dedi server, which is hosted by. ![]() Thank you very much for creating that fred, Phand. dedicated server config file (SpaceEngineers-Dedicated.cfg) dedicated server log file from the session where autosave failed (SpaceEngineersDedicated.log) In case you are still experiencing issues with autosave on dedicated server, please paste here (use dropbox or any other service): Like almost any other setting, autosave setting is per-world, not per-serverīoth game and original DS tool allows to edit world settings before loading a world. when you server edit config file, set 'autosave' to 'true' and then load some world, it will autosave only when the world has setting 'autosave' set to 'true' I'll just summarize how autosave should work:ġ) Autosave is enabled when creating new world or editing world settingsĢ) Autosave setting is saved together with World and it's settings (into world file)Ĥ) Game is saved when server is shutdown in "friendly" way:ĭS as service - stopping service in task managerĭS as console app - pressing CTRL+C in console window,ĭS as non console app - calling 'taskkill' without /f and with /pid where pid is process ID of DSĮ.g. All autosave issues should be solved, we could not reproduce any autosave issues on our side here anymore for the last week. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |