[2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal

Anything that prevents you from playing the game properly. Do you have issues playing for the game, downloading it or successfully running it on your computer? Let us know here.
uwslothman
Manual Inserter
Manual Inserter
Posts: 3
Joined: Sat Dec 06, 2025 4:26 pm
Contact:

[2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal

Post by uwslothman »

Sorry for the below- I've been having ChatGPT guide me through how to determine the problem and fix the longest save I've ever worked on:



This save crashes at engine level during Map::checkConsistency with an invalid MilitaryTarget registration.
A small-biter is physically in chunk [65,114] but registered on chunk [0,-1].

Behavior:
- With Transport Drones enabled: the map loads, but destroying enemies or loading the affected area crashes.
- With Transport Drones disabled: the game crashes immediately during “checking consistency.”
- Teleporting near ~{2080,3648} and moving east reliably triggers the crash.

This is a hard C++ assert in MilitaryTarget::unregisterOnChunk / Unit::onDestroy.
No Lua error is involved.
Save, log, crash dump, and mods are attached.

My goal is simply to eliminate Transport Drones and continue.

For space considerations, I deleted some inactive mods like krastorio.

Thank you!
crash report.zip
(206.53 MiB) Downloaded 13 times
mods part 1.zip
(591.19 MiB) Downloaded 13 times
mods part 2.zip
(332.67 MiB) Downloaded 12 times
mods part 3.zip
(362.13 MiB) Downloaded 12 times
Loewchen
Global Moderator
Global Moderator
Posts: 10553
Joined: Wed Jan 07, 2015 5:53 pm
Contact:

Re: [2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal

Post by Loewchen »

The save is corrupted, if you find a way to reliably corrupt new save files on the latest version of the game provide exact steps please. Make sure your bios is up to date for the raptor lake defect.
uwslothman
Manual Inserter
Manual Inserter
Posts: 3
Joined: Sat Dec 06, 2025 4:26 pm
Contact:

Re: [2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal

Post by uwslothman »

I'm wondering if the dev's have any sort of special way to fix the binary? This is my crowning achievement so far, probably 1000 hours into my first (and i think last) pyanadon run.

I'd be willing to veno/paypal a dev if its time consuming.
Loewchen
Global Moderator
Global Moderator
Posts: 10553
Joined: Wed Jan 07, 2015 5:53 pm
Contact:

Re: [2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal

Post by Loewchen »

Some corruptions can be fixed, but it might take a while for someone to have time to look into it.
uwslothman
Manual Inserter
Manual Inserter
Posts: 3
Joined: Sat Dec 06, 2025 4:26 pm
Contact:

Re: [2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal

Post by uwslothman »

Ok, I think i changed my mind. The devs have more important things to do like making this game even more awesome!

I was able to find a save from 3 months ago pre-corruption and for the first time successfully load it on my new laptop with the most up to date mods, likely offending mod excluded. It took me better part of two days to blueprint copy my pyanadon megabase over to the new laptop and finally getting it back to what it was. It's been running AFK without a crash for 96 hours now which hasn't happened in a long time. The only major thing I'm missing is my pride at using lua commands to cheat in the base and modules, and 3 months of nearly nonstop AFK buffer results.

So ignore the request to the devs. Thanks for making this game!
Loewchen
Global Moderator
Global Moderator
Posts: 10553
Joined: Wed Jan 07, 2015 5:53 pm
Contact:

Re: [2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal

Post by Loewchen »

uwslothman wrote: Wed Dec 10, 2025 3:59 pm likely offending mod excluded
This is not caused by a mod, it is either a factorio bug or most likely a hardware problem. Since you are using a 13th Gen Intel cpu you should make absolutely sure you are on the latest bios before it gets permanently damaged.
Post Reply

Return to “Technical Help”