Page 1 of 1

[1.1.77][macOS] Unable to load too large save file

Posted: Sat Mar 18, 2023 1:16 pm
by azesmbog
Lord Developers!!
Finally your Game gave up, threw out the white flag, and refused to upload its own saves files. I am the Absolute Winner. EpicWin !!!1
Image
Now in order.
Here is the first part of this sad story, if of course it's interesting
viewtopic.php?p=581414#p581414

I then lost two weeks of progress, but I thought it was RANDOM! failure, and replayed this path for a month, saving progress every hour :(
when I went almost the same way in the game (actually even a little less) - I got exactly the same error!! But now I had previous records, an hour or two or three ago. Replaying many times, at least five times and rebooting the computer so that there are no random failures, I realized that at some point in time the current map is successfully saved, but this save can no longer be loaded. All. The final.
By simple deductions (and a month of lost progress), I came to the disappointing conclusion that this is due to the size of the save file.
A file with a size of 4,295,675,955 bytes still loads just fine
A file with a size of 4,296,497,050 bytes no longer downloads with the above error.
Somewhere between these two numbers is a "watershed" and a month of lost time:(((
(the first failure occurred on February 11, and the second on March 5)
I enclose the save from February 11, with a "speaking" title

https://drive.google.com/file/d/1biDRq4 ... share_link
If you decide to check my words, then at least 64 GB of RAM is required to (not) load this save, preferably 128 GB

But this is not the end of this sad story.
When I made sure that it was impossible to load the save, the thought dawned on me - why not try to load the same save in Windows OS. The fact is that for the last two years I have been playing Factorio in MacOS, and I will repeat once again - this game works better and smoother in Macos than in Windows, this is the final opinion, an axiom (by the way, I also launched Linux, played for a week and returned to macOS
And then an unexpected surprise awaited me!
My save for March 5 loaded like nothing happened!!! I thought - what about saving for February 11 ??? And it's loaded!!! and there I have even more progress than in March, so I continued to play it.
Today is March 18th.
A file with a size of 4,335,173,175 bytes still loads just fine

Everything is saved and loaded perfectly, except that it works a little slower in Win10 (for me this is a very significant drawback), and in order to load, for example, the previous save, when the game is running (for example, check whether it was successfully registered :), I just have to in the task manager, remove the application, because the unloading of the current map is monstrously slow, 10-20 minutes. If you are interested, I can measure the exact value by killing half an hour of time :) It's faster to kill the process, and reload both the game and the save. (In MacOS, this happens almost instantly, maybe 30 seconds).

So, Lord Developers!
I have just two questions.
Can you fix this fatal bug in MacOS localization?
The second question is no less important to me.
I'm almost out of time until Hour X - my current game time is 19445 hours. Will it be possible to fix my save so that there is no issue with tick overflow??

Re: [1.1.77][macOS] Unable to load too large save file

Posted: Tue Apr 04, 2023 4:44 pm
by Rseding91
Thanks for the report. It will be a while still but this will be fixed for 1.2 when the expansion comes out.

Re: [1.1.77][macOS] Unable to load too large save file

Posted: Tue Apr 04, 2023 7:37 pm
by azesmbog
Thanks, I'll be looking forward to it.
It is not very comfortable to play under Win, but nevertheless the size of the save has grown, now it is 4,393 Gb

Re: [1.1.77][macOS] Unable to load too large save file

Posted: Wed Apr 05, 2023 7:19 am
by boskid
Fixes here are related to MiniZip, you may try extracting the save file into a directory using an external tool to try loading a save file when it does not load from zip, factorio supports loading unpacked save files.

Re: [1.1.77][macOS] Unable to load too large save file

Posted: Wed Apr 05, 2023 2:02 pm
by mrvn
You could try cleaning up the map a bit, e.g. remove all decorations:

/c game.player.surface.destroy_decoratives({})

Then see if the save file is below 4GB again.

Re: [1.1.77][macOS] Unable to load too large save file

Posted: Wed Apr 05, 2023 3:41 pm
by azesmbog
mrvn wrote:
Wed Apr 05, 2023 2:02 pm
You could try cleaning up the map a bit, e.g. remove all decorations:
thanks, but you can start a new map with the same success. This is unacceptable for me :)
boskid wrote:
Wed Apr 05, 2023 7:19 am
Fixes here are related to MiniZip, you may try extracting the save file into a directory using an external tool to try loading a save file when it does not load from zip, factorio supports loading unpacked save files.
Yes, I know about unpacking the map. Once I already loaded the unpacked map, it worked. But these are also crutches, although it is not difficult for me to drag the current map under Win to MacOS and unpack it.
And further. Under MacOS, I tried to pack two saves into one archive at once. The total file turned out to be more than 8 GB. By means of the OS itself, it was normally packed and unpacked.

upd: The unpacked archive loaded perfectly under MacOS, and the size is not much larger than the packed one. While I try to play

Re: [1.1.77][macOS] Unable to load too large save file

Posted: Thu Apr 06, 2023 11:44 am
by mrvn
azesmbog wrote:
Wed Apr 05, 2023 3:41 pm
mrvn wrote:
Wed Apr 05, 2023 2:02 pm
You could try cleaning up the map a bit, e.g. remove all decorations:
thanks, but you can start a new map with the same success. This is unacceptable for me :)
How is that the same as starting a new map? You would loose all your base and end up with a too big save file some month later again.

The decorations are purely visual and have no game play effect, they are just there for their look. Removing them saves memory and reduces the save game size. It might buy you enough time to keep playing till the fix comes out with 1.2.