I also stepped in this trouble with ending a flight in mid-air and being unable to continue. Eventually I think I understood what’s going on and found a (rather?) simple workaround, at least for my preferred gliding activities. First I’d like to describe what’s (imho) going on, which may help those who are responsible for a more professional solution.
Usually, you start a creating a flight in the World-screen by setting a departure and destination. Then you may add further waypoints by click on the map and selecting add. You can check the result by opening the navlog. It is now important to recognize that besides the waypoints and departure and destination at least to more waypoints are inserted, “TIMECLIMB”, “TIMEDSCNT” and maybe “TIMECRUIS”. When you save the such created flight as, say, “MyFlight.flt” the amended flightplan is saved concurrently as “MyFlight.PLN”.
If you re-open then “MyFlight.flt” in a text editor you will find in the section [GPS_Engine]
[GPS_Engine]
Filename=C:\USERS<user>\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT
CountWP=7
…
It’s noteworthy to recognize that here it is not the filename of the precedingly saved flightplan what is referenced, but, instead “CUSTOM.PLN” in the flightsimulator app-directory. At the same place there is also a “CUSTOM.FLT” and a “CUSTOM.SPB” of a minimal size of <1kB. The latter represents binary data of the flight simulator simulation and display engine.
Once a take-off has commenced and the flight is saved again under a different name some things change. Most important is that in the GPS section (not in the various ATC-sections) the flightplan is stripped back to the originally defined waypoints. Despite that the “Filename=” parameter still points to the original file “CUSTOM.PLN”, which has the larger number of waypoints. Apparently the NAV-MAP doesn’t show a flightplan if the numbers in “CountWP” and those in the “CUSTOM.PLN” are different. Furthermore “CUSTOM.PLN” will be inevitable not correlated with “MyFlight.flt” anymore, if you fly in between some other flight. You may consider to timely make a copy of “CUSTOM.PLN” in a folder with your personal flights and rename it to “MyFlight.PLN” and update the “Filename=” parameter. Unfortunately, the such preserved original flightplan does still not fit to “MyFlight.flt”. It is also not straightforward to adjust [GPS_Engine] section such that the two files match. Further, if you save the flight after the next break, again the list and number of waypoints in the “MyFlight.flt” is stripped.
I found for me that the best solution is now, to create a flightplan by means of MSFS that fits to the last state of your flight and adjust the correlated flight file accordingly. This can be achieved by the following steps:
- leave the flight with [ESC]
- save it under a name of your choice (e.g. “MyNewFlight.flt”, different from the original “MyFlight.flt”)
- end the flight by hitting [END]
- reload the flight saved before
- save the flightplan under a name of your choice (e.g. “MyNewFlight.PLN”)
- open the flight file “MyNewFlight.flt” in text editor
- look-up the GPS-section and edit the “Filename=”-parameter as
Filename=[full-path-your-flight-folder]\MyNewFlight.PLN - save “MyNewFlight.flt”
- reload “MyNewFlight.flt” in the world screen of MSFS
For a long flight with several intermediate breaks you have to do this only once, as you can keep the first stripped flightplan for all subsequent parts. The “eating” up of the completed legs, however is not addressed by htis procedure.
If you further would like to keep weather and time adjustable look-up this section
[Weather]
…
FixedClouds=False
…
and delete the line “FixedClouds=” or edit like this:
[Weather]
…
; FixedClouds=False
…
If you further don’t want the cable hanging at your glider and tear you down when starting in mid-air, than look up this:
[Sim.0]
…
GliderLaunchType=TOWPLANE
…
and delete “GliderLaunchType=…” or edit like this
[Sim.0]
…
; GliderLaunchType=TOWPLANE
…
Upon next save ;-lines are removed by MSFS anyway.