Howto:Make a helipad: Difference between revisions

Jump to navigation Jump to search
m
Robot: Cosmetic changes
m (+ little discription about adding lights)
m (Robot: Cosmetic changes)
Line 1: Line 1:
[[Image:EH0001.jpg|thumb|270px|An [[EC135]] at the helipad of a [[VU University Medical Center|large hospital]] in Amsterdam, the Netherlands.]]
[[File:EH0001.jpg|thumb|270px|An [[EC135]] at the helipad of a [[VU University Medical Center|large hospital]] in Amsterdam, the Netherlands.]]
[[Image:RS_Platform.png|thumb|270px]]The current [[FlightGear]] world has little '''helipads''' to fly from/to with your [[helicopter]]. This article is meant to provide help in the progress of making a helipad.
[[File:RS_Platform.png|thumb|270px]]The current [[FlightGear]] world has little '''helipads''' to fly from/to with your [[helicopter]]. This article is meant to provide help in the progress of making a helipad.


==Creating the model==
== Creating the model ==
Every face in FlightGear is solid and can be landed on by default, so helipads can be modeled just like any other object.
Every face in FlightGear is solid and can be landed on by default, so helipads can be modeled just like any other object.


Placing lights is very easy. FlightGear contains two basic lights in the <tt>[[$FG_ROOT]]/Models/Effects/Lights/</tt> directory: the red one is usually used to mark obstructions, while the green ones mark the helipad. You can link to those models from your buildings .xml file like this:
Placing lights is very easy. FlightGear contains two basic lights in the <tt>[[$FG ROOT]]/Models/Effects/Lights/</tt> directory: the red one is usually used to mark obstructions, while the green ones mark the helipad. You can link to those models from your buildings .xml file like this:


  <model>
  <model>
Line 17: Line 17:
  </model>
  </model>


==Editing apt.dat==
== Editing apt.dat ==
Right now your helipad can be landed on, but we do like to takeoff from it aswell, don't we? Therefore, we need to extend the apt.dat file, which stores all [[:Category:Airports|airport]] information. You can find it likely in <tt>[[$FG_ROOT]]/Airports</tt>.(Mac route = FlightGear/data/Airports). Before we can edit the file we need to unzip it first. Be sure to always make a backup before you change anything.  
Right now your helipad can be landed on, but we do like to takeoff from it aswell, don't we? Therefore, we need to extend the apt.dat file, which stores all [[:Category:Airports|airport]] information. You can find it likely in <tt>[[$FG ROOT]]/Airports</tt>.(Mac route = FlightGear/data/Airports). Before we can edit the file we need to unzip it first. Be sure to always make a backup before you change anything.  


Once it's unpacked, open it with any texteditor you like (TextEdit is prefered for MAC users) and scroll down to the bottom of the file, where the heliports are listed (lines with [H]) in alphabetical order. Now we need to add one or two line(s) to the file, in order to add our helipad as a startup location.
Once it's unpacked, open it with any texteditor you like (TextEdit is prefered for MAC users) and scroll down to the bottom of the file, where the heliports are listed (lines with [H]) in alphabetical order. Now we need to add one or two line(s) to the file, in order to add our helipad as a startup location.
Line 24: Line 24:
As an example, the lines below are used for the helipad on the roof of a large hospital in the Netherlands.
As an example, the lines below are used for the helipad on the roof of a large hospital in the Netherlands.


<tt>17 126 0 0 EH0001 [H] VU medisch centrum<br>
<tt>17 126 0 0 EH0001 [H] VU medisch centrum<br />
10 52.33434 4.85911 H1x 360.00 40 0000.0000 0000.0000 36 111111 2 0 2 0.25 0 0300.0300</tt>
10 52.33434 4.85911 H1x 360.00 40 0000.0000 0000.0000 36 111111 2 0 2 0.25 0 0300.0300</tt>


Line 85: Line 85:
Save the file after you've made your changes and zip it again, overwriting/replacing the old apt.dat.gz file.
Save the file after you've made your changes and zip it again, overwriting/replacing the old apt.dat.gz file.


==Testing==
== Testing ==
===MAC===
=== MAC ===
At the time of writing this wiki, the Mac's GUI launcher cannot synchronize the apt.dat update at run time, and is also not able to access the Helipad part of the apt.dat file, and therefore the Heliports are not listed in the ‘position’ page of the Launcher, where you usually choose your starting points.
At the time of writing this wiki, the Mac's GUI launcher cannot synchronize the apt.dat update at run time, and is also not able to access the Helipad part of the apt.dat file, and therefore the Heliports are not listed in the ‘position’ page of the Launcher, where you usually choose your starting points.


Line 93: Line 93:
# Now just start your flight as usually.
# Now just start your flight as usually.


===Windows===
=== Windows ===
Refresh your FlightGears airport cache, with the button on the Airport page of the Launcher. Now your heliport should come up in the list. Just select it as every other airport and run FlightGear to see if your hard work paid of.
Refresh your FlightGears airport cache, with the button on the Airport page of the Launcher. Now your heliport should come up in the list. Just select it as every other airport and run FlightGear to see if your hard work paid of.


==Distributing==
== Distributing ==
If you want your helipad to be included with a further FlightGear release, make sure to send your change/addition to apt.dat to http://data.x-plane.com/ and upload your model to the [[FlightGear Scenery Database]].
If you want your helipad to be included with a further FlightGear release, make sure to send your change/addition to apt.dat to http://data.x-plane.com/ and upload your model to the [[FlightGear Scenery Database]].


Navigation menu