Hi

I'm new to the Sim world so I may be doing something obviously silly here!

I am creating some routes in Littke Navmap, exporting them as a PLN file and then importing them into FS2020.

On the whole this works well however there seems to be a bit of an issue on having FS2020 select the starting runway.  In this example I am taking off from RW05(North)  in the opposite direction from where I want to end up:

FS2020 imports this data however it doesn't seem to parse the starting runway properly and as such selects RW23 (south) then adds RW05 as a waypoint:

Lookling at the PLN file https://pastebin.com/Wi6m7d40 I think I'm missing the <DeparturePosition></DeparturePosition>  value, ive tried "RW05" "RUNWAY 05" "05" not FS2020 always seems to put me on RW23.

I think the issue is how I'm creating the route?

Thanks 🙂

 

I'm about to adapt the flight plan export for MSFS and will look into this for sure. The flightplan format looks equal on the first glance but it is not.
Extensions I can see are SID, STAR, approcaches (where are the transitions?).
Looks like starting positions are slightly different too. Meh.

Did anybody manage to select transitions in MSFS and add them to a flight plan?

Anyway, thanks for reporting. Good to know I have to check this too.

Alex

Hi Alex 

Thanks for the swift reply and for all the hard work you are putting into this, its certainly helping me learn loads!

I created a route in FS2020, set the runway to 05 and exported, I then set the runway to 23 and exported again.  The two resulting PLN files are exactly the same and when I import them into FS2020 the runway is always 23.  So i guess FS2020 doesn't support runway information on the PLN format.

It also exported two FLT files, these did keep the runway information intact and had a section for it:

[Departure]
ICAO=EGPF
RunwayNumber=5
RunwayDesignator=NONE

UPDATE:

I looked at some other tools and if you have <RunwayNumberFP>5</RunwayNumberFP> in the ATCWaypoint FS2020 picks up the runway!

Edited September 2, 20205 yr by hr83k8e

On 9/2/2020 at 6:51 PM, hr83k8e said:

I looked at some other tools and if you have <RunwayNumberFP>5</RunwayNumberFP> in the ATCWaypoint FS2020 picks up the runway!

I see. Good find. Will add this.

I just adapted LNM to add saving of SID, STAR and approaches (sans transitions since MSFS cannot deal with them 🙄).
It works most of the time but the rest is ... well.

I noticed that MSFS does not save start positions (gate, ramp and others) at all when creating and saving plans in the simulator. Needless to say that it does not accept starting positions like ramp or gate if you put them into the plan file like FSX and P3D do.
Loading of procedures: Quite often ok but then: MSFS invents departure procedures which are not in the plan or does not load procedures despite being saved correctly.

This cannot even load its own saved plans 😕. I checked MSFS created files for procedures and they were saved but on loading again: Nada.

At least it can load the en-route part reliably. Although, I cannot check for airways since these are not visible in the sim planner. Maybe in the Garmins but I did not check.

While writing about airways: MSFS has no concept of a maximum altitude or one-way airways as far as I can see. Still the same as FSX. So, don't be surprised if you load a plan created in MSFS and it does not work in other applications.

Hopefully it gets better over time. I can only encourage everybody to submit tickets if one finds issues.

Alex

On 9/2/2020 at 11:51 AM, hr83k8e said:

Hi Alex 

Thanks for the swift reply and for all the hard work you are putting into this, its certainly helping me learn loads!

I created a route in FS2020, set the runway to 05 and exported, I then set the runway to 23 and exported again.  The two resulting PLN files are exactly the same and when I import them into FS2020 the runway is always 23.  So i guess FS2020 doesn't support runway information on the PLN format.

It also exported two FLT files, these did keep the runway information intact and had a section for it:

[Departure]
ICAO=EGPF
RunwayNumber=5
RunwayDesignator=NONE

UPDATE:

I looked at some other tools and if you have <RunwayNumberFP>5</RunwayNumberFP> in the ATCWaypoint FS2020 picks up the runway!

How did you export as FLT files?

 

-Dave

 

When FS2020 exported it did 2-3 file formats all at the same time

 

15 hours ago, hr83k8e said:

When FS2020 exported it did 2-3 file formats all at the same time

You probably exported a .flt which contains aircraft state (more or less), flight plan and more stuff like weather.