Bugger.

[=CfC= Binks]

Hmmm, this Alamein mission is jinxed.
Yesterday evening, I finished it, and added one last flight, net result was that it refused to close. I had that rotten message, do you want to save this as a new file, which in bug terms means that I had too many aircraft in the same unit. Only way to get out of this is to not save.  I lost the previous 3 hours work on ground objects etc.
Tonight, I retraced steps, added in the flights, being careful to change the units, save and close at every step, after another hour or so, saved and closed, opened up, and the last flight had disappeared, together with every last ground object, tank, artillery piece and runway etc, hundreds of them!
Anyone know if this is recoverable? There is a little box that appears that says loading mission, but nothing is happening, only the aircraft waypoints are still visible. 

[=CfC= Binks]

The mis file appears to be completely corrupted. I copied the previous version from a restore point two days ago, which has nearly all the ground objects, but when I paste them on to what remains of the existing mission file, they won't save. So I have the ground objects on one file, but very few of the flights, and nearly all the flights on the other, but no ground objects. Think I'll have to go for the ground objects version, and renew all the flights from a screen shot of the other.
I still don't understand what is causing this though, as I'm changing all the flight details at each entry!

[=CfC=Bounder]

Dear oh dear!

I know the feeling only too well!

As I understand it, you have one file with the objects and one with the flights?

If that is the case, just open up in Notebook, back-up both files, then copy the objects from the good objects file into the file that has the flights.
You must have the syntax correct in that "stationary objects" must be pasted underneath the current "stationary objects" section and static objects pasted in the "buildings" section. The number prefix has no bearing on the issue, they will still load even if you have another object with a similar number in front of it.

If you get a load failure after this, check the file against a good mis file for a syntax error.

Hope this works for you.

Bounder :-\

[CFC_Conky]

Hi Binks,

I often get that message if I've filled a particular unit's squads with four-plane flights, i.e. 64 kites in the unit. As long as I don't populate every squadron, or at least leave a few flights with three or less a/c, I can usually avoid it.

Pip, pip,
Conky

[=CfC= Binks]

Thanks both, I'll try those options this evening, If yours works Bounder, it will save hours of work!

[=CfC= Binks]

I tried as Bounder suggested, copied both .mis files and opened up in note, and all the ground objects, artillery, tanks buildings etc are still there! The last flight shown was some JU88's, so the final two additions got wiped. I changed the squadron detail number of the 88's, inserted the copy folder in the dogfights section, and it opened up, all the missing objects now showing again, together with all the flights, excepting the JU88's!
I'm going to try deleting the 88's from the .mis file, and putting them back in again, see what happens. After another backup of course!

[=CfC= Binks]

Finally, I think I found the problem. Working toward the end of the build, and I set a flight of three to take off from a particular remote airfield, and exactly the same thing happened. Afterwards, nothing else could be entered, so I saved logged out and then back in, and all the ground objects had disappeared again. Went into the .mis file and deleted the flight of three, and everything loaded with no problem.  Put the flight of three in as a normfly, and again, no problem. I think the map has a corruption associated with that particular field, as I had just entered the same flight as taking off from there before the previous crash.
At least I know how to retrieve the objects now, just delete the last entry.

[CFC_Conky]

That's good news Binks, another thing I do when building larger missions is to not only save frequently, but also exit the fmb completely from time to time. This should 'lock in' all the stuff in the mission.

Pip, pip,
Conky