Cycle 2602 Rev. 2 - missing waypoints in DB, FBW A32NX

Navigation Data General MSFS Data
1

Hi there,

I am having trouble today when importing Simbrief generated flight plans into the MCDU of the A32NX. I have the current dev version installed.

Example 1:

EDDL/23L COL6T COL DCT DODEN Y852 EDISA Y173 PABLA Y163 HERBI Y164 OLBEN Z50 ROTOS ROTO3M LSZB/14

The flight plan loads, but the waypoints DODEN and TUSIK (along Y852 behind DODEN) are not in the database, so I had to insert them manually.

Example 2:

LSZB/32 RAMO3A RAMOK Z143 BERSU N871 DITON T163 ZUE T125 ROMIR N851 LOKTA DCT TEDGO N851 LBU DCT ABUMO N850 NIE Z88 VERED DCT EDDW/27

The flight plan only loads after I manually removed waypoints between LBU and ABUMO (Simbrief had a route along an airway there), and no waypoints along Z88 between NIE and VERED are loaded.

Another thing I have also found is that ILS course values displayed in the A32NX MCDU often differ a few degrees from the values published in the charts. For LZSB ILS 14, the chart says 138°, but the A32NX MCDU displays 140°, and this value is not manually changeable.

Is there any way to tell if this is an aircraft or a navdata problem?

2

Sorry: It’s Cycle 2602 Rev. 2 I am on.

3

Hi,
Do you use any 3rd-party scenery? When yes, which one?

In most cases, such issues come from a bad/incompatible scenery package. Therefore, the question.

Also, which SIM do you use?

Cheers
Richard

4

Hi Richard,

yes, that is a valid question: I am on MSFS 24.

Thanks for the tip with the scenery. I was using the Orbx LSZB scenery - or at least I thought I was. I removed it now for testing, and found that the World Update LSZB scenery was active in the MSFS24 scenery manager, so it’s possible that earlier today both sceneries were active simultaneously, thus causing the conflict (still weird because optically it all looked like the Orbx scenery, so I’m not sure).

Anyway: I now deactivated the Microsoft scenery, reinstalled the Orbx scenery and right now I am not able to reproduce the problem. So I guess all is good for now.

Again: thank you very much for your assistance.
I have to say: Navigraph is always top notch in terms of customer service!

1 Like
5

OK, I did one more test and deliberately activated both LSZB sceneries. I reloaded the same flight plan and it is still working. So I have no idea what went wrong earlier today. May also have been some random MSFS issue. Still, the good news is: it’s working now.

1 Like
6

Hi Werner,
First of all, WOW, thank you very much for this kind feedback:

We do our best to get better and better - not only in the support, but also in our products :wink: … We haven´t reached the end of the development :wink:

Back to your issue:
Also, thanks for sharing your results. It could be that you had an outdated/old content.xml file, which will be re-created when you disable/enable default packages. This file is necessary for the package loading order, and the logic changed dramatically with SU3. Therefore, it is always a good idea, after a SIM update, to delete this file (with a backup first) and let the SIM recreate it. This “solution” ensures you use the latest version every time and avoids such strange issues.

Anyway, it´s solved, and that’s good. Enjoy the MSFS2024, thanks again for your feedback, and I hope you have a nice day - greetings from Vienna (sadly a little bit ill at the moment :face_with_thermometer:)

Cheers,
Richard

1 Like
7

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