zakalawe wrote in Fri Sep 27, 2013 8:51 am:What happens on successive launches after the first one? it sounds as if you're experiencing a nav-cache build *every* launch, which would be bad, and needs to be explained. It's something related to particular setups, but you will need to figure out what. Running at log-level=info should tell you why the cache rebuild was triggered (scenery paths changes, timestamp of a data file changed)
The behavior is consistent. I was careful to test for successive launches. After several tests, I uninstalled, and checked to see if any registry artifacts were left behind and there were none. Previously, there were some, and I was suspicious of that. Not this time.
The flightgear.org directory was left behind after uninstalling, and there were two log files in there. One, fgfs.log is 125K, and too long to post, but I looked it over, and found near the top
view:3:..\..\..\flightgear\src\Viewer\splash.cxx:410:Splash screen progress loading-aircraft-list
view:3:..\..\..\flightgear\src\Viewer\splash.cxx:410:Splash screen progress loading-nav-dat
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:216:NavCache at:Path "C:/Users/PCUser/AppData/Roaming/flightgear.org/navdata_2_12.cache"
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1197:NavCache: main cache rebuild requirednavaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:216:NavCache at:Path "C:/Users/PCUser/AppData/Roaming/flightgear.org/navdata_2_12.cache"
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:234:will create tables
general:3:..\..\..\flightgear\src\Airports\apt_loader.cxx:132:Data file version = 810
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1241:apt.dat load took:31106
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1250:fix.dat load took:12792
navaid:4:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1974:findAirportRunway: unknown airport/runway:EDDB 07 ILS-cat-I
... (many unknown airport and similar database discrepancies follow ... e.g. )
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1068:re-loaded ILS data for DNYO
... etc. etc. etc.
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1068:re-loaded ILS data for ZYCC
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1255:nav.dat load took:19282
navaid:5:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1258:SKIPPING POI load on Windows
navaid:3:..\..\..\flightgear\src\Navaids\navdb.cxx:276:opening file: C:/fgfs/data/Navaids/carrier_nav.dat.gz
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1068:re-loaded ILS data for EFMA
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:1272:awy.dat load took:13556
navaid:3:..\..\..\flightgear\src\Navaids\NavDataCache.cxx:170:cache rebuild took:78874msec... further down, there's this
flight:3:..\..\..\..\flightgear\src\FDM\JSBSim\JSBSim.cxx:489:Finished initializing JSBSim
flight:3:..\..\..\..\flightgear\src\FDM\JSBSim\JSBSim.cxx:492:FGControls::get_gear_down()= 1
io:4:..\..\..\flightgear\src\Main\fg_commands.cxx:1288:loadxml: Failed to open fileThe fgfs_0.log file also contains that last error, along with several unknown airport, etc. messages. And sure enough, the navdata_2_12.cache file has the same timestamp as the fgfs.log file. It's about 79K in size. I checked permissions on that file, and it's "read only"
I wonder how it's being re-written every launch, if it's read-only. Sorry about the formatting, I wanted to put it in a code window, but thought some lines needed to be emboldened, and you can't do that in a code window.
This is a family-friendly saloon. No talk stink.