WAJJ IDIN1A broken

Using Navigraph (2401r1) and SU15, in the SWS Kodiak, WAJJ SID IDIN1A seems broken (instead of intercepting JPA radial 191° [correction: 175°], it plans to return to JPA). This is visible in the MSFS World Map and in the G1000. The procedure is interpreted correctly in Little Navmap.
Who is likely to own this issue – WT, Navigraph, Asobo, or SWS?

(For SOME reason, the forum “auto-corrects” the subject removing all my precious CAPS. [edit: Ah, it doesn’t like when the subject is ALL caps. fixed])

DISREGARD, also happens with Navblue data (ie. when I remove Navigraph data from Community).

Sorry for re-opening this: WT says that it might be an issue with upstream data (quoting: “source arinc pointing to facilites that can’t be found in the sim”).

Maybe you can have a quick look at the data and let me know whether I should press the issue with Asobo/WT?

Hi,
I think you have answered your question by yourself … it´s no navdata issue, nor do miss something because when it would, our chart-app (or in your example LNM) wouldn´t also shown a correct path.

Here from our chart-app:

… and here from LNM - but now using the stock navdata from MSFS:

Both apps shown exactly the same path, no return back to JPA … so, when really anything is missing why can LNM shown the correct path with the default stock navdata then?

No, this is 100% a coding issue somewhere in the ASOBO/WT world. As a third reference, I have tried the same with the PMDG, which uses an external database from us:

Also here, a perfect path - so the data are complete and correct. In our data and also in the stock MSFS (NavBlue) data. The interpretation of the data are incorrect and therefore you get a so bad result.

Sorry, thats 100% a bug from ASOBO/WT.

Hope that helps,
Richard

Thank you so much for checking!

1 Like

No probs - you´re welcome :wink:

Have a nice weekend,
Richard

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