Howto:Add procedures to the route manager: Difference between revisions
Jump to navigation
Jump to search
| Line 36: | Line 36: | ||
|date = Jun 28th, 2017 | |date = Jun 28th, 2017 | ||
|added = Jun 28th, 2017 | |added = Jun 28th, 2017 | ||
|script_version = 0.40 | |||
}}</ref> | |||
for example if you want to import a sid/star file for VTSP, you name the file VTSP.procedures.xml and put it in <scenery directory>/V/T/S/ . In there you will likely find VTSP.twr.xml but not an existing *. procedures.xml file. | |||
Substitute VTSP for your airport code.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=313409#p313409 | |||
|title = <nowiki> Re: routeplanner stir sid </nowiki> | |||
|author = <nowiki> Parnikkapore </nowiki> | |||
|date = Jun 29th, 2017 | |||
|added = Jun 29th, 2017 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
Revision as of 15:30, 6 August 2017
| This article is a stub. You can help the wiki by expanding it. |
Background
Make some yourself. Charts are easy to find and a quick search will find you the syntax. This is what FlightGear is all about; doing it yourself and sharing it to others. A quick search would also find existing packages...[1]
Objective
a free way to get mor e SID STAR for the routeplanner in fg[2]
Instructions
Something like
<scenery directory>/Airports/I/C/A/ICAO.procedures.xml
Where ICAO is your airport code.[3]
for example if you want to import a sid/star file for VTSP, you name the file VTSP.procedures.xml and put it in <scenery directory>/V/T/S/ . In there you will likely find VTSP.twr.xml but not an existing *. procedures.xml file.
Substitute VTSP for your airport code.[4]
References
References
|