Reopen Navigraph Hub - 2020 - Shows 777 Navdata packages as not installed

Navigraph Hub
24

There wasn’t a real problem to begin with, except for the screenshots with errors from the HUB app. It was no problem for me to get it working, but I wanted to know why those errors arose.
My navdata was already working but after the “send us the log file”, I’ve checked that log file myself and saw that it was unable to write to the community folder of the 777-300er, in my case because of a corrupt junction (a functionality of the OS) pointing to a no longer existing folder somewhere else on my system. I’m guessing I’m one of the few out there fiddling about with folders, links etc so nobody really noticed what’s happening (anymore)
All in all it was a back and forth, support hesitating to accept that there’s anything written to the community folder, and several attempts to suggest otherwise failed. But now it’s clear that that particular addon has some other (older way of doing things) method of handling the navdata.
All in all I’m glad it’s sorted out..
FS2020 PMDG 777-300er wants its Airac navdata in the community folder. After starting the sim, it will copy itself to the work folder.

Thanks for your input nonetheless!
Cheers
Roel

25

Hi Roel,
Finally, we have changed the path now internally for the MSFS2020 777.-300ER and F too.

Based on this topic and our tests, we have now figured out that the MSFS2020 PMDG T7 also uses the work folder as its main data folder. So there is no reason to install the files in the community folder any longer.

From now on, when you make an update, the AIRAC files will be installed only in the work folder.

It makes one thing easier for us, too, thanks to these postings.

Cheers
Richard

26

That is indeed good news. If I in any way came across as ignorant or stubborn, I do apologize but I was certain this was as mentioned a niche case scenario worth investigating.
Cheers!

27

I must apologize. I was so sure that all addons are working in the same way, but we have forgotten PMDG :slight_smile:

Anyway, hopefully fixed now, and by the way, it was an important posting because we have figured out that we can close a workaround, and emotions are allowed (sometimes) :wink:

Thanks again for your time and your patience,
Richard