I find that the development version of the FBW works fine with IFR flightplans from the worldmap.
At least on my last two flights I had no issues. One discontinuity or so, maybe.
I don’t fly thre aircraft much however, maybe it was just luck.
1 Like
Please don’t take this as nitpicking but this is not a GPS fix. It denotes the intended groundspeed and altitude:
I quote from the LNM Manual:
35.3.3. Speed and Altitude
Cruising ground speed and cruising level not separated by a space.
Speed is prefixed with:
K: Kilometers per hour followed by a four digit value.
N: Knots followed by a four digit value.
M: Mach followed by a three digit value. The mach value is converted to knots ground speed assuming standard atmosphere conditions at the given flight altitude.
Altitude is prefixed with:
F :Flight level in three digits.
S: Metric flight level in three digits of tens of meters.
A: Altitude in hundreds of feet in three digits.
M: Altitude in tens of meter in four digits.
Examples:
N0410F310 410 knots at flight level 310.
M071F320 Mach 0.71 at flight level 320.
K0790M0710 790 kilometers per hour at 7,100 meters.
1 Like
Now this is interesting, I will try that! Thanks for the idea.
I have a problem I am hoping ya’ll can help me with. I have a subscription to Navigraph. I use Simbrief and the latest AIRAC information. I did a flight yesterday from KDEN to KDFW. I entered the info in the flight computer in the FBW A320. Imported the info from Simbrief into the ipad before entering any info into the flight computer. I got my clearance for my flight which told me to take off on runway 8 and climb to 10,000ft. All good up until this point. I reach 10,000 ft and ATC never clears me to climb higher. After a while I have to request a higher altitude. I have to keep doing this until I am finally cleared up to my filed cruising altitude of FL360. What did I do wrong? This happens on every flight I make using Simbrief. If I don’t use Simbrief and just make my flight plan on the World screen in MSFS, ATC will respond and give me higher altitudes. But the next flight if I use Simbrief I am back to only getting clearance to my climb out altitude. I have to request all further climbs. Any ideas what I should be doing?
You didn’t Load the SimBrief flight plan into the World Planner prior to pushing FLY. You would have needed to download the SimBrief flight plan to the correct location on your PC first of course.
I didn’t load the Simbrief plan into the World Map. Is that where I went wrong? Because I have tried that before and MSFS adds in a bunch of junk waypoints and messes up my arrival.
Sorry I’m not understanding your second sentence.
I think fundamentally, you need a cruising altitude shown in the “NAVLOG” screen in the world map. That’s what ATC uses to set your cruising altitude for an IFR flight.
If you follow FBW’s instructions to the letter, you only pick a departing airport and gate/ramp and click “FLY”, then load the flight plan in the MCDU. In this case, ATC only clears you to your initial climb altitude.
On the other hand, LNM with its Navigraph nav source turned off, uses exactly the same navdata that exists in the FS2020 simulator – which it connects to in real time. And its free. So much simpler! 
3 Likes
Im utterly 
because after all this effort - my A320NX will only follow the first leg of the flight plan.
I was so excited learning the systems that I now have a decent understanding of how it all works (on a casual level).
I tried for 5 hours to crack the flight plan follow issue including trying the Dev version of the A320NX.
I have ensured the autoflight system is in Managed Mode. It flawlessly tracks the first leg of the route - but once it gets to the first waypoint it just ignores the rest of the route and keeps chugging along straight and level.
I’ve lost too much time trying to fix it so in desperation to enjoy the A320neo Im back in the stock Asobo version for now.
Thanks to all of you in this thread for your help! When I recharge I’ll take another look at the A320NX!
Oh you’re absolutely right! I only looked at N038 and never read further. For GPS it should be eather E/W, no F
Ok so until Asobo gets ATC right I will fly without ATC. Thanks for the information.
This is why you should set the MSFS Sync option set to NONE in the EFB. That way, when you load the SimBrief flight plan to the world map, it doesn’t add the junk waypoints to the FMGC. The SimBrief plan that’s loaded on the world map is used only for the ATC purposes (including the cruising altitude), but the flight computer will use the flight plan that was imported directly from SimBrief (which will have the exact same cruising altitude).
3 Likes
But it won’t have exactly the same navdata / waypoints etc. as what’s in the sim unless you’re ponying-up around 100 bucks each year for a Navigraph subscription.
A great explanation thanks, will bookmark this. I was wondering what the reason for all that was.
1 Like
ATC works fine for me. Maybe there is another explanation.
You don’t have to pay for the whole year for it. Just subscribe for one month, get the navdata update for the sim and also unlock the same AIRAC cycle in simbrief, then unsubscribe. Then you should be using the same navdata in both SimBrief and the sim for a while.
There are other ways to get it that won’t cost you hundreds of dollars. Just need to get creative.
I’ve discovered the bug causing this. And it’s not the MSFS World Map’s fault. Rather, if your .PLN contains VOR waypoints, then the FBW’s FMS imports them, but then pushes them all to the end of the flight plan! So they end up being bunched-up together before the Arrival section, rather than being correctly spaced-out amongst the other waypoints throughout the flight plan.
Consequently these misplaced VOR waypoints in the FBW’s FMS cause the later parts of your flight to be screwed-up. It’s not the fault of World Map or the .PLN file.
I tested other aircraft which don’t use FBW’s custom FMS coding and they don’t have this problem. You can try this for yourself with the error-free .PLN file that I have attached which contains VOR waypoints intermixed with regular GNSS waypoints.
Ps. I think this kind of bug should be fairly straightforward for the good folks at FBW to isolate and fix
KLAX KJFK_06L.pln (19.6 KB)
Thank you! I will try this today and see if it works for me.
Ok so I tried the solution yesterday that MeoKingRthur suggested. It worked well until final approach. Then the plan had me doing circles about 12 miles out from runway 17L at KDEN. The approach was all messed up. I’m going to go back to just importing Simbrief into the EFB and FBW A320 flight computer without using the World Map. I’ll just keep requesting higher altitudes from ATC until I get to my filed cruising FL. Either that or just stop using ATC. Thanks for the suggestion though.
I don’t know why you’re having this problem but I assure you that loading the Simbrief plan into the world map works perfectly. I’ve done dozens of flights this way since game release and never had a problem. Except for the usual bizarre ATC behavior which I just ignore.