(fixed_alfa) On EHAM some vertice seems to be inverted see this picture. I saw this (if I remember correctly) with an older development version of terragear, but this was fixed some time ago. (unfixed_alfa) On ELLX there are some problems with "holes" in the pavement that flicker between grass and tarmac. On many airports where the taxiway signs are now taken from the apt.dat and put in the Terrain folder, the old signs still remain in the Object folder. Also if you fly over this at just the right altitude you can see this area switching back and forth between being water and land (thanks hvengel) The old scenery didn't have either of these problems. Flightgear world scenery pack download code#
When flying over this you can see trees sticking up out of the water so the code that is placing random trees thinks this is above sea level. There is an area on the coast just to the north of the Moss Landing airport that is above sea level if you are up above 1000ft but is covered in water is you are on the deck.
The Moss Landing airport (on the coast a little bit south of KSFO) is partly submerged into the water and the airport's north end is elevated above the terrain around it. Terrain and ocean z-fighting such as east of EKCH. On the same matter, clipping between river and terrain is somewhat strange, making the river "climb" over the terrain, noticeably under bridges - probably due to the presence of the roads. (unfixed_alfa) On sharp cliffs, water sometimes climbs over the cliffs (see e000n40/e000n49/2958056 and this picture for instance). Airport being located over two different tiles sometimes renders bad, leading to z-fighting (LEJR, UKKE.). This way you limit the number of "line features"). (fixed_alfa) Some troubles on very dense cities (such as Paris) leading to grey-white triangles on cities - see also yellow lines (unfixed_alfa) Some line issues on small airfield with LTA specific runways (LFNH, LFLI.) - the small centerlines on the runways are "floating" over the runway (20 cm to 1m), leading to some gear destructions -) (they didn't use lines, but surfaces that are defined as transparent and borders defined as the line type. (fixed_alfa) Some z-fighting (clipper is generating the correct number of contours, but the airport hole is wound as a boundary, not a hole) and/or triangles on airports (LFRH, EDWJ (partially submerged).). Clipping of OSM roads on water showing height glitches (due to bad coast/river lines definitions and bad clipping): clip roads against landmass or add landmass where required? Should roads over bridges get removed, even in places where a 3D bridge model is missing?. The addition of OSM roads added a lot of new triangles, hence the fps reduction. This is being worked on, however keeping a high quality scenery with a lower count of triangles is not easy. The new scenery is currently quite heavy and hardly runs and can lead to FG crashes if run on systems with less than 4Gb RAM and if you're not using FG 64 bits. Use our webforms, if necessary, to fix this. 
Thus, if some objects were defined with a bad elevation or bad offset, they may have taken a bit of elevation. World Scenery 2.0 is available through the usual channels:
Road, rail and rivers courses line data by OpenStreetMap.The latest airports (2013.10), maintained by Robin Peel of X-Plane.Several custom land cover enhancements (to be listed here.).See for the correspondance between CORINE and FG textures
CORINE Land Cover 2006v16 for Europe (Source : European Union, SOeS, CORINE Land Cover, 2006 - ).ViewFinderPanoramas elevation model by Jonathan de Ferranti (using terrafit.py -x 20000 -e 10),.This FlightGear World Scenery was compiled from:
0 kommentar(er)
