Unable to open navigation cache...

[bugman]

Hmmm, looks like you lost the backup copy. Could you create a text file with that name and the content '11024'? Make sure there is no *.txt extension (this is often hidden in the default Windows settings).

Cheers,
Edward

[Johan G]

Short question: The fgfs.pid file, is that just an ASCII file with the extension .pid holding the process id used by FlightGear the last time it run?

The only reference I can find after searching the wiki and later some Google searching is in flightgear/utils/TerraSync/terrasync.cxx (perm/b7ec7904), but I do not really get what it does or is used for.

[zakalawe]

It's a lock file, it doesn't have any meaningful contents. it should be deleted automatically when the process exits (even crashes). If you're seeing it, there is an FGFS process running, or something very abnormal happened.

[bugman]

For reference, please see the other thread.

Regards,
Edward

[eddgbc]

I was able to get 2017 version to load by following this part of the procedure on the WIKI page i was directed to:

"If it still crashes, rename the flightgear.org folder to flightgearBAK.orgBAK, which will fix the errors, but you lose your user settings, such as options you have set in sim (ALS, don't show fps / ms, etc), joystick settings, etc ... In case FG starts up well, you can restore these settings by copiing back the files from the backup directory."

By renaming the flightgear .org file it allowed the launcher to reload the Navcache..

It appears to be working and I have access to the scenery files!!

Thanks to all for the help...

[bugman]

@eddgbc: Would you like to help the FlightGear developers to finally confirm and eliminate this long standing bug? If so, could you:

• Confirm that you have a fgfs.pid file in your old flightgear.org fiolder.
• Rename the new flightgear.org folder.
• Copy - not move - the old flightgear.org folder back.
• Start FlightGear and confirm that you see the navigation cache error.
• Rename the fgfs.pid file.
• Start FlighGear and confirm that the error is gone.

This would be extremely valuable to the developers!

Cheers,
Edward

[pb321]

I got the same navdata.cache error mentioned above and sent in an error report (twice) I just did the procedure above and I can confirm it. After fgfs.pid was renamed and FG restarted, the small dialog boxes popped up and then the startup continued with the regular startup but I was at ICAO 5L2 Cyr Aviation instead of Bergen. I don't understand how I got to 5L2.

[bugman]

Thanks pb321! I've reported this on the mailing list thread discussing fixing this long-standing bug:

[Flightgear-devel] Windows nav-cache permission issue

Cheers,
Edward

[eddgbc]

I have repeated your request and can confirm that I was able to make the navcache error return and then go away and function properly.

That appears to be a good fix.

agian thanks to all for working this through!!