111
edits
Using the Custom Scenery TerraGear Toolset: Difference between revisions
Jump to navigation
Jump to search
Using the Custom Scenery TerraGear Toolset (view source)
Revision as of 18:52, 15 June 2009
, 15 June 2009→Airports: Add info that can save a lot of hassle
No edit summary |
Papillon81 (talk | contribs) (→Airports: Add info that can save a lot of hassle) |
||
| Line 81: | Line 81: | ||
If it is simply run with a specified apt.dat and work directory, it will generate airport layouts for every airport in the file, which can take a long time. | If it is simply run with a specified apt.dat and work directory, it will generate airport layouts for every airport in the file, which can take a long time. | ||
If you are just creating a single airport and you know the ICAO ID (e.g. KSFO, EGPH, EG32), use is as follows from your root scenery directory (i.e. the directory above your data, work and output directories). | If you are just creating a single airport and you know the ICAO ID (e.g. KSFO, EGPH, EG32), use is as follows from your root scenery directory (i.e. the directory above your data, work and output directories). If you use an apt.dat file with one single airport in it you should omit the "--airport" parameter. | ||
genapts --input=data/airports/apt.dat --work=./work --airport=<AIRPORT_ID> | genapts --input=data/airports/apt.dat --work=./work --airport=<AIRPORT_ID> | ||