Might that warrant a little extra effort to include mesh for the area, or any other potential workaround for FS9 limitations, that is obviously the call you get to make. Worth asking at least.
The issue is, you are assuming is a little effort but, as I've explained already, and as being confirmed by Anydigital (that did the local flatten fix for CH Pro in FSX) making a mesh fix for 3rd party meshes in FS9 that would surely fix any problem, it's not very pratical because:
- FS9 doesn't allow small local meshes with arbitrary shapes, they need to fully cover at least a LOD quadrant. THAT'S why, for example, a Grand Canyon mesh might affect KLAS airport
- Because of this, and because of the fact that FS9 will NOT just load the topmost mesh on the Scenery Library, but will ALWAYS load the highest-resolution mesh regardless of its position in the Scenery Library, we would need to start a "Mesh war". Meaning: in order to be sure to overwrite ANY 3rd parth mesh that might be around, we should create it at the highest LOD level possible (regardless of the fact if that resolution is real or faked) JUST to "win" the mesh war and be sure to be on top of everything else, because just being on top of the Scenery Library would not be enough.
I really think this is not something we are supposed to do: if WE were in the business of selling mesh products, it would have been reasonable to pretend, as customers, to implement a similar processing to our meshes, compared to the one Microsoft has done for the default ones, that makes a lot of sense, because it would prevent any problem with any airport that, in the FS world, will always be entirely flat across the whole perimeter, because this is what the FS engine requires. A 3rd parth mesh that doesn't take into account this issue, it's not a complete product, IMHO...