For those of you unaware of this problem, if you load a saved game and then attempt to look at the mission objectives list immediately afterward, OP2 crashes. A few minutes ago, I found out (by accident) that saved games do in fact work right. Sorta. Basically, if you wait a mark or two before attempting to view the mission objectives, you're fine.
But this begs the question, why does this occur at all? Further, why don't the original Dynamix missions suffer from this problem? So I got to snooping.
At first, I thought it had something to do with updating the struct used for save data, so I tried to make a time trigger that fired every 10 ticks and changed something pointless in the save data struct. That didn't work, so I'm guessing it has something to do with the mission objectives list itself. That got me thinking that perhaps forcing OP2 to update the mission objectives upon loading a saved game might fix this nuisance.
Of course, I'm not sure how to do that, so my research ended.
But still, I'm happy that saved games aren't as buggy as we previously thought!
Anyways, to recap:
-Saved games only crash if you try to look at the mission objectives immediately after loading a saved game.
-To avoid this, wait a mark or two before attempting to view the mission objectives list.
-To eliminate this problem once and for all, we need to figure out a way to eliminate this delay.
