Jump to: navigation, search

TerraGear GUI

937 bytes added, 19:07, 24 April 2011
Extended manual.
Specifying boundaries in the boxes on the left will download all [[World Custom Scenery Project|custom scenery]] shapefiles for that area. Alternatively you can download shapefiles from [ the mapserver by hand]. Unpack the downloaded file(s) to your <tt>{project's directory}/data/</tt>.
Elevation files are optional, but ofcourse required to generate scenery with elevation offsets (even flat countries like the Netherlands need elevation data, since a country isn't 100% at sealevel. Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-30</tt>.
=== HGT chop ===
This will convert the files you have downloaded earlier on and converts them into a form that TerraGear can read. Simply select the directory in which you unpacked the elevation downloads. Make sure you do set the correct resolution! For the USA this can be 1 arcsec, while the rest of the world is provided in 3 arcsec resolution.
=== Genapts ===
What is scenery without airport airports in a flight simulator? If your tile does not contain any airports, you can skip this part and continue with [[#ogr-decode|ogr-decode]].
First create the <tt>data/Airports/</tt> directory. Then locate You can do two things now:*'''Already-made airports:''' Locate FlightGears <tt>apt.dat.gz</tt> file, which is usually in <tt>[[$FG ROOT]]/Airports/</tt> in the just created directory. Unpack the file before you continue.*'''Home-made airports:''' if you created an airport in [[TaxiDraw]], just use the .dat file that you exported.
Use the button to browse to the (unpacked) .dat fileof your choice. If you only want to create the scenery for a specific airport you can enter the ICAO name into the relevant field. If you do not enter any information in any of the boxes, the tool will run through the entire apt.dat file, which can take a long timewhen using the default apt.dat from FlightGear.
=== OGR Decode ===
Now we need to decode the shapefiles into TerraGear format, which we do with OGR Decode. After clicking the "Retrieve shapefiles" button, the left list will be populated with the shapefiles from your project's data directory. On the right list you'll add the materials, per shapefile. Each single shapefile on the left, should have a material assigned on the right. By dragging materials up&down, you can finetune the material assignments.
You'''Warningll have to run OGR Decode twice: *_landmass MUST be mapped onto the # with all shapefiles assigned to material "Default", if you don't do this all scenery will be water.# with shapefile-specific materials. This is where you can try various materials in order to find the ones that best fit your area.'''
You can delete shapefiles and materials from the lists list by double-clicking on them. A single click on a material will allow you to edit it; to create custom materials that are not (yet) in materials.xml (do note that FlightGear will apply the default material to those landclasses, untill you create the material in materials.xml!).  Line width is only used on line-data (like roads, rivers and railroads). If you leave the line width fields empty, a default width of 10 meters is used.
=== FGFS Construct ===
The fgfs-construct tool brings all your gathered data together, throws it in a washing machine and spits it out the otherside in format ready for use with FlightGear. Click the "Update list" button to populate the field with all decodes decoded shapefiles. In the list you select all types that you'd like to include in your scenery. Note that you must select "Default" in order to generate anything other than water.
Then set the boundaries again (probably you want these to be the same as the ones you set on the start page), so the GUI can calculate the center of the to-be-created scenery area; and the radius, (all in degrees).
After clicking the "Generate scenery" button, it may take a long time for TerraGear to finish. Depending on the size of the area you are creating the scenery for and the level of detail in your shapefiles. Simple and small sceneries will take a couple of minutes, where larger, more detailed areas can take over an hour! So trying new things on small areas first will save you a lot of time.
The folders and files in your project's <tt>output/</tt> directory are ready to use as scenery. You can set the scenery path of FlightGear to this directory to check if the scenery is generated correctly. If you generated scenery, you must copy the files [ICAO].btg.gz file(s) from <tt>{project's directory}/work/AirportObj/</tt> to the corresponding directories in <tt>{project's directory}/output/Terrain</tt>.
== GUI development ==
The GUI is currently undergoing a complete rebuild and re-written in [ Qt]. This will allow us to build the GUI on multiple OSes (Mac OS X, UNIX, Windows).
The current source code can be retrieved [ from Gitorious].
Feel free to add feature requests and/or bug reportsto this page.
=== Requested features ===
* Maybe error reports possible? So you get a message when a certain file isn't found, or a certain path isn't set.
== External links ==
* [ Forum topic]
[[Category:Scenery enhancement]]

Navigation menu