20,741
edits
FlightGear Newsletter October 2016: Difference between revisions
FlightGear Newsletter October 2016 (view source)
Revision as of 15:53, 18 October 2016
, 18 October 2016→Development news
| Line 22: | Line 22: | ||
== Development news == | == Development news == | ||
{{Next default airport|airport=LSZH (Zürich)}} | {{Next default airport|airport=LSZH (Zürich)}} | ||
===Local apt.dat versions support === | |||
apt.dat now supports local versions: | |||
It is now possible to have one or more local apt.dat files each containing data for one or more airfields. The airfields in the local apt.dat files take precedence over the contents of the apt.dat.g file that is distributed as part of fgdata. - in much the same way as local custom scenery takes preference over terragear scenery. | |||
If you are using WED, the apt.dat output by that program is suitable. | |||
To use it add a folder NavData/apt in your fg-scenery and place your private files in that folder. <ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=296919#p296919 | |||
|title = <nowiki> apt.dat - local version(s) </nowiki> | |||
|author = <nowiki> Alant </nowiki> | |||
|date = Oct 18th, 2016 | |||
|added = Oct 18th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Of course, your apt.dat changes should continue to be submitted to the Xplane gateway so that they will eventually be included in the main distribution.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=296919#p296919 | |||
|title = <nowiki> apt.dat - local version(s) </nowiki> | |||
|author = <nowiki> Alant </nowiki> | |||
|date = Oct 18th, 2016 | |||
|added = Oct 18th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
No need for any command-line option. As I wrote in <https://sourceforge.net/p/flightgear/mailman/message/35424973/>;, you have to put your apt.dat files (any name ending with .dat or .dat.g is OK) in a structure like the following: | |||
<pre> | |||
Scenery path | |||
├── NavData | |||
│ ├── apt | |||
| | ├── vrmg.dat | |||
| | ├── vrmh.dat | |||
| | ├── vrmk.dat | |||
├── vrmm.dat | |||
├── vrmo.dat.gz | |||
└── vrmt.dat | |||
</pre> | |||
where “Scenery path” can be any of you scenery paths (e.g., any component of --fg-scenery/$FG_SCENERY; the path given to --terrasync-dir is also one). The files read are all NavData/apt/*.dat[.gz] files inside each scenery path, followed by the default $FG_ROOT/Airports/apt.dat.gz (last in precedence order, thus allowing your custom sceneries to override airports already present in $FG_ROOT/Airports/apt.dat.gz). In the typical case, just put your apt.dat files(*) in the NavData/apt subdirectory of your custom scenery and they will be picked up automatically. In each of these files, you may include as many airport definitions as you want. (*) Actually, any name ending with .dat or .dat.gz---but the syntax inside, of course, must be valid "apt.dat syntax". And if the file name ends in .gz, of course the contents must be gzipped-compressed. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35432391/ | |||
|title = <nowiki> Re: [Flightgear-devel] apt.dat - add local version ? </nowiki> | |||
|author = <nowiki> Florent Rougon </nowiki> | |||
|date = Oct 17th, 2016 | |||
|added = Oct 17th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
{{Appendix}} | |||
== In the hangar == | == In the hangar == | ||