64
edits
Understanding FlightGear Scenery: Difference between revisions
Understanding FlightGear Scenery (view source)
Revision as of 08:05, 7 January 2011
, 7 January 2011no edit summary
(first edit) |
No edit summary |
||
| Line 1: | Line 1: | ||
If you want to develop scenery for FlightGear, great! FlightGear needs as much help as possible with modeling the world. This article is meant to explain how FlightGear manages scenery and what quirks or nuances you need to know in order to best contribute. | If you want to develop scenery for FlightGear, great! FlightGear needs as much help as possible with modeling the world. This article is designed for someone who is interesting in creating FlightGear scenery for the first time and is meant to explain how FlightGear manages scenery and what quirks or nuances you need to know in order to best contribute. | ||
==How Scenery is Generated== | ==How Scenery is Generated== | ||
| Line 9: | Line 9: | ||
==How Scenery is Stored== | ==How Scenery is Stored== | ||
FlightGear manages scenery through a folder hierarchy representing square degrees for both Objects and Terrain. | FlightGear manages scenery through a folder hierarchy representing square degrees for both Objects and Terrain. The purpose of separating scenery tiles by degree is to allow easy internet distribution and to provide boundaries for the generation of terrain, so polygons do not just go on for miles. | ||
This means you need to know where your scenery project is in longitude and latitude. For instance, San Francisco's airport can be found under the folder w123n37. | |||
==The Basic Format== | ==The Basic Format== | ||
| Line 17: | Line 19: | ||
This folder contains various .xml files for the airports you have downloaded. You do not need to edit these! | This folder contains various .xml files for the airports you have downloaded. You do not need to edit these! | ||
If you are interested in contributing airport data, you will want to use [[TaxiDraw]]. Unfortunately TaxiDraw is not very robust at the moment, but it works. As of January 2010, FlightGear uses an older version of the X-Plane airport data. The kind people over at [http://scenemodels.flightgear.org the Scenery Model Database] accept updated airports in the 8.10 format. | If you are interested in contributing airport data, you will want to use [[TaxiDraw]]. Unfortunately TaxiDraw is not very robust at the moment, but it works. As of January 2010, FlightGear uses an older version of the X-Plane airport data. The kind people over at [http://scenemodels.flightgear.org the Scenery Model Database] accept updated airports in the X-Plane 8.10 format. | ||
Because of the FlightGear feature which allows airports to undulate, or change elevation, all airports must be regenerated using [[TerraGear]] once [[TaxiDraw]] has been used. | Because of the FlightGear feature which allows airports to undulate, or change elevation, all airports must be regenerated using [[TerraGear]] once [[TaxiDraw]] has been used. | ||
===Objects=== | ===Objects=== | ||
Objects are possibly the easiest sceneries to create for FlightGear. All you need is to create an .ac model and place it using the ufo or manually using co-ordinates. You can also create an .xml file to create animations. | |||
Objects are stored in a global database, the [http://scenemodels.flightgear.org/ FlightGear Scenery Model Database]. Once you have modeled your building, please make sure to send it into the database, as this is how your work gets distributed! Your work will be available to [[TerraSync]] users shortly after it is added. | |||
Please note there is a difference between SHARED and STATIC objects. SHARED objects are objects which are included within the whole scenery, regardless of where you are. STATIC objects are specific objects, which appear a limited number of times (usually once) in the scenery. For instance, a house created to be auto-generated scenery would be a SHARED model, while the model of the tallest skyscraper in the country would be a STATIC model. SHARED models are typically to be avoided unless you know what you are doing, as they are loaded into memory when FlightGear starts up. | |||
* [Howto:_Place_3D_objects_with_the_UFO] | |||
* [Howto:_Add_shared_models_manually] | |||
===Terrain=== | ===Terrain=== | ||