PREFIX = "w097n37"
PATH_TO_SCENERY = "/home/wayne/FGFS/Scenery/kansas/output"
PATH_TO_OUTPUT = "/home/wayne/FGFS/osm2city/Kansas/custom/state/w097n37"
PATH_TO_OSM2CITY_DATA = "/home/wayne/FGFS/osm2city-data"
OSM_FILE = "data.osm"
BOUNDARY_WEST = -97
BOUNDARY_SOUTH = 37
BOUNDARY_EAST = -96
BOUNDARY_NORTH = 38
NO_ELEV = False
ELEV_MODE = "FgelevCaching"
FG_ELEV = "/home/wayne/FGFS/install/flightgear/bin/fgelev"
BUILDING_MIN_AREA = 20.0
BUILDING_REDUCE_RATE = 0.01
BUILDING_MIN_HEIGHT = 1.0
PREFIX = "TEST"
PATH_TO_SCENERY = "/media/sf_terrasync"
PATH_TO_OUTPUT = "/media/sf_fg_customscenery/TEST"
PATH_TO_OSM2CITY_DATA = "/home/vanosten/develop_vcs/osm2city-data"
FG_ELEV = "/home/vanosten/bin/fgfs_git/install/flightgear/bin/fgelev"
OSM_FILE = "foo.osm"
BOUNDARY_WEST = -96.8124000
BOUNDARY_SOUTH = 37.8004000
BOUNDARY_EAST = -96.7788000
BOUNDARY_NORTH = 37.8150000
NO_ELEV = False
FG_ELEV = "/home/vanosten/bin/fgfs_git/install/flightgear/bin/fgelev"
BUILDING_MIN_AREA = 20.0
BUILDING_REDUCE_RATE = 0.01
BUILDING_MIN_HEIGHT = 1.0
The reason why it does not generate the airport terminal is that there are no suitable textures. This is an area, where a lot is left to do - especially having more and more diverse textures (in this case for terminal).
model it as a static model and submit the scenery model database.
vanosten wrote in Sat Dec 17, 2016 2:26 pm:[*] Speed might or might not be faster. However given that much of the time is used on elevation probing the difference will not be crucial.
psadro_gm wrote in Mon Dec 19, 2016 5:01 pm:Since it's always a regular mesh [...] I expect it to be crazy fast
psadro_gm wrote in Mon Dec 19, 2016 5:01 pm:I would love to know if elevation probing could be sped up using the experimental meshes I am creating.
The ultimate goal would be to perform all elevation probing at runtime, so we would only store offsets in the data.
Users browsing this forum: No registered users and 7 guests