Howto:Make an airport: Difference between revisions

Jump to navigation Jump to search
m
Robot: Cosmetic changes
m (Out of date.)
m (Robot: Cosmetic changes)
Line 3: Line 3:
For changing [[scenery]] and airports you needed [[TerraGear]], which was always very hard to use and only for Linux. With the [[FlightGear Scenery Designer]] it is also possible to make custom airports or to change existing airports in [[FlightGear]].  
For changing [[scenery]] and airports you needed [[TerraGear]], which was always very hard to use and only for Linux. With the [[FlightGear Scenery Designer]] it is also possible to make custom airports or to change existing airports in [[FlightGear]].  


===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
Line 18: Line 18:
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. 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].
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].


=== Preparation for FGSD ===
=== Preparation for FGSD ===
#We create a file for the shapefiles like ./shapefiles.
# We create a file for the shapefiles like ./shapefiles.
#Now we download all the v0-layer and save them into the folder. Don't forget to unpack!
# Now we download all the v0-layer and save them into the folder. Don't forget to unpack!
#Now we create a folder for the heightmap like./heightmap and download the required data. Here we don't need to unpack!
# Now we create a folder for the heightmap like./heightmap and download the required data. Here we don't need to unpack!
# Now we open FGSD and prepare it for our work "Tools" -> "Chop HGT-Files": Set the root to the file of the "heightmaps.zip" and change it to heightmaps.arr.gz by replacing ".zip" with ".arr.gz"
# Now we open FGSD and prepare it for our work "Tools" -> "Chop HGT-Files": Set the root to the file of the "heightmaps.zip" and change it to heightmaps.arr.gz by replacing ".zip" with ".arr.gz"
# Now set the roots in "Tools"-> "Option": General: ./flightGear/scenery Our new tile will be find there later.
# Now set the roots in "Tools"-> "Option": General: ./flightGear/scenery Our new tile will be find there later.
# FlightGear: set the root to the data-file and the root for FlightGear Scenery to the file "shapefiles"
# FlightGear: set the root to the data-file and the root for FlightGear Scenery to the file "shapefiles"


Line 71: Line 71:
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?
* 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.
** You have to define the width: "Tools" - "landcover DB" -> "width" maybe. 10 for smaller ones and 20 for bigger ones.
*I only see the default-texture?
* I only see the default-texture?
**Uncheck v0-landmass
** Uncheck v0-landmass
*I see only red-white chequered surfaces in FlightGear?
* 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.
** Look if you have used in taxidraw the textures: others- they don't work in FlightGear.
*I can't start FlightGear?
* I can't start FlightGear?
**Look if you used special characters in apt.dat.gz - No use of special characters!
** Look if you used special characters in apt.dat.gz - No use of special characters!


== Thanks==
== Thanks ==
'''Thanks to:'''
'''Thanks to:'''
* Vadym who discovered this function in FGSD and showed it on the devel-list!
* Vadym who discovered this function in FGSD and showed it on the devel-list!

Navigation menu