What on earth is going on with the Flight Planner!

Be careful if you edit this file, it’s in “Official”

:skull_and_crossbones: - I DO NOT RECOMMEND YOU EDIT ANYTHING IN “OFFICIAL”, UNLESS YOU REALLY KNOW WHAT YOU ARE DOING - AND THE RISKS INVOLVED

…\packages\Official\OneStore\fs-base\worldmap\WorldmapFilters.xml

The idea way to deal with this is to start MSFS with a batch/cmd-script file, and have that search/replace edit the above XML.

That way, when the sim is updated, and files in Official change, chances are the search/replace will work with the new file, and continue to work.

or whatever other method you want to use.

Just remember, if you just edit the file once, it might be overwritten, if you change any other item in the UI of that page in the sim.

Asobo really need to fix it, so it remembers changes done in the Sim on that UI page, for those last 3 items (like it already does for all the other items on that page)

2 Likes

Thanks Sir

Not sure if this is my ignorance (def possible) but when I create a flightplan in LittleNavMap it gets badly distorted in MSFS. I created a plan from EG13 Glenforsa flying first over Oban then over a nearby loch to line up for Oban airfield. When loaded into MSFS the route is changed so that it goes north of Oban airfield (to get on an approach path), then south to Oban, over to the loch then onto the Oban airfield. So why is MSFS changing a prepared flight plan? It seems nuts, but maybe a by product of all the other problems with flight plans.

This is the exact bug I reported to Zendesk. I took screenshots of the flight planner and the MFD in flight, and uploaded these with the .pln file that I imported from LNM. It is due to the TIME waypoints that MSFS inserts into your VFR flightplans. I think they are trying to recreate TOC and TOD but it has been implemented really badly. It places the waypoints on the departure and arrival runways as per the flight plan. The problem is when you add in POIS as waypoints that are close to the departure or arrival airport it still wants to go to the AI-inserted waypoints first, then to the added POI and then back to the destination airport. If they remove this peice of code that auto-inserts these then all our problems will be back to pre-SU5, and importing or creating VFR flight plans will be back to how it was (good or bad :slight_smile: )

No worries, with the way they make unannounced changes to the sim, I thought maybe it had finally been fixed, LOL

Hence, my previous comment about all these mysterious CTD’s lately. If the dev’s would just get some of this simple, basic stuff working correctly and with a purpose, maybe people wouldn’t have to resort to “hacking” things.

I’m not a programmer, but this shouldn’t really be THAT difficult, should it?

Anyway to me, if it defaulted to the basic aviation stuff and made those interested in fauna, poi and other VFR stuff have to turn it on everytime - it could at least be called a flight planner.

1 Like

The most amusing one is that when you create a plan and it adds those new climb and approach points - which is annoying but not a game killer - and then add an enroute waypoint some distances away, it some times inserts the enroute waypoint IN BETWEEN the approach and the runway.

So you get to fly to the new MS runway approach, back track 100 miles to your new enroute point and then turn around again and fly back direct to the airport itself.

2 Likes

There is even more that needs fixing……

Maybe they’ll add an AI refueler aircraft that you can summon by using the fancy handle bar so you make it to your destination…Yeah, that’s realistic.

Have you guys been voting in here and uploading Zendesk tickets? Please do!

1 Like

Thanks Craig. Reassuring to know it’s not me. Amazing how much SU5 has screwed things up - visuals not so good (pop ins for me), trim not woking (really bad) & now this.

It is beyond Crazy that this needs votes to fix. It is absolutely Garbage and needs to be fixed, it is horrific. But FWIW I have voted lol

1 Like

Comparison between a “Little Nav Map” generated Flightplan (left) (that mostly follows the MSFS SDK), and the current after SU#5 MSFS one (Right) , that DOES not even follow it’s own SDK. !!

2 Likes

Interesting. I’ll try the same thing tonight with a simple VRF direct GPS flight.

Isn’t that just a decoding issue, your text editor is reading the UTF-8 characters as if they were ASCII?

I don’t think so as I have looked at the FP in a multitude of TEXT editors, with and without UTF-8 decoding.

And those so supposed to be UTF-8 character strings are not correct in any case, so the forced pre-encoding is wrong.

Then if you edit the FP to put in the Correct UTF-8 character strings, then now correctly edit plan with correct UTF-8 codeing, CRASHES the sim, when loading the FP, so the MSFS UTF-* decoding would also be incorrect, (but is compatible with the MSFS incorrect forced pre-encoding)

Then, why in some cases, is the Departure airport, with MSFS encoding UTF-8, sometimes Totally missing in the or

Then the next obvious question is – why is a “corrupted” XML FP file, causing the Sim to CTD, and is not being caught by some Data verification and error checking ??

1 Like

Yikes… Yeah that does not sound good at all.

Agreed!!!

1 Like

Prior to SU5 I started working on a comparison of flight plans between different flight planner programs, World Map, Navigraph, SimBrief, and LittleNavMap. Used the same departure and destination, SID, STAR, Approach. I let the program perform the routing. They all created different flight plans! I did not check VFR flight plans.

Because of SU5 broken flight plans and waypoints not inserted by the user, after WU6 I’ll recheck the different flight planning apps to see what differences remain. (Assuming flight plan fixes are in WU6…)

Sounds good … Nice to see someone actually taking the Flight Planning side seriously AND prepared to help towards a better understanding and a solution – as opposed to just moaning and crying that “it is Broken”

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.