I was doing a little scenery project to redo the Wabash River in SW Indiana, US. That went OK, but there is a little grass strip II33 right along the river. The problem is that the default airport is set at 194m, whereas the terrain appears to be about 124m. I looked at it in FS9 with FSG mesh, and the same problem is in there. In FSX, it appears that MS has jiggered the default mesh to create a hill for II33 to sit on, but it's so close to the river that causes a steep cliff (I don't have FSX improved mesh but I used GE and the USGS data to get "ground truth".
Anyway I see the same kind of elevation problem as with FS9: I create an xml file from the default and change the airport, runway, and start elevations to 124m (lower than default), deleted the runway and starts compiled and placed in addon scenery. When I start at II33, aircraft is placed and I have a floating runway at the default 194m. So I created an airport element xml @ 124m compiled and placed it in the default scenery\0302\scenery and that fixed it. So I guess we have the same problem as FS9 with elevation changes not taking in all cases unless an "afcad"stub is in the default folders?
scott s.
.
Anyway I see the same kind of elevation problem as with FS9: I create an xml file from the default and change the airport, runway, and start elevations to 124m (lower than default), deleted the runway and starts compiled and placed in addon scenery. When I start at II33, aircraft is placed and I have a floating runway at the default 194m. So I created an airport element xml @ 124m compiled and placed it in the default scenery\0302\scenery and that fixed it. So I guess we have the same problem as FS9 with elevation changes not taking in all cases unless an "afcad"stub is in the default folders?
scott s.
.