Hi Ed:
Looking good ! :ernae:
BTW: Regarding Rich's question... what terrain mesh were you using for this area when you set the elevation for the flatten and ground poly ?
Also, what slider settings (% mesh complexity and mesh meters resolution) did you use at the time ?
The elevation for any ground polys and flattens are of course necessarily a fixed value, but the scenery library objects would automatically adjust to ground level if they were placed with AGL=True in the placement XML file.
The FSG V2 terrain mesh for the USA is based on 10 Meter source data, and the ACES FSX default USA source data is based on lower resolution 30 Meter data.
Although the FSX default terrain mesh can be dynamically "oversampled" by setting one's slider at 10 Meter mesh resolution in the sim, there will be inaccuracies in some areas.
Indeed Justin Tyme had begun further refining the initial attempts by ACES to address airfield elevation inaccuracies in the terrain mesh, but any such fix in either ACES FSX default or FSG terrain mesh will still be over-ridden by any "flatten" we choose to place under our own "home-built" 3rd party airfields.
Additionally, there may terrain meshes that accompany add-ons for Mt. Ranier and it's surrounding environment (Ranger Creek is down in the shadows below Mt. Ranier).
If by any chance one of those add-ons with a 3rd party mesh is loaded in FSX, and it happens to have an internal resolution of 9.6 meters or higher (a FSX mesh resolution slider setting of "less than" 10 meters such as 5 etc. would enable this), it may end up being displayed instead of the FSXdefault or FSG add-on terrain mesh.
It is possible that Rich could purposely adjust his FSX mesh sliders to "down-sample" how his terrain mesh is displayed at Ranger Creek to make your airfield look OK on "his" system ...if we know what terrain mesh and FSX slider settings you chose to use on your system when you built this scenery (unless the FSG data set shows the valley and creek bed to be considerably deeper within the shadows of Mt. Ranier than the FSX default !).
Rich could try purposely adjusting his FSX mesh sliders to "down-sample" how his terrain mesh is displayed by setting the slider to a number "higher-than" 10 meters or more (effectively reducing his terrain mesh resolution).
Of course the trade off might be one could lose some of the wonderful details otherwise seen on Mt. Ranier after one is "up and out of the shadows" below !
FYI: Both FSX default and FSG V2 terrain meshes are constructed with the FSX SDK method that allows dynamic "up and down"-scaling of the displayed mesh resolution to achieve multiple Levels of Detail ("LOD") in the sim.
I'll be looking forward to seeing more folks "re-discover the Georender airfields in FSX"; ...keep up the great work, Ed ! :mixedsmi:
GaryGB