OK, this one seems an Orbiter bug:
Nothing in the Orbiter.log, but the D3D9 log has several lines of
[ERROR] Base Object 0x253A460 = 'Zaragoza' not cataloged
for the "Context XYZ" surface bases.
Looks like something isn't being initialized between 2 runs in the same session.
BTW, running Orbiter 2016.
- load a scenario with a "Context XYZ" entry
- exit to the launch pad, but don't close it
- load another scenario, this one without the "Context" entry
- MOGE CTD, D3D9 loads as if "Context XYZ" was in the scenario
Nothing in the Orbiter.log, but the D3D9 log has several lines of
[ERROR] Base Object 0x253A460 = 'Zaragoza' not cataloged
for the "Context XYZ" surface bases.
Looks like something isn't being initialized between 2 runs in the same session.
BTW, running Orbiter 2016.