This is not a big. The technology shows in the effects list what it’s doing.

Save corruption like this has virtually always been traced to bad hardware: most commonly failing RAM but also sometimes failing CPUs.

Factorio is not tolerant of failing hardware because it expects things to be correct and failing hardware scrambles things.

I suggest running a memory test, but ...

After the changes I made 2 weeks ago, the provided save file and mod load in a few (3) seconds on my laptop.

I did some improvements around this logic 2 weeks ago pending a release of the next experimental game version. It makes it faster - but it will always take some amount of time. The issue is compounded by migrations running for each blueprint in the save file and each blueprint in your library. There ...

Thanks for the report. I looked into this and I don't see a reasonable way to prevent this from happening. There's some precision loss going from the screen position the cursor wants to draw at to the end draw order sent to the drawing logic due to the position passing between screen-space and world ...

Thanks for the report however this is working as intended. Stack inserters only output full stacks of items onto belts unless specifically set to be less than the belt stack size. When the inserter limit is set to > the belt stack size but < a multiple of the stack size - it has no way to know "I ...

Reason: CRC check failed: The zip is corrupted.

This means it was corrupt after the game told the operating system to save it to disk. The only known way for that to happen is failing hardware (RAM, SSD/HDD, or CPU). So in that regard: there's no bug here for us to work on and the topic was put ...

Thanks for the report. This is now fixed for the next release.

This is now fixed for the next release.

Would you be able to provide a zip of the mods needed to reproduce this? I'm having a difficult time understanding the exact required set of installed mods and steps to reproduce the issue(s) mentioned.

Given the constant scaling factor of 2.5, and that recipe icons load with an expected icon size of 64 - which is the same icon used in map view - I'm going to put this into not-a-bug.

Thanks for the report. This is now fixed for the next release.

Thanks for the report. This is now fixed for the next release.

Actually I was able to figure out the underlying issue and it's now fixed for the next release.

Thanks for the report. It looks like this might be an engine issue - however without a way to reproduce it I can't be sure. If you ever do figure out how it happened and can make it happen again please let us know.

Thanks for the report. This is due to the chunk generation limit and how fast the game will generate them. You simply need to wait a few moments/a minute or two and it will catch up.

Thanks for the report. This is now fixed for the next release.

Thanks for the report. This is now fixed for the next release.

Thanks for the report however I don't believe there's any way to reasonably fix this. The way the values are stored internally only supports pure-number sequential keys (starting at 1), or pure string keys.

At best, we can update the Lua docs to mention this limitation.

If your PC blue-screened then you have hardware/driver issues. Given the crash logs provided, I lean towards hardware. Most likely RAM, but also possibly the Ryzen CPU issue.

Mods are not able to cause crash-to-desktop errors or bluescreens.