Digging around the OneStore to understand how missions are done, see what I found in all the .pln files:

asobo-bushtrip-nevada\Missions\Asobo\BushTrips\nevada\Nevada.PLN

    <!-- LNMDATA
         _lnm=Created by Little Navmap Version 2.2.3 (revision f743328) on 2020 02 28T14:45:26|
         aircraftperffile=|
         aircraftperfname=|
         aircraftperftype=|
         cycle=1801|
         navdata=NAVIGRAPH|
         simdata=
-->

asobo-bushtrip-chile\Missions\Asobo\BushTrips\Chile\Chile.PLN:

    <!-- LNMDATA
         _lnm=Created by Little Navmap Version 2.4.4 (revision b96521a) on 2020 03 03T11:13:02|
         aircraftperffile=|
         aircraftperfname=|
         aircraftperftype=|
         cycle=1801|
         navdata=NAVIGRAPH|
         simdata=
-->

asobo-bushtrip-balkans\Missions\Asobo\BushTrips\Balkans\Balkans.PLN

    <!-- LNMDATA
         _lnm=Created by Little Navmap Version 2.2.3 (revision f743328) on 2020 02 26T14:04:10|
         aircraftperffile=|
         aircraftperfname=|
         aircraftperftype=|
         cycle=1801|
         navdata=NAVIGRAPH|
         simdata=
-->

 

Congrats Alex, this is to me a BIG result!

Edited August 28, 20205 yr by Marco Manieri

Now this is a nice catch, Marco! Amazing! 🙂

Normally I save all this stuff to allow LNM reloading of procedures (not contained in the examples). But some other data like version is helpful when debugging problems with flight plans.

Alex

It'd be nice if they threw you a few bucks for using your program...🖖

Are they in complance with the license agreement?

20 hours ago, pgde said:

Are they in complance with the license agreement?

Yup. GPL. Anyone can use it, compile it, modify it.

But if you modify it you have to publish the changes.

IANAL, though.

Alex