20,741
edits
Navdata cache: Difference between revisions
Jump to navigation
Jump to search
m
http://forum.flightgear.org/viewtopic.php?f=25&t=27820&p=261905#p261849
m (screen shot of $FG_HOME with navdb files is apparently missing now ?) |
m (http://forum.flightgear.org/viewtopic.php?f=25&t=27820&p=261905#p261849) |
||
| Line 4: | Line 4: | ||
[[File:Fghome.png|400px|right|Screen shot showing structure of [[$FG_HOME]] ]] | [[File:Fghome.png|400px|right|Screen shot showing structure of [[$FG_HOME]] ]] | ||
--> | --> | ||
{{Caution|This feature is crucial to the FlightGear startup sequence, but is unfortunately infamous for rendering FlightGear non-startable under certain situations. Particularly, after experiencing a FlightGear crash or when running multiple fgfs instance at the same time-it is assumed that this is due to lack of synchronization and missing atexit handlers, so that the SQLite database gets corrupted under these circumstances. }} | |||
The '''navdata cache''', '''navdb''', (sometimes also '''navcache''') is automatically built by FlightGear during startup by parsing/processing the gzipped <code>nav.dat</code> file and building a spatial SQLite-based database in [[$FG_HOME]] so that more efficient queries can be run at run-time, but, in particular when starting up/[[Reset & re-init|re-initializing FlightGear]]. | The '''navdata cache''', '''navdb''', (sometimes also '''navcache''') is automatically built by FlightGear during startup by parsing/processing the gzipped <code>nav.dat</code> file and building a spatial SQLite-based database in [[$FG_HOME]] so that more efficient queries can be run at run-time, but, in particular when starting up/[[Reset & re-init|re-initializing FlightGear]]. | ||