STAR Waypoints missing in A320

[tsprinzl]

On many approaches the STAR waypoints are not loaded correctly into the A320, don’t know if this is a known problem. Here some screenshots from my recent KORD-KATL-flight.

I generated the FPLAN with Simbrief, loaded it into the Charts App and pre-selected the ILS approach with the desktop Charts app, exported the MSFS plan and loaded it before I started the flight. Here’s the plan: KORD/28R DCT CMSKY DCT CARYN DCT CYBIL DCT PXV J73 BNA DCT NEWBB DCT IHAVE DCT MTHEW CHPPR1 KATL/ZELOW.I26R.

Plan is loaded correctly into the FMC, I manually added the ILS approach:

However, the waypoints of the STAR are not loaded correctly:

Here is also a screenshot from SimToolkitPro showing the actual deviation from the original plan:

I’m using the FlyByWire Mod for the A320, hope it’s not related to that because I really don’t want to step back to the default A320… Navdata were updated today with a clean install of Beta17. And the simulator was newly installed 2 days ago due to a hardware upgrade.

The strange thing is, that sometimes the STARs are loaded correctly, but in about 50% of my approaches I have the STAR waypoings missing.

Is that a known issue, anything I can do on my side?

[NAVDataOld]

Hi …
thank you very much for the details and the screenshots. I guess it´s more a sim-issue as a navdata issue. I have loaded the CHPPR1 STAR with the BBABE transition into the TBM930 and here the sequence which we have in our data seems to be correct:

… and here the ILS26R with the ZELOW transition

So, I guess, it´s more a A320 issue (not the mod - I guess, its more the basic features underlying the mod). Sorry, but as you see the waypoints are in the correct sequence in our dataset.

Cheers,
Richard

[tsprinzl]

ok, thanks anyway - I’ll try to stay patient

[Ethreven]

Hi,
I can confirm what Richard wrote. I investigated the same issue. A320Nx doesn’t transit all waypoints STAR or SID, TBM does. However, MCDU contains all needed waypoints. For example; SID at LOWI airport ADIL2J. SID looks like this:
RW08
RUM
OEJ
INN
ADILO

After takeoff, A320NX begins SID procedure but only to RUM waypoint then suddenly turns right to INN, omitting OEJ. It’s probable you end up your flight on the mountains surrounding Innsbruck because INN waypoint is on the top of the mountain.

[AuFinger]

Have you shared this info with the FBW team? This documents the issue well. I believe they’re panning to do custom planning system, so curious if that would solve this MSFS issue?

[jbburrows]

The FBW knows about this and does nothing to fix it. They said they are working on a collab with WorkingTitle that will fix it.

They actually have been quite rude about it and don’t seem to care

[AuFinger]

I’ve reported some bugs and found some developers to be defensive and argumentative. Programmers don’t always have people skills.

If the answer is the full redo of the planning system via WT, that’s fine.

BTW, I went out searching for this issue after doing the same approach into ATL. LOL. It’s so frustrating to put in a STAR and the SIM does a lazy general route with no points.

FWIW I found using Pilot2ATC is a workaround. I load my plan via SimBrief into Navigraph. Tweak things to my liking. Then load the route as text from SimBrief into Pilot2ATC. Set up the SID, STAR, APPR in Pilot2ATC as I determined in Navigraph. Then export to file. Then import into MSFS. Don’t touch a thing and load it. It will have everything perfect. Pilot2ATC does altitudes and 32nx will even follow the altitudes on managed alt all the way down the STAR. Just don’t change your approach in flight, otherwise MSFS might happen.

Alternatively, you can just put in your origin and destination into Pilot2ATC and it will auto do your route for you. Then export for MSFS. Just depends how much you like the planning part of things.