![]() You can set the scenery path of FlightGear to this directory to check if the scenery is generated correctly. The folders and files in your project's output/ directory are ready to use as scenery. 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. Depending on the size of the area you are creating the scenery for and the level of detail in your shapefiles. In the list you select all types that you'd like to include in your scenery.Īfter clicking the "Generate scenery" button, it may take a long time for TerraGear to finish. Click the "Update list" button to populate the field with all decoded shapefiles. The tg-construct tool brings all your gathered data together, throws it in a washing machine and spits it out the otherside in a format ready for use with FlightGear. Note: with recent TerraGear builds, it is required to add the used material-names to the default_priorities.txt file. If you leave the line width fields empty, a default width of 10 meters is used. Line width is only used on line-data (like roads, rivers and railroads). 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!). You can delete shapefiles from the list by double-clicking on them. Each single shapefile must have a material. If a shapefile has no material, you'll need to assign it by hand. The GUI will try to assign fitting materials. After clicking the "Retrieve shapefiles" button, the list will be populated with the shapefiles from your project's data directory. Now we need to decode the shapefiles into TerraGear format, which we do with OGR Decode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |