186
edits
Hellosimon (talk | contribs) No edit summary |
m (→Philosophy: word choice) |
||
Line 8: | Line 8: | ||
The initial purpose of fgsd was to edit existing scenery because of the lack, at that time, of a decent free elevation model outside the USA. Releases up to 0.3.1 had capabilities to hand-edit part of the terrain. But it appeared to be cumbersome to edit triangles one at a time, and very frustrating as the work done on one tile was obsoleted every time a new global scenery was released. Moreover, editing the result of the TerraGear process proved to be non-trivial because of hidden gotchas on the topological quality of the tiles. | The initial purpose of fgsd was to edit existing scenery because of the lack, at that time, of a decent free elevation model outside the USA. Releases up to 0.3.1 had capabilities to hand-edit part of the terrain. But it appeared to be cumbersome to edit triangles one at a time, and very frustrating as the work done on one tile was obsoleted every time a new global scenery was released. Moreover, editing the result of the TerraGear process proved to be non-trivial because of hidden gotchas on the topological quality of the tiles. | ||
Finally, NASA and others released the SRTM digital elevation model that offers a more refined elevation dataset for most of the world, | Finally, NASA and others released the SRTM digital elevation model that offers a more refined elevation dataset for most of the world, lessening the need to edit elevations manually. | ||
From release 0.4.0 ( to be released ) ( and its pre-releases 0.3.9x - Win32 binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here] - Other systems, use CVS ), fgsd no longer offers the ability to edit already made scenery tiles. Instead, it | From release 0.4.0 ( to be released ) ( and its pre-releases 0.3.9x - Win32 binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here] - Other systems, use CVS ), fgsd no longer offers the ability to edit already made scenery tiles. Instead, it works interactively, using the same workflow as TerraGear. This workflow can be summarized as follow : | ||
* load raw elevations | * load raw elevations | ||
Line 22: | Line 22: | ||
additionally, 3D object models can be placed here and there to add verticality to this somewhat horizontal world. | additionally, 3D object models can be placed here and there to add verticality to this somewhat horizontal world. | ||
One side effect is that modified land cover contours can be exported to a format that TerraGear can use. A centralized database of contours is setup for that ( see http://www.custom-scenery.org ). This way collaborative changes to the global scenery can be | One side effect is that modified land cover contours can be exported to a format that TerraGear can use. A centralized database of contours is setup for that ( see http://www.custom-scenery.org ). This way collaborative changes to the global scenery can be consolidated and the next round of global scenery generation will include submitted individual changes. | ||
Of course, import from the landcover database is possible in fgsd. | Of course, import from the landcover database is possible in fgsd. | ||
edits