Lol THobson, I was kinda hoping you would come up with a list of things I might have forgotten about.
1) Un-Im... or UnIm.... I know it is slightly truncated in the list of missions and I don't like that, but I experimented with various forms of the name when it was changed from Impossible mission and that was the best one. I considered changing it but the name appears in so many places I would be bound to miss one, so I'm going to leave it as it is.
2) The second chopper now appears 1.5 - 2 hours into the mission and does not run out of fuel. (The first chopper doesn't run out of fuel either.) Both choppers make a trip to an outlying island to the north to simulate going somewhere to refuel, though they don't land or anything.
3) Yesterday I completely re-recorded my voices for the cutscene, the new ones being marginally less crap than the old and virtually click free. The girl doesn't live locally so hers will have to stay for now: I've editing them in Goldwave as far as my limited abilities will allow so they are better than they once were, but there is still the odd click. The tinny echo effect has been eliminated.
4) The swinging body isn't worth more work, it's intellectually unsatisfying and if it was important I'd fix it, but ..... it is one of the many remaining imperfections in the mission. The trouble is my whole bloody life is on hold till I finish the wretched thing so I'm keen to get it done.
5) I'll never say never, particularly about tricky things like stuck vehicles, but the mission is much more robust than it was. The jeep that caused all that bother was working under just a couple of triggers, which on many, many test runs worked fine about 3 times out of 4. So you were slightly unluckly. As you know, the script had already replaced the triggers when your incident occurred: since then, under your advice, the script has been improved several times. On a fair few test runs there have been no incidents of stuck vehicles. I will make a test with a jeep roughly in that place check that it works.
6) I checked the beta testers names, and in the latest version there are no squiggly lines above them.
Any more thoughts like that very welcome. I did a quick run through the last few pages of the thread but I could easily have missed something.
The final version, nominally 1.00 but in reality 0-66, (0-65 is a backup version) will hit the missions depot in a couple of days and certainly before the weekend. Things will continue to come up, so I expect to make a 1.01 before the review is done in a month of two's time. With a mission of this complexity there is no sharp line between "final beta" and "first release", but 1.00 will be something I'm happy to put my name to.