Project3000: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(scenery project3000)
 
Line 5: Line 5:


== the name ? ==
== the name ? ==
When the project started in 10/2015 the gateway website stated roughly 3000 Scenery Packs with 3D Objects. Put some airports have more than one pack to choose from, so at the moment we can populate 2260 airports.
When the project started in 10/2015 the gateway website stated roughly 3000 Scenery Packs with 3D Objects. Some airports have more than one pack to choose from, so at the moment we can populate 2260 airports.


== requirements ==
== requirements ==

Revision as of 11:41, 28 October 2015

what is it?

Project3000 is a project to automatically improve scenery at airports using position data (.dsf) from http://gateway.x-plane.com/ and shared models from Flightgear.

the name ?

When the project started in 10/2015 the gateway website stated roughly 3000 Scenery Packs with 3D Objects. Some airports have more than one pack to choose from, so at the moment we can populate 2260 airports.

requirements

you need Python 2.x. Python3 will not work. some knowledge of the commad line.

the tools

  • gateway_pull.py
  • dsf2stg.py
  • populate.sh

how to use

git clone https://github.com/mherweg/d-laser-fgtools.git

or "Download zip" on https://github.com/mherweg/d-laser-fgtools

make sure that you have downloaded terrain of the airports that you want to make, otherwise elevation probing will fail and all objects will be at sea level.

Test if fgelev is working on your computer: (be patient, fgelev is slow )

export FG_ROOT= YOUR FG_ROOT PATH
export FG_SCENERY= YOUR TERRASYNC PATH
time echo "foo 8.56256161 50.04758962 " | fgelev

a good result example(107m above MSL)

foo: 107.910

a bad result example (approx 0m MSL)

foo: -0.34

write your paths into parameters.py:

PATH_TO_SCENERY = "/home/YOURUSERNAME/.fgfs/TerraSync"
PATH_TO_OUTPUT = "/home/YOURUSERNAME/scenery/test"

you might also have to change the fg_root in fgelev.py:

fg_root = "/usr/share/games/flightgear"

unpack dsf_txt_collection2000.tgz

populate 1 airport:

./dsf2stg.py -i dsf_txt_collection2000/EDDF.txt

populate all airports(takes a few hours and only makes sense if you have terrain for most of them):

./populate.sh > populate.log 

getting a new airport:

cd dsf_txt_collection2000
./gateway_pull.py -i ICAO

testing the result:

fgfs --aircraft=ufo --airport=EDDF --fg-scenery=/home/YOURUSERNAME/scenery/test

modify and contribute

Let's say you want different light-posts, no jetways, no static aircraft or whatever you like/dislike. You can control what will be generated by changing lines in library.txt. Put a # at the beginning of a line to disable a model. change the second path in a line to choose a different model. the number at the end of some lines are offsets and heading. the first 2 numbers are not used atm, the third is a elevation offset in meters tha last value is the heading offset in degrees. Let's say a model is pointing north in WED and your replacement is pointing up(+y) in Blender's top view then the required heading offset is 90.

At the end of library.txt you find a list of models where we don't have a Flightgear replacement yet, sorted by popularity. Pick stuff that you would like to have (shed, factory, ...) open WED to see how it looks and find or make a model that fits.

If you don't want to run the tools yourself, you can still "disable" or change models by renaming/moving/replacing the .ac and .xml files in you Models folder.

download

the tools are here: https://github.com/mherweg/d-laser-fgtools

and the first version of a world wide custom scenery pack is here: http://media.lug-marl.de/flightgear/project3000.tgz (21MB)

questions ?

please post on the forum: https://forum.flightgear.org/viewtopic.php?f=5&t=27688 or use the discussion tab of this page