518
edits
m (→Tools) |
m (→Tools) |
||
| Line 63: | Line 63: | ||
Add your email address to be informed of the progress of the update. Import should happen soon (let's say between 24 and 72 hours, but it depends on the poor scenery maintainer(s) workload!). | Add your email address to be informed of the progress of the update. Import should happen soon (let's say between 24 and 72 hours, but it depends on the poor scenery maintainer(s) workload!). | ||
The address ? http://scenemodels.flightgear.org/submission/ then choose mass import, or via the menu (Contribute => Mass | The address ? http://scenemodels.flightgear.org/submission/ then choose mass import, or via the menu (Contribute => Mass shared object position insertion). | ||
Please note: | Please note: | ||
. You must only import new objects, not the whole STG file you're working on! | . You must only import new objects, not the whole STG file you're working on! | ||
. Don't add models not present in the FG scenemodels database, nor (yet) OBJECT_SIGN nor OBJECT_STATIC. | . Don't add models not present in the FG scenemodels database, nor (yet) OBJECT_SIGN nor OBJECT_STATIC. | ||
. Don't add forest or other items linked to the landcover. Those items have to be generated based on the landcover, not on objects! The only trees accepted will be those located on | . Don't add forest or other items linked to the landcover. Those items have to be generated based on the landcover, not on objects! The only trees accepted will be those located on airport boundaries, for example. | ||
. The data you're asking for import should be based for elevation on the terrain shipped with FlightGear/Terrasync, and not on a terrain you could have downloaded or compiled yourself. Else, your objects | . The data you're asking for import should be based for elevation on the terrain shipped with FlightGear/Terrasync, and not on a terrain you could have downloaded or compiled yourself. Else, your objects could appear floating or sunk in the terrain... | ||
. Finally, the import is limited to 100 lines per submission (let's think about the poor | . Finally, the import is limited to 100 lines per submission (let's think about the poor scenery maintainer(s)...) | ||
. The import is quite sensitive about the data in entry, which goes through quite a lot of checkings, including humans, before insertion. | . The import is quite sensitive about the data in entry, which goes through quite a lot of checkings, including humans, before insertion. | ||
edits