March 7, 20242 yr I have a Navigraph subscription. Today suddenly I am having problems with procedures which can't be found (by the BATC beta) or wrong procedures being assigned (FSHud). It's as if the navdata is corrupted. I also noticed procedures are missing in my Vision Jet G3000. I uninstalled the navdata and reinstalled it but that didn't solve the problem, Is there any way to troubleshoot navdata...? And while I am at it: is there also a way to verify MSFS without it causing a complete reinstall? I have the Steam version. Yesterday MSFS wouldn't start and after a PC restart some settings had been reset. Perhaps more has been reset somehow... Edited March 7, 20242 yr by tup61
March 7, 20242 yr Author 1 minute ago, Matchstick said: Which procedures are you missing and can you see them in the web Charts app ? Can't remember the exact ones unfortunately... But my G3000 showed an RNAV approach for one runway while the opposing one wasn't there (and should be there according to Charts). Also FSHud wanted me to select a runway 24 while all I could see was a runway 23. I did so much troubleshooting afterwards that I forgot which airports I gave a try and checked.
March 7, 20242 yr Just now, tup61 said: Can't remember the exact ones unfortunately... But my G3000 showed an RNAV approach for one runway while the opposing one wasn't there (and should be there according to Charts). Also FSHud wanted me to select a runway 24 while all I could see was a runway 23. I did so much troubleshooting afterwards that I forgot which airports I gave a try and checked. All Garmins use the MSFS navdata format (which gets updated by Navigraph). This format has a big flaw (since... well 2020): If the runway designator changed (which is reflected in the Navigraph data and charts), but the scenery has the old designator, it will not recognize procedures for this runway. E.g. RW24 becomes RW25 in real life and Navigraph, but the scenery still has RW24. No workaround, sorry. Only airliners with custom navdata formats (Fenix, PMDG, CRJ) do not have this flaw. For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
March 7, 20242 yr Author 12 minutes ago, Fiorentoni said: All Garmins use the MSFS navdata format (which gets updated by Navigraph). This format has a big flaw (since... well 2020): If the runway designator changed (which is reflected in the Navigraph data and charts), but the scenery has the old designator, it will not recognize procedures for this runway. E.g. RW24 becomes RW25 in real life and Navigraph, but the scenery still has RW24. No workaround, sorry. Only airliners with custom navdata formats (Fenix, PMDG, CRJ) do not have this flaw. Well... that would be a great coincidence that I've chosen 6 airports in a row that have those kind of problems...! Just checked LSGC and indeed, in the sim there is a runway 06 while Charts say the runway should be 05. However, I also had problems with a SID (LIMF SRN6M) which turns out to be a transition of a SID SIRL6A instead. Odd stuff.
Archived
This topic is now archived and is closed to further replies.