so this will not be fixed
then? That's a shame, because all your other airports work just fine using P3Dv3 and EZDok.
You already asked this question, and I already replied in the post above. I'll repeat it again: KIAH is more precise with the ground/polygons altitude difference, so it will have way less issues with vehicles wheels sinking in the ground, which many users found annoying in the other sceneries.
The downside of it, is that it requires more precision from the camera view, which is why you get some flickering with EZDOK CAM, which I guess is optimized for closer view.
And so do all airports of FlyTampa or Flightbeam for example
FlyTampa still use the slow FS8 ground polygons, which are processed in realtime by the sim (that's why they are slower) to conform with the round earth, so they don't have this issue. You pay for this in fps cost.
Flightbeam used them too, but it's going to switch to the same method we use for his next sceneries, since he has access to our scripting engine, so it's possible he'll have issues with non-standard cameras too.
We are handling the Avatar mode separately, for example ( a fix which is still not released ), but we can't support *every* other possible camera configuration.
I really don't see why KIAH has to be different here. A fix would be highly appreciated.
The scenery works fine with default cameras, so there's really nothing to fix. You can probably fix it yourself by adjusting the clipping parameters in the EZDOK custom cameras configuration.