Missing RNAV waypoints in SIDs

User Support Hub Aircraft & Systems
, , ,
1

Hello everyone,

can anyone confirm if this is a general issue or an issue thats limited to my installation? :thinking:

Short summary of the topic:
RNAV waypoints (in SIDs) appear in the procedure (at least their identifier), but not in the map as soon as an addon of the bespoke is installed (for some, not all). As a consequence those are skipped when flying the departure.

Details:

  • No additional AIRACs installed (Navigraph or similar) - MSFS native only
  • Tested in WT G1000Nxi (see screenshots)
  • When addon-sceneries of the bespoke airports (here: Simwings EDDH, Aerosoft EDSB) are not installed all works fine as expected:

(picture shows IDEKO7B @EDDH and GAGSI1Z @EDSB)

EDDH_SID_IDEKO7B_complete.PNG
EDDH_SID_IDEKO7B_complete.PNG1920Ă—1014 158 KB

EDSB_SID_GAGSI1Z_complete.PNG
EDSB_SID_GAGSI1Z_complete.PNG1748Ă—851 125 KB

  • When bespoke addon-sceneries are installed, the waypoints appear correctly in the FPL menu but details are missing and in the map view on the right side a direct to the last SID point can be seen as a consequence

EDDH_SID_IDEKO7B_missing.PNG
EDDH_SID_IDEKO7B_missing.PNG1617Ă—851 105 KB

EDSB_SID_GAGSI1Z_missing.PNG
EDSB_SID_GAGSI1Z_missing.PNG1920Ă—967 155 KB

  • Interesting thing: Fenix320 still has the waypoints available (also when the addons are installed):

EDSB_SID_GAGSI1Z_complete_Fenix.PNG
EDSB_SID_GAGSI1Z_complete_Fenix.PNG1433Ă—1354 141 KB

I’m wondering

  • is it a general issue with the addon airports or any conflict of different databases on my system only? can anyone reproduce the situation?
  • how is the Fenix320 able to load the RNAV waypoints no matter if with or without (possibly conflicting) addon scenery?

Thanks a lot guys :+1:

1 Like
2

What happens if you use a Working Title G3000 or CJ4 FMS? There’s a few variables in play here.

3

Same like with WT G1000 - showing all waypoints correctly in the “sequence” area, but not on the map :smirk:

EDSB_SID_GAGSI1Z_G3000.PNG
EDSB_SID_GAGSI1Z_G3000.PNG786Ă—415 34.1 KB

EDSB_SID_GAGSI1Z_G3000_2.PNG
EDSB_SID_GAGSI1Z_G3000_2.PNG829Ă—471 40.9 KB

4

Have any of the Third Party airport makers responded to help tickets filed with them?

5

I bounced this off the good folks at Working Title since they have a stock-navdata-channel that sometimes takes a look at these types of issues. Observations that might be useful to the airport makers should you decide to relay them:

They probably have the navdata replace flags on in their XML (the scenery devs, that is).

Fenix is not affected because it doesn’t use the sim data, it uses it’s own Navigraph database (which you have to have a Navigraph sub to update, BTW)

6

Didn’t file any yet - I first really want to make sure it’s a thing on their side and not my own fault… So for you it seems like a general issue?

7

it seems to be an issue specific to the third-party airports - which are the common denominator so far. I would start by passing those comments by Working Title back to the makers of the ones you own and see what they find.

8

Thanks! So we’ll patiently wait and see if anything will change over time :wink:

Just out of interest - can the scenery xml value changed manually? as a short term fix until an “official” solution will be published…

9

No idea I’m afraid - I don’t edit anything in the SDK, so I’ll defer it to others who know better. Are you planning to let the makers know?

10

ok, yes of course. Just wondering where to start because basically all addon airports I known are affected :roll_eyes:

11

understood - in the meantime I figured out that basically all addon airports I own are affected. Just like @EDSB and EDDH, also EDDS, EDDN, EDDL are affected…
What would you recommend? I mean posting in all forums might not be the way to proceed. Especially since I’m quite sure this hasn’t always been a thing, I remember from before the last SimUpdate the waypoints had been there…

12

Start with one vendor and see if they can figure it out. Then if they do, you can pass that info along to the others. Or point them all to this thread so they can see the Working Title comments.

13

We also talk of this problem here:

14

Thanks for your input so far!

I opened a ticket @AerosoftDev and linked the two cases described here in the official MSFS forum. Lets see what they can figure out :slightly_smiling_face:

15

Update - first feedback from support @AerosoftDev:

"Hello,

Thanks for contacting us.
Unfortunately, this issue is due to a problem with an earlier version of the sim/sdk, and the developers of these sceneries are aware of the issue and have been working on patches. Most of these should have an update out to resolve this soon! In the meantime, if you have Navigraph installed as your main sims database, it should bypass the problem."

I asked if they can be any more precise about “soon” - lets see what we’ll get. But as far as I see this seems to be the solution - patiently waiting for patches… :melting_face:

16

Hi,
updates are on the way

1 Like
17

Hi,
which airports did already receive their updates?

18

some airports have already received an update.
e.g.
Cologne
Brussels
Trondheim
Bratislava
Hamburg

19

I updated my EDDH and Nolgo STAR is just NOLGO to EDDH (Same for e.g BOGMU etc). Using MSFS Navdata and the FBW A320.
this product is unuseable to me right now. Wish I didnt buy it right now because in the current state its a waste of money.