Howto:Make an airport: Difference between revisions

Jump to navigation Jump to search

Howto:Make an airport (view source)

Revision as of 12:26, 23 August 2008

31 bytes added ,  23 August 2008
m
small wikicleanup
m (cleanup, needs some more altough)
m (small wikicleanup)
Line 2: Line 2:


===What you need:===
===What you need:===
* FlightGear Scenery Designer - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/fgsd-win32-20060423.zip
* [[FlightGear Scenery Designer]] - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/fgsd-win32-20060423.zip
* [[TaxiDraw]] - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/taxidraw-win32-20061010.zip
* [[TaxiDraw]] - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/taxidraw-win32-20061010.zip
* Google Maps or Google Earth for making the runway layout
* Google Maps or Google Earth for making the runway layout
Line 14: Line 14:


=== Let's start with making the runway layout- taxidraw ===
=== Let's start with making the runway layout- taxidraw ===
At first we have to define the runways and taxiways. So we use TaxiDraw. A tutorial about using TaxiDraw could be find here: http://taxidraw.sourceforge.net/taxidraw/tutorial.html
At first we have to define the runways and taxiways. So we use [[TaxiDraw]]. A tutorial about using TaxiDraw could be find here: http://taxidraw.sourceforge.net/taxidraw/tutorial.html


So if we have done the airport in TaxiDraw, we save it as "airport.dat". That's the X-plane-fileformat, which is used by FlightGear too.
So if we have done the airport in TaxiDraw, we save it as "airport.dat". That's the X-plane-fileformat, which is used by FlightGear too. Now we unpack apt.dat.gz in the data folder of FlightGear and paste and copy our new "airport.dat" into it. Don't use any special character like "/" - it could causes a 2h long troubleshooting on your pc system ;-) Now we pack it again to  apt.dat.gz. For user of Linux it is easy, windows user can use [http://www-7-zip.org 7-zip].
 
Now we unpack apt.dat.gz in the data folder of FlightGear and paste and copy our new "airport.dat" into it.
 
Don't use any special character like "/" - it could causes a 2h long troubleshooting on your pc system ;-)  
 
Now we pack it again to  apt.dat.gz. For user of Linux it is easy, windows user can use [http://www-7-zip.org 7-zip].


=== Preparation for FGSD ===
=== Preparation for FGSD ===
Line 37: Line 31:
If we don't know the name, we can use the [[UFO from the 'White Project' of the UNESCO|UFO]] and place any object at the spot we want to have the new airport. We have to look now in the generated .xml-file and we see something like 3531408.stg. So we open in our case here the tile with the name 3531408.arr.gz.  
If we don't know the name, we can use the [[UFO from the 'White Project' of the UNESCO|UFO]] and place any object at the spot we want to have the new airport. We have to look now in the generated .xml-file and we see something like 3531408.stg. So we open in our case here the tile with the name 3531408.arr.gz.  


You should see now your tile. If not, play a little bit with the buttons in the scenery toolbar.
You should see now your tile. If not, play a little bit with the buttons in the scenery toolbar. "Option" and "Landcover-DB" and check the required layers. You don't need the layer "v0landmass"
 
"Option" and "Landcover-DB" and check the required layers. You don't need the layer "v0landmass"
 
Sometimes you could only see the standart-layers, but we want to have our downloaded layers. So unckeck all, exit the program and launch it again.


We have to order the layer and define which texture matches to the layer. ( so as an example the v0railroads really have the right texture). We also define the weidth.
Sometimes you could only see the standart-layers, but we want to have our downloaded layers. So unckeck all, exit the program and launch it again. We have to order the layer and define which texture matches to the layer. ( so as an example the v0railroads really have the right texture). We also define the weidth.


The larger textures are always above the smaller one like that:  
The larger textures are always above the smaller one like that:  
Line 56: Line 46:


Play a litte bit with it, so you can see how it works.
Play a litte bit with it, so you can see how it works.
 
Now click "Simplify Terrain" in "Scenery" the heightmodel is now beeing simplified so we can use it in FlightGear. Click "embedded Curves" - the shapefiles will now being embedded and we can see our landclasses. Our airport is still missing - select "Tools" and "Select Airport" and choose our airport. You can see it now on the tile.  
Now click "Simplify Terrain" in "Scenery" the heightmodel is now beeing simplified so we can use it in FlightGear.
 
Click "embedded Curves" - the shapefiles will now being embedded and we can see our landclasses.
 
Our airport is still missing - select "Tools" and "Select Airport" and choose our airport. You can see it now on the tile.


"Scenery"->"embeddes airports"
"Scenery"->"embeddes airports"
Line 69: Line 54:
Now we export it now: "File"->"Export"
Now we export it now: "File"->"Export"


We will find our airport in " ./FlightGear/Scenery" and copy this into ./data/scenery
We will find our airport in <tt>./FlightGear/Scenery</tt> and copy this into <tt>./data/scenery</tt>. If we have made a airport which was not yet existing in FlightGear, so put in the IACA-Code in <tt>./application data/flightgear.org/fgrun</tt> into the list.Now we launch FlightGear and start from our new made airport!
 
If we have made a airport which was not yet existing in FlightGear, so put in the IACA-Code in "./application data/flightgear.org/fgrun" into the list.
 
Now we launch FlightGear and start from our new made airport!


=== next time ===
=== next time ===
Line 88: Line 69:
Don't forget to send your new "airport.dat" to Robin Peel, so we all will benefit from!
Don't forget to send your new "airport.dat" to Robin Peel, so we all will benefit from!


===sources of errors and FAQ===
===Sources of errors and FAQ===
 
*The new made airport has no lights, towers, beacons and windsocks?
- The new made airport has no lights, towers, beacons and windsocks?
**That's right - in the moment it is only possible with terragear. But you can place in FGSD the towers, beacons and windsocks with the object editor.
That's right - in the moment it is only possible with terragear. But you can place in FGSD the towers, beacons and windsocks with the object editor.
*I don't see any roads and rivers?
 
**You have to define the width:  "Tools" - "landcover DB" -> "width"  maybe. 10 for smaller ones and 20 for bigger ones.
- I don't see any roads and rivers?
*I only see the default-texture?
You have to define the width:  "Tools" - "landcover DB" -> "width"  maybe. 10 for smaller ones and 20 for bigger ones.
**Uncheck v0-landmass
 
*I see only red-white chequered surfaces in FlightGear?
- I only see the default-texture?
**Look if you have used in taxidraw the textures: others- they don't work in FlightGear.
uncheck v0-landmass
*I can't start FlightGear?
 
**Look if you used special characters in apt.dat.gz - No use of special characters!
-I see only red-white chequered surfaces in FlightGear?
Look if you have used in taxidraw the textures: others- they don't work in FlightGear.
 
-I can't start FlightGear?
Look if you used special characters in apt.dat.gz - No use of special characters!


== Thanks==
== Thanks==
Thanks to Vadym who discovered this function in FGSD and showed it on the devel-list!
'''Thanks to:'''
Thanks to Frederic Bouvier, who wrote FGSD!
* Vadym who discovered this function in FGSD and showed it on the devel-list!
Thanks to Martin Spott and Ralf Gerlich for the Landcover DB!
* Frederic Bouvier, who wrote FGSD!
* Martin Spott and Ralf Gerlich for the Landcover DB!


[[Category:Howto]]
[[Category:Howto|Make an airport]]
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/6360"

Navigation menu