Ian, turn off two way editing, especially if you are not using it. This relies on shared XML source. That does not support any thing that is not specified in the bglcomp schema such as background images and MSFS scenery polys.
If you are not using two way editing then ADE uses it's own format which does remember those elements.
Hi Jon:
Regarding work underway here to interpret MSFS SU9 Polygons (that a 'legacy' FS Schema may otherwise regard as "airport" BGLComp XML):
https://www.fsdeveloper.com/forum/threads/bglviewer-for-fsx-bgl-files.432840/post-902163
...I have not yet immediately / directly tested the XML project output of Airport2Project in the MSFS DevMode GUI.
Rather, I have worked with ADE's compiled XML version of the ADE "imported / converted" ARP2PROJ source XML ...via MSFS DevMode GUI.
Having seen this thread now, have I 'goofed' by first opening original XML code output by ARP2Proj in ADE, then attempting to work with ADE's compiled XML version of the ADE "imported / converted" ARP2PROJ source XML ...via MSFS DevMode GUI ?
NOTE: Thus far, I have
always told ADE 2020 to utilize "2-Way Editing" for any derived airport I work with for any purpose via ADE.
I am curious as to whether
ADE 2020 Alpha 2021 et seq. has yet implemented the 'new' SU9 Polygon code, to make it possible to have those objects and code types available in the "2-Way Editing" code output by ADE ?
If not, should those of us wishing to work with
both the MSFS pre- and post- SU9 versions of Polygons for Terrain Flattens utilize exclusively the MSFS DevMode GUI, rather than ADE ...to be able to successfully implement flattens and misc. textured polygons at MSFS 2020 airports ?
PS: Does the "
ApplyFlatten" feature actually
NOT work to flatten "Airport Boundary" / Radius areas ...via ADE 2-Way Editing ?
docs.flightsimulator.com
"
Apply Flatten
Checking this option will auto-generate terraforming rectangles within the bounds of the airport test radius to flatten the terrain. These rectangles are internally defined and not rendered in the world as objects, although their effects will be visible on the terrain."
<
Where exactly do we find this code, assuming we can de-compile / output it into XML / ESRI SHP files ? >
Related SDK links:
https://docs.flightsimulator.com/ht...perties.htm?rhhlterm=Flatten&rhsearch=Flatten
https://docs.flightsimulator.com/ht...m?rhhlterm=ApplyFlatten&rhsearch=ApplyFlatten
IIRC, past ADE versions normally included FS' default vector for Airport Boundary Fences in the 'derived' project code.
If we compare FS'
default vector Airport Boundary Flattens in (legacy FS) CVX-derived project code,
Flattens match (Airport Boundary) Fences.
If working with ADE, would we otherwise be compelled to use an external work-flow (
ex: CvxExtractor XML output) to:
* de-compile FS' default vector objects for Airport Boundary Fences / Flattens in 'derived' project code and output XML code
...
then:
*
Import XML (this feature is obviously 'missing' from ADE 2020 Alpha 2021
et seq.)
...to successfully display / edit / output FS' default vector objects for Airport Boundary Fences and Flattens via the ADE GUI ?
BTW: I see ADE 2020 Alpha 2021
Project Tree lists a SHP Poly, but
no Terrain Polygon ...if "Add Polygon" makes a
new Flatten.
How does a SU9 Flatten "
Polygon" affect MSFS' default Flatten CVX vector rendering, and does it work via "
Apply Flatten" ?
Thanks in advance for your clarification as to whether / how we may implement "Terrain" attributes at MSFS airports via ADE.
GaryGB