Hi Ken:
I have the files you attached to your reply immediately above.
https://www.fsdeveloper.com/forum/threads/ground-elevation.444517/post-814851
Hi Gary,
Sorry it took me a few days to reply. I was experimenting with ADE and trying out those scenery options. Okay, I'll hold off on the Alabama scenery until everything else is correct. Actually, I thought that when I removed the airport background, that would have taken care of that but it doesn't. I think I understand it now when the term "airport background," is used. It's the green area around the airport that separates the airport boundary from the rest of the land, and even after one excludes it, there's still a ground layer below that. Is this the hard core layer, or ground scenery that I've read about in that tutorial?
Regardless of the existence of
any terrain mesh file that underlies an Airport Background polygon, if it has a "flatten" attribute, the resulting CVX vector "flatten" should over-ride and modify
any such terrain mesh file ...within the extent of coverage of that CVX vector "flatten".
What utility did you use to create the CVX vector 'flatten-only' polygon at KHSV in:
KHSV_ADEP4_KM_CVX.bgl ?
I ask this as there is no Airport Background CVX vector 'flatten-only' polygon at KHSV in:
KHSV_ADEP4_KM.ad4 when loaded into ADE.
This is what I see at KHSV in FSX Default:
...
with:
*
KHSV_ADEP4_KM_CVX.bgl (flatten-only made via ?)
...
and:
*
KHSV_ADEP4_KM.bgl (airport made via ADE)
NOTE: The entire flatten "lower level area" at KHSV has a uniform "continuous" Altitude when your files are loaded on my default FSX install.
It is also not clear why default Roads local to
KHSV are '
indented' with a 'slope' on
your FS install
AFAIK, the default Roads local to
KHSV do
not use "
FlattenOffsetMeters" in Terrain.Cfg:
// Roads - asphalt / 2 lanes / undivided median
[Texture.145]
Name=Roads_Asphalt_2_Lanes_Undivided_Median
Color=FFC00000
guid={325DD470-B342-4D15-AC54-F67ED9F5914F}
LegacyId=1163
Textures=hiway_2_lane_asphalt_su.bmp,hiway_2_lane_asphalt_hw.bmp,hiway_2_lane_asphalt_su.bmp,hiway_2_lane_asphalt_su.bmp,hiway_2_lane_asphalt_su.bmp,hiway_1_lane_lm.bmp
Layout=3_PLUS_4
StripWidthMeters=13
Size=2
FlattenMode=flat
FlattenPriority=21000
LandClassRemapType=none
VectorAutogen={B4011B59-8B6B-C446-B79D-A9DA97AC3C05} (Small road with telephone poles only)
ExcludeAutogen=Yes
RenderToTexture=Yes
RenderPriority=102200
Water=No
BTW: Here is a comparison between internal Altitude values for the default (aka "stock") KHSV and your ADE-modified KHSV:
KHSV_ADEP4_KM ARP: 191.717 Meters
(-)
KHSV_ADEP4_KM_CVX vector flatten: 188.061996459961 Meters
(=)
3.655003540039 Meters = 11.99145 Feet
KHSV Stock ARP: 191.719
KHSV Stock CVX vector flatten: 191.719192504883 Meters
(-)
KHSV_ADEP4_KM_CVX vector flatten: 188.061996459961 Meters
(=)
3.657196044922 Meters = 11.99864 Feet
FYI: The ADE-modified KHSV airport Altitude values are compatible with default airport Altitude values.
This 'may' allow your ADE KHSV to work in FS without a need for altering default Traffic / Approaches
It seems that
you may have (1) or more (SHP2VEC CVX vector) Airport Background or (BGLComp XML) Airport infrastructure objects creating a "ground surface" which is being draped with Alabama Megascenery Earth photo-real imagery, and obscuring the intended
KHSV flatten area.
Please tell us if you have any other freeware or payware add-on scenery which may affect the
KHSV terrain, such as overlooked prior 'test BGLs' from personal projects at KHSV, or 3rd party terrain mesh, vector airport elevation corrections, OrbX "Global" products etc. that may overlap KHSV as part of very large coverage areas.
PS: You can link here- or via PM- to a large
ex:
*.KMZ by uploading it to a free file storage site such as DropBox, MediaFire, MS-OneDrive etc.
GaryGB
) have an intact, properly imported, 3D model aligned on a newly created and precisely geo-located imagery background.
