It has been over a year since this prior conversation, and Navigraph Hub continues to be an immensely frustrating experience for me each month when I go to update my Navdata.
To recap:
When clicking update, many times my computer fans spin faster than they do under peak loads within the sim itself. What is being done with all that power?
The updates themselves often take several minutes to complete, which would be fine, except…
Sometimes after waiting for even ten or fifteen minutes, the “Updating” flag never goes away, but if you go to another tab in Navigraph Hub or if you close it and reopen it, the button has reverted back to either “Update” or “Install”.
Sometimes you click update, it transitions to “Updating” and then reverts back to “Install” for some reason.
Sometimes when you click update, it transitions to “Updating”, then to “Remove” indicating it updated successfully, but if you go to another tab or reopen the Hub app it’s back to showing “Update” again. Sometimes it does this without even having to close the app or navigate to another tab, it’ll go from Removed back to Update on it’s own.
I don’t mean to be rude, but it boggles my mind that this state of affairs seems acceptable to other simmers or to Navigraph. Please, I’m begging you, make your installer app more robust and reliable!
Hi,
The main issue is the number of files in some packages. As an example of the TFDi, it contains over 100k files, mostly small files of 1-5 kB, which require a lot of I/O bandwidth. The Hub downloads the package, decompresses it, and copies the files to the correct location. All that needs time, and therefore a package with 2-3 files is much faster (like the PMDG database) than a package with several thousand files.
In most cases, it has nothing to do with your internet connection. It depends more on the IO transfer rates.
That’s the current process, but we have a task to improve the Hub to version 2.
I’m not aware of any PMDG issues in the last couple of cycles. The great “break” was when ASOBO/MS changed the logic (I guess this was with SU3), and all 3rd-party add-on devs had to rewrite their code to get the latest data. But all in all, I don’t know about any package issue with PMDG.
So, not all add-ons work when TFDi works as expected … I assume there’s an internet issue on your end. For more analysis, we need the main.log file to provide a clearer answer, but in general, it is not related to a package.