Frozen every 2 minutes

[Doskan]

As title says, i get a screen freeze for about 1-2 seconds every 2:04 exactly, is there something that triggers every that lapse of time?
Got many mods btw... heres a list of them:

- Advanced equipment
- Dytech, core, inserters, storage and tools
- F-mod
- mopower
- motrans
- Pocketbots
- Powerlimiter
- Quick-start
- Resource monitor
- Telelogistics
- TimeButtons
- Yuoki
- Treefarm

[FishSandwich]

Yeah. That's quite a few mods you have there.

Is it the auto save? Try increasing it to a higher number, or just turn it off.

[Rahjital]

Check your autosave interval at options. I believe it is set to 2 minutes by default, so there's high chance the game is taking a while to save the game. You can raise the interval if it bothers you, but I would recommend not to set it any higher than 10 minutes. Remember that 0.10.1 is still a somewhat unstable version, so the autosaves make sure you don't lose all your progress in case anything happens.

The mods can make your saving time longer, especially large ones like DyTech or F-mod. It's your choice whether you want to sacrifice the mods in favour of saving speed or if you live with the occassional freeze.

[Doskan]

Oh its definetely that autosave thing, thank you guys

[ssilk]

Moved to technical help, but left a link in Game-help.

[slpwnd]

We really should make some "saving animation" to make it clear that autosave is running.

[Shaymes]

maybe like this?

[slpwnd]

Haha, yes something like that

[Shaymes]

[bulldog98]

We really should make some "saving animation" to make it clear that autosave is running.

You could also fork a process for saving the files.

[slpwnd]

We really should make some "saving animation" to make it clear that autosave is running.

You could also fork a process for saving the files.

Not so easy. The game must be stopped to capture the game state. We were playing with a mechanism that would save the game to memory buffer and then in another thread write it to file. That would be quite faster but can cause errors when requiring a lot of continous RAM (we had issues like that recently).

[ssilk]

Hm. What if you use a resynchrinisation?

First (very naive iteration):

- You begin the save and save chunk by chunk and the tick, when a chunk is saved. At the end you saved all chunks with the time.
- So when you now load the chunks in this exact order at exact the same tick you have the same game.

Well, of course this works only, if there is no interaction between the chunks.

Next iteration is to define a maximum speed; like the lightspeed there is nothing in factorio, which can move faster than this speed.

With this definition you need to save overlapping parts only.

- Save a chunk plus all tiles around this chunk, where anything can move in the time it takes to save this chunk.
- So when you load now you overlap add the saved chunk plus the saves tiles around this chunk.

And now you can make that faster, by using your method: Copy as many chunks as possible into the memory plus a border around them, which brings you on the sure side, that you have enough time to not come over the "light-speed".

More ideas: First store the non-moving stuff, landscape etc. Then the slow moving parts, like belts, then the fast moving part like locomotives. Also exactly the same idea, but for the non-moving parts it is only needed to update after the save, if something has changed meanwhile. And so with all the other things.