Risks of the new 0.14 aysnc autosave features

[Jan]

Hi!

After upgrading to 0.14(.1), its really risky to fight agist a base, when autosave arrived. If the server the faster to save the game as you, the game will be continue on the server. Within this, the creatures can kill you easy while you are in saving screen. I like to have an option to disbale the async auto save, or factorio should be save the game in the background.

[golfmiketango]

Background saving would be TOTES AMAZEBALLS!

On linux and mac they could probably fairly trivially achieve background saving by exploiting fork(). On Windows... well there is probably some way to do it but it'd presumably be harder (FILE_MAP_COPY on a memory-mapped file or some kind of PAGE_GUARD dance... I'm sure there is plenty of prior art floating around).

[Jan]

The NT API has functions like ZwCreateProcess to fork a process. Subsystem for Linux on Windows 10 use this function to map the fork UNIX syscall. I don't if its good enough or not.


Anyway, I want sync autosave back. Should i create a bug report?

[DaveMcW]

Is it possible for the client to simply disable autosave?

[MeduSalem]

Is it possible for the client to simply disable autosave?

In an MP game that would be the best thing anyways... since you can't really play such maps offline as there's no way to synchronize any changes you made while being offline. The only one autosaving the game should be the host/server. The clients though don't really need a local autosave copy on the hard disk.

That said if one is really going that route there should still be the possibility to make a manual copy of the current state of the game in case someone really wants to download an MP map permanently for offline play or whatever.

[ssilk]

Latest posts:
viewtopic.php?f=6&t=3829 Smarter autosaving (ie: Not in combat)
viewtopic.php?f=6&t=26016 Autosaving while in combat is DUMB
viewtopic.php?f=6&t=31305 No autosaves while combat !

Map transfer:
viewtopic.php?f=6&t=31279 Ideas to increase multiplayer map transfer speed