20,741
edits
FlightGear Newsletter October 2016: Difference between revisions
FlightGear Newsletter October 2016 (view source)
Revision as of 18:40, 30 October 2016
, 30 October 2016→Local apt.dat versions support
| Line 79: | Line 79: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
The rule is that your file(s) must end in .dat (or .dat.g if gzip-compressed), there is no requirement to use the airport code in the file name, although of course it is clearer this way if you have one apt.dat file per airport. But it is also possible to have many airports in one big apt.dat or apt.dat.gz file like the $FG_ROOT/Airports/apt.dat.gz that comes with FG.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=297374#p297374 | |||
|title = <nowiki> Re: </nowiki> | |||
|author = <nowiki> rominet </nowiki> | |||
|date = Oct 25th, 2016 | |||
|added = Oct 25th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
you shouldn't add things yourself to the TerraSync folder or even, in this case, to K:\Program Files (x86)\FlightGear 2016.3.1\data created by the FG installation. You should just create a '''new''' folder for your custom scenery (k:\myflightgear\myscenery was an example, choose whatever you want) and declare it as a scenery path to FG. The Airports, Objects and Terrain subfolders are standard folders inside custom sceneries, so in the end if your custom scenery is non-empty, you'll have at least Objects or Terrain.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=297374#p297374 | |||
|title = <nowiki> Re: </nowiki> | |||
|author = <nowiki> rominet </nowiki> | |||
|date = Oct 25th, 2016 | |||
|added = Oct 25th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
{{Appendix}} | {{Appendix}} | ||