20,741
edits
FlightGear Newsletter October 2016: Difference between revisions
FlightGear Newsletter October 2016 (view source)
Revision as of 18:42, 30 October 2016
, 30 October 2016→Local apt.dat versions support
| Line 37: | Line 37: | ||
=== Local apt.dat versions support === | === Local apt.dat versions support === | ||
apt.dat now supports local versions: | apt.dat now supports local versions: | ||
Local NavData directory support was added very recently, it wasn't included in 2016.3.1. But even when you do have a more recent version, you still need to use TerraGear to actually generate the visible terrain. NavData is only used for maps, startup locations etc., while the physical layout including runways and taxiways has to be generated in advance with TerraGear.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=297382#p297382 | |||
|title = <nowiki> Re: </nowiki> | |||
|author = <nowiki> Gijs </nowiki> | |||
|date = Oct 25th, 2016 | |||
|added = Oct 25th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
the NavData/apt/*.dat[.gz] files will allow you to see airports on the map, but to see actual 3D terrain different from what is already in TerraSync, running TerraGear and using its output(*) will be necessary. | |||
<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=297391#p297391 | |||
|title = <nowiki> Re: </nowiki> | |||
|author = <nowiki> rominet </nowiki> | |||
|date = Oct 25th, 2016 | |||
|added = Oct 25th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
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. | 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. | ||
| Line 90: | Line 111: | ||
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 | 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 | |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> | |||
As for the startup locations, it is definitely good for the future to include them in these files, but current FG only takes them from groundnet.xml files AFAIK, not apt.dat files (however, I've seen people post links about conversion tools from apt.dat format to groundnet.xml format, so probably the best way currently is to use apt.dat/WED as your primary data source even for startup locations/parkings and generate the groundnet.xml files from that). FFGo does read startup locations from $FG_ROOT/Airports/apt.dat.g, not yet from NavData/apt/*.dat[.gz] files inside scenery paths, but this is coming...<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=297391#p297391 | |||
|title = <nowiki> Re: </nowiki> | |title = <nowiki> Re: </nowiki> | ||
|author = <nowiki> rominet </nowiki> | |author = <nowiki> rominet </nowiki> | ||