Hi Aboud:
Congratulations on your success with getting a HECA airport terraforming Polygon to work at a
+50 Priority setting.
I had not yet tested using higher priority numbers, as the SDK docs indicated that
default scenery was only using layers up to 10 or so.
I understand that you may subsequently wish to use terraforming to blend HECA into the surrounding terrain.
But, IMHO, you may not need to do as much work if you first correct the ARP and RWY Altitudes, then apply the "Flatten" setting for the ARP display radius ...prior to fine-tuning your terrain blend at the edges of the airport area with such a terraforming Polygon.
In my own test scenario, after having first disabled the HECA
*.JSON files cited above, I corrected the ARP and RWY Altitudes, and applied the "Flatten" setting for the ARP display radius; then I was able to render a terraforming Polygon for the airport at
+12 Priority.
It is important to first check and see if MSFS re-installed the
*.JSON files cited above when it next re-started and checked for updates.
If in fact MSFS did re-install the
*.JSON files cited above when it re-started and checked for updates, they must be deleted again.
Apparently MSFS did this on my installation, so I had to delete the files again; we may need a better way to disable the Deluxe HECA.
So, in summary, I was able to change the scenery render to the specified Altitude by only editing HECA airport parameter values.
I was then able to get a terraforming Polygon to render at only
+12 Priority.
I shall probably now test HECA with its
*.JSON files cited above
enabled, then see if a terraforming Polygon will render at
+50 Priority.
FYI: I am trying to find a less complex solution to enhance HECA using a default airport boundary SHP polygon derived by CvxExtractor.
But, the learning curve for most would-be developers in utilizing ESRI SHP files derived via that method may be impractical to take on.
We could otherwise save a lot of work by being able to import / edit external GIS-data set ESRI SHP files into ADE and/or SDK DevMode.
ADE / DevMode now forces us to make Polygons by
manual clicks to create all vertices for each such scenery object in one's terrain.
I may post more on this pending progress in achieving a simplified GIS app work-flow to offset effort of manual Polygon creation.
GaryGB