Hi,
Here are a few notices you should read before uploading - and better - before creating any 3D-model for FG. This is VERY important to save a lot of extra-human workload at the other end (the nice guy validating your submission in FG's scenery database). Those recommendations are also available at http://scenemodels.flightgear.org/contribute.php#tips . Not following those recommandations could lead your models to be redesigned afterwards. Please follow them thoroughly.
For shared models positions.
If you want to add, delete, update, mass import shared models, please please use the forms at http://scenemodels.flightgear.org/submission/.
Use -9999 as elevation if you want the database to automagically compute it - less hassle for you
For 3D-models (there should hopefully be a form for this soon).
1. Release early, release often! The earlier you contribute, the easiest it is to tell you if your contributions are done as expected - or not.
2. Mandantory submission items
- Always choose reasonable (meaningful, descriptive) filenames for your models. At urban areas having a geometry 'tower.ac' or a texture just named 'red.png' or 'concrete.png' might prove not to be unique
- As a rule of thumb, try to let even a detailed, single model not exceed 1/2 MByte in total size, otherwise the simulation will face hard times when approaching densely packed areas. - A typical, single office building usually can be done at (far!) less than 100 kByte;
- Avoid spaces in file- and/or directory names;
- ALL PNG textures must have a power of 2 between their two dimensions (eg 128*256...).
Model placement:
- Position (if appropriate; either lon/lat, or Ordnance Survey grid - other grids can be added on request);
- Heading (if appropriate);
- Ground elevation (if known to the author) - in any !! case, report if the model has to be sunken into the ground in order to display properly !!;
-> .... or just simply submit the respective .stg-line with your model.
- Full name of author (if not already known);
- EMail of author (if not already known, will not be published, just as a reference);
- A notice which tells us that your submission is covered by the GPL (if not already known) - the nature of the FlightGear project does not allow us to accept submissions that don't comply with the GPL;
- Always tell us how to name the model (like 'Tour Eiffel - Paris - France').
- A 320x240 thumbnail containing an advantageous view on the model/object as (JPEG) image - this is preferred for a nice representation of your artwork;
- Country in which the model is located (if known to the author);
- Additional short comment on the author;
All this is to be submitted through our webforms at http://scenemodels.flightgear.org . Read also here: http://www.flightgear.org/forums/viewto ... =5&t=14671 for more information.
NOTICE: To save you and us from avoidable and unnecessary extra work:
- Never group different, detached buildings into a single geometry file.
- Never put surface materials (tarmac, grass, roads, parkings, ...) into Scenery Model geometries.
-> The reason is simple: Depending on the angle of view, the operating system, the graphics card and driver, the underlying terrain slope, various people might be seeing rendering artifacts. Therefore: Please don't !
For groupings of individual models choose a distinct, corresponding position for each of them, never mount multiple models into a single position.
Textures should be in PNG format - older models which used rgb textures have been updated.
As a general rule, do not try to (mis)use 3D models as a substitute for unfinished airfield layout or land cover. Do not place your models at incorrect positions just because the current land cover shapes do not match.
Feel invited to send us an early version of your model even if it still has unfinished details. It's always possible to update the respective metadata entry with a refined model - especially when the placement of the model doesn't change any more.
-> The better your submission complies with these recommendations, the quicker we'll have it imported into the repository.