This is a rather old thread but just for the record I wanted to share a possibility to enhance the catalogue of available fixes without touching the originally delivered fix.dat.gz of FlightGear. It stems from an idea Alessandro Menti used with his fabulous scenery of
LIPX .
FlightGear does willingly accept additional fix data if only it is presented in a defined folder structure.
We need to establish a new scenery folder (i.e. "Fixes") containing a folder “NavData” and therein a folder “fix”. I was missing some waypoints for the northerly approach to Rome (LIRF). So my first .dat file inside the fix folder was ~/FlightGear/Fixes/NavData/fix/lirf.dat containing
- Code: Select all
I
1101 Version - Copyright © 2020 D-UKA GPLv2+
42.014920 012.191160 OXERU
42.075050 012.165540 IRBES
42.063430 012.122540 MAVEN
42.094450 012.082680 SUVOK
42.153610 012.202280 EXAMA
99
The new scenery folder “Fixes” needs to be added into the sequence of your established scenery structure (most advanced scenery first):
- Code: Select all
--fg-scenery=/home/D-UKA/FlightGear/Scenery-extra/LIPX
--fg-scenery=/home/D-UKA/FlightGear/Scenery-extra/PROJECT3000
--fg-scenery=/home/D-UKA/FlightGear/Fixes
--fg-scenery=/home/D-UKA/FlightGear/Scenery
--fg-scenery=/home/D-UKA/FlightGear/TerraSync
You are not limited to ICAO-codes in filenames nor are you to only one file. italy.dat instead of lirf.dat will do as will canaries.dat or norway.dat living beside it.
After establishing the new scenery folder FlightGear needs to be restarted. If you don’t see it rebuilding the navdata cache something is amiss. Try to delete the navdata.cache and retry.
You want to make sure your additional fixes are incorporated, so add a non-existent test fix to your list like 45.123456 15.123456 DUKAL and try to use it in your flight plan.
Best regards, D-UKA