All of the airports we have so far released have custom mesh. It’s been a long
journey trying to find different methods to integrate such custom mesh when
running into issues that stem from the way the default mesh has a N to S
integration, integrating a sheer drop seems impossible without the use of 3D
fake terrain. After running extensive tests, it seems that there is an
inherent issue with default photogrammetry causing aprons, taxiways and
runways to be bumpy, in some cases so much so, that it leads to the aircraft
on top of the terrain layer crashing. Switching the photogrammetry off offers
an instant fix, eliminating the photogrammetry via TIN exclusion polygons
seems to have very little to no effect, I have no idea why this is so poorly
implemented in the SDK toolset. In the image below for instance there is an
invisible terrain mesh layer that has contours that strongly deviate from the
actual visible terrain profile:
When taxiing the aircraft just
before this particular area at Alicante Airport, you can actually see the
wheels disappear slightly into the ground, then they rise above the ground, as
shown above, and shortly afterwards the aircraft falls, as if it had taxied
onto a ramp that abruptly ends with much lower terrain. With photogrammetry
set to OFF, there is no such issue and the custom terrain mesh is smooth in
the apron, taxiway and runway areas, just as we designed and built it. Could
someone at Asobo kindly look into this and shed some light on why this
invisible terrain is present, and ideally find a solution to eliminate this
particular issue?