DVA1873
Captain, B737-800
E-MAIL
Joined on September 04 2004
Century Club
Western United States
141 legs, 244.5 hours
61 legs,
98.0 hours ACARS
|
Posted onPost created on
September 12 2006 00:28 ET by Tracy Braithwaite
|
DVA1583
Senior Captain, MD-11
OLP
Joined on March 23 2004
Everett 250 Club
Online Six Century Club
50 State Club
DVA Fifteen-Year Anniversary
Seven Century Club
South America
710 legs, 1,938.2 hours
619 legs,
1,760.2 hours online 589 legs,
1,630.3 hours ACARS 16 legs,
61.2 hours event
|
Posted onPost created on
September 12 2006 01:53 ET by Charly Azcue
|
FS Genesis FAQ
I've just installed your terrain mesh. Why do some of the runways at some of my airports appear to be sitting on plateaus?
In most cases, the terrain is accurate but the airport's elevation isn't.
This is usually due to the "flat runway" limitation of FS. Since the airport's listed elevation is usually the highest point on the airport grounds, and isn't necessarily the same as the airport's runway threshold elevations, which invariably are all different, or the elevation of the rest of the airport in real life.
Airport's in real life are never perfectly-flat, yet that's the only thing FS can depict--perfectly flat airport and runways. Since the FS database uses the highest elevation on the airport grounds, the result is the plateau effect in some instances when highly-detailed and highly-accurate terrain is applied.
As an example, go to airnav.com and look up Davis-Monthan AFB in Tucson. Go there is FS and note the elevation at one end of the runway is perfect, but at the other end it's on a plateau. Note the threshold elevations of the ends of the runway at Airnav.com. They are over 100 feet different. Since FS can only depict a perfectly flat runway, one end is on a plateau.
Just something we have to live with until FS comes up with a way to depict runways and airports as they are in real life--uneven.
KLAS --> http://airliners.net/open.file/0482808/L/
Regards
|