[BUG] Export Charts Retention + File Format Save Bug + Feature Request

[trevxc]

1st Bug:

When exporting a flight plan to the Microsoft Flight Simulator 2020 (.pln) format - it does not retain the appropriate approach, it defaults back to “final” when I wanted it to be “transition” The transition I picked bleeds into final. It should retain the settings last known.

RNAV Z RWY 17L
Transition = FSHER

2nd Bug:

When exporting flight plan, it replicates .pln.pln.pln over and over each time a new addition is saved…then I need to go and format it to NAME.PLN in my documents folder. In addition, if I modify the name before save to “name” and select the dropdown of .pln (default) it still saves extra dots prior to the appended .pln extension.

Request in relation to this:
Can we please have the last known export flight plan / save location be the default when exporting multiple flight plans? I have a pretty organized file structure on my computer and its kind of annoying to re-navigate to it each time.

[skysail]

Hello! Thanks for posting this and sorry for the late response, this went under our radar.

For any future topics, please split each issue into a separate topic!

@trevxc

When exporting a flight plan to the Microsoft Flight Simulator 2020 (.pln) format - it does not retain the appropriate approach, it defaults back to “final” when I wanted it to be “transition” The transition I picked bleeds into final. It should retain the settings last known.

Are you still having this issue? It sounds like a possible navigation data mismatch or an issue in the simulator itself. Perhaps this topic could be of interest:

Differences between exported PLN and MSFS world map

Initial inspection This flight looks like this in Charts: [image] And this is MSFS: [image] So far so good, as far as I can see! Same procedures, same waypoints and same route. It is worth noting that MSFS does not simplify their “route pills” by showing the procedure names, instead showing the waypoints that they are made up of. For example, TEETO, JAAZZ and FITZY are all part of the approach: [image] But MSFS displays them as separate route items in their pills: [image] The result …

---

@trevxc

When exporting flight plan, it replicates .pln.pln.pln over and over each time a new addition is saved…then I need to go and format it to NAME.PLN in my documents folder. In addition, if I modify the name before save to “name” and select the dropdown of .pln (default) it still saves extra dots prior to the appended .pln extension.

This sounds related to this topic:

MSFS Export File Extension is Wrong

When exporting a Charts 8 file to MSFS, it is assigning the extension as …pln.pln.pln . If you edit the extra .plns before exporting, you still end up with a …pln as the export. kphxkont…pln File has to be manually edited after export before MSFS will read it.

Can you still reproduce this issue? I am not able to, so it should have already been solved.

---

@trevxc

Request in relation to this:
Can we please have the last known export flight plan / save location be the default when exporting multiple flight plans? I have a pretty organized file structure on my computer and its kind of annoying to re-navigate to it each time.

Feel free to make that a Wishlist topic! This one seems related:

Have the ability for flight plans in Charts to export to multiple locations simultaneously

On the PC version of Charts, the export function remembers only one location to export a flight plan to. With MSFS each aircraft variant, ie PMDG 700, 800, 900 all have their own flightplan folders that are unique. Most of my flightplans can be used with any of those variants, but as it stands I have export to one folder and then copy the flight plan to each of the other folders of variants that contain compatible aircraft variants, which can be tedious, particularly how deeply buried the folde…

Kind Regards,
Malte

[greg100o]

Any update on this issue of being able to export to multiple file locations simultaneously? No one else seems interested, or no one has seen the wish-list to comment.
It seems that this should not be difficult to implement, but I may be totally in the dark about the feasibility.

Thanks,

Greg

[skysail]

You are free to share it around to get as much exposure as you want! I’d say that many users would prefer to use the SimBrief integrations built into their aircraft over having to export PLN files. Personally, I prefer programming the route myself most of the time!

@greg100o

It seems that this should not be difficult to implement

It is not as simple as it sounds, no. But it is it is doable if our users think we should prioritize it over VATSIM features, Navlog etc etc, all higher up on the wishlist at the moment!

Kind Regards,
Malte