View attachment 89003
attached mission for 31 Sqdrn on 2-3 December 1942, flying from Drysdale.
I had to modify the dp files of the Beaufighter to allow if to fly lower in mission builder, and also allow the A6M2 to fly a bit slower (to see if it used less runway when landing? - )
also changed the formation to get the Beaufighters tighter together - so that will be lost if opened/edited in Mission Builder.
Interestingly, the AI aircraft flies over the terrain as if it's still using the original mesh, and the AI aircraft rise as they approach what would have been higher ground, but isn't!! Mission Builder even keeps wanting to adjust the altitude of some waypoints to match the older mesh. Is anyone else finding this?
RWills
I don't do enough mission writing to really comment, but I believe you may have stumbled on a quirk of Mission Builder.
It's really a stripped down version of the CFS2 exe, to allow mission creation & editing.
Because of this, I think they stripped out a lot of the code that wouldn't be useful.
Key amongst this, I believe, is that MB only seems to use mesh & A16N flattens that live within the sims own file structure.
I use a centralised scenery folder, kept outside each Sim install, to save disk space.
I've noticed that quite often when I'm creating a new airbase scenery, everything displays fine in the Sim, but when I open up Mission Builder to place GSL objects, part of the blended background doesn't show. It's as though the sim isn't recognising the LOD8 mesh, or any A16N flattens associated with the new base.
This can make gsl object placement somewhat challenging
I checked this out recently. I took a new airstrip I'm working on, that has this display issue in Mission Builder.
If I take a copy of that airbases A16N flattens bgl and place it in the installs SCENEDB/runways/scenery folder, the display issue (in Mission Builder) is resolved.
It does seem like Mission Builder only likes scenery bgls that live within that particular install' folder structure ...