Context: When placing a higher priority polygon over the top of another polygon, the underlying polygon still takes effect.
Bug description: Polygon priorities used to work well in 2020, but seem completely broken in 2024. Any polygon placed on top of another doesn’t have the desired effect despite any priority settings. This is particularly noticeable with Vegetation, but also applies to buildings, excludes and secondary height maps.
Repro steps: Place a polygon with vegetation. Place a higher priority vegetation exclude on top. The exclude does not work.
I assume by “vegetation exclude” you mean a vegetation polygon with density set to 0?
Is this something you used on MSFS 2020?
I checked on version 1.38.2.0 and already, scale and density properties were not overridden:
I don’t remember that issue in 2020 but I could be wrong.
Regardless, expected behavior of a higher priority polygon would be to ‘replace’ the polygon(s) of lower priority.
If a higher priority opaque Apron is placed on another opaque apron, it replaces the texture. It would be nice to have the same behavior with polygons.
In addition, I’m not only talking about Vegetation. I had to clean up a 5 mile radius of dodgy tree Photogrammetry using building exclude, and it wasn’t possible to place small higher priority polygons to retain some of the small areas of Photogrammetry buildings.
