This once agains highlights the need for scenery designers to “protect” their airports against third-party meshes by placing exclusion zones - even if no offending trees/objects appear when used together with default XPlane mesh.
I have amended the (very nice) latest version to include exclusion zones and also remove the “always flatten”. Yes, there is a little bump on the runway, but it doesn´t make it unusable (and will be even better after next scenery recut which will smooth out the area). Property should only be used when runway is unusable without it.
Jan Vogel March 13, 2021 7:28 AM
Reporter has checked out the airport, he will hopefully fix it.
cjreed May 10, 2021 10:59 PM
Investigated the issue and it's not an issue when Default X-Plane scenery/overlays are used (see attached screenshot)
Probable that issue reporter has a 3rd party overlay or scenery (e.g. SpainUHD or X-Europe) - which is where the fault would be.
cjreed May 10, 2021 11:01 PM
I'd therefore suggest the issue be closed.
Jan Vogel May 11, 2021 5:59 AM
This once agains highlights the need for scenery designers to “protect” their airports against third-party meshes by placing exclusion zones - even if no offending trees/objects appear when used together with default XPlane mesh.
I have amended the (very nice) latest version to include exclusion zones and also remove the “always flatten”. Yes, there is a little bump on the runway, but it doesn´t make it unusable (and will be even better after next scenery recut which will smooth out the area). Property should only be used when runway is unusable without it.