Hello, I have noticed on more than a few occasions (dating back quite some time ago, to when I first starting using ProSim737 in 2022) that occasionally waypoints are missing on various STARs.
One example I can give (the others I did not record, but I will start keeping a log) is WAPPL7 into KHOU. Specifically, all four (4) waypoints between WAPPL and PUSHN (as shown on the Jeppesen chart) are missing. Again, this is not an uncommon occurrence, and the WAPPL7 issue has spanned several AIRACs (that I’ve noticed), with the most recent being AIRAC 2513.
Btw, I searched ProSim’s forum for info on this issue. As of this post, I found no recent mention of “missing waypoints”, so (therefore?) it must be a Navigraph issue? Perhaps it is the way ProSim is loading/processing FMS Data Manager AIRAC updates that is causing the problem (yet no other ProSim user is noticing/reporting it)?
Hi,
It looks that the issue is more on your end/system, because I’m unable to reproduce it. We offer the complete correct sequence when you use the FMC/MCDU correctly. Possible an installation issue?!
My addon mapping is “ProSim737 2.24b1 (and above)” for the ProSim737 B738 product. Is that the same as your Airbus? If not, can you please check the 737 Navdata add-on? My installation updates normally (as far as I can tell); the ProSim database rebuilds without a problem after any update, and my ProSimIOS app indicates the current AIRAC is installed….
Hi,
Yes, it is the same database. When your installation path is correct, I would recommend asking ProSim if someone else can reproduce it. I can’t, as you can see, sorry…
My MFS Data Manager installation path for ProSim is correct (C:\ProgramData) according to documentation and convention.
I posted on the user-to-user ProSim forum and another user indicated he encounters the same problem (and posted a screenshot of the missing WAPPL7 waypoints in his FMC/CDU).
At this point I don’t know what to think. I wish Navigraph could reach out to ProSim and advise them of the issue (definitively stating the problem is not with Navigraph). Otherwise, I’m stuck manually entering waypoints on a lot of STARS, which can cause problems with ProSim when there is a runway change on arrival. It’s an utter mess at times. Oh well.
Possible that it is a handling error on your side, and you have forgotten to add the approach, but as you see, it works in the A320 and also in the B738. So, it is not navdata related. When you still mean, that there is something wrong - please open a ticket at ProSim.
This is not a navdata or installation issue, it seems more a user issue or a bug in the CDU.
Hmmm…. I always select a runway when programming the arrival. My s.o.p. is selecting the Runway approach first, then the Arrival, then the Transition (from the route). Are you performing the sequence by selecting the Arrival/Transition first, then the Runway approach?
Well…… (deep subject), first of all, thank you, Richard, for taking the time to invistigate this issue, with both ProSim products. Much appreciated!
Anyway, I took some time to investigate further on my end (knowing that there does not appear to be a problem with the Navdata) and (for the benefit of any ProSim737 B738 user reading this) I observed the following issue / bug with ProSim (as of at least v3.35.1):
When programming the arrival (WAPPL7) along with a runway approach, the four waypoints in question (see above) do indeed appear in the LEGS page. HOWEVER, subsequently selecting a Transition (from the route onto the Arrival, e.g. AEX) causes the four waypoints in question to dissapear from the LEGS page.
Quirky bug, and it doesn’t happen with all STARS. Makes me wonder what is so special about WAPPL7 and a few others I have encountered (that unfortunately escape my memory).
I guess problem solved (it’s likely a ProSim bug), unless further analysis of the navdata is warranted, i.e. maybe something in particular/peculiar (in the navdata) is triggering ProSim to delete waypoints when a Transition (from the route to the STAR) is selected……
