20,741
edits
m (http://forum.flightgear.org/viewtopic.php?f=25&t=27820&p=261905#p261849) |
mNo edit summary |
||
Line 5: | Line 5: | ||
--> | --> | ||
{{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. }} | {{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. | ||
Unfortunately, this bug is hard to reproduce. So if you are encountering this bug, please make sure to file a proper bug report, including instructions for reproducing the bug, so that this can be hopefully fixed. }} | |||
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]]. |