[http://sourceforge.net/p/ufoai/bugs/2947 Item 2947] imported from sourceforge.net tracker on 2013-01-28 19:54:51

I have attached 3 game save to show this bug.

1) A ufo fighter to fight. After kill of the ufo figther, the crash area is there but the ufo fighter is unkillable.
2) Without problem to load the save game.
3) After completion of the mission of the crashed ufo. Load the mission will result to a crash for Error: UFO 'craft_ufo_fighter' is not linked to any mission

The vicious point is that you can play without problem a lot of mission and save. You will only see the break after loading.

I think that the save break problem is related to the unkillable ufo.

===== Comments Ported from Sourceforge =====

====== nabla64 (2011-07-09 17:36:57) ======

save before fighting
====== nabla64 (2011-07-09 17:37:44) ======

Save after the kill of the ufo
====== nabla64 (2011-07-09 17:38:22) ======

Save after completion of the mission (crash)
====== nabla64 (2011-07-09 17:38:55) ======

ufo console of the crash
====== geever (2011-07-10 21:52:11) ======

Another mapDef name was changed and I couldn't load your first save either. BUT:

Analyzing the savegame and the warnings I got, I think I've found the cause.

For missions we save index of UFOs. If a mission has a wrong mapDef we remove it's UFO too, but it changes other UFOs' indexes, so other missions will be linked to wrong UFOs. However UFOs will be linked to right missions....

I changed the code so UFO-data postprocessing set the connection between UFOs and missions in both directions and it will drop mission/UFO on wrong data to keep compatibility.

It should be fine with the latest version. Your savegames are corrupted but will load. UFOs and missions have problems will be removed automatically (I hope).

-geever
====== nabla64 (2011-07-10 23:16:04) ======

The save game now load, thanks. I will say you if i have again a problem with save game.
====== geever (2011-07-11 02:31:03) ======

Thanks for the feedback!

-geever

ps. You could have closed the ticket instead of reopening with your answer. ;)