Texture themselves can't cause any bleeding, it's the conflict between the altitude of ground *polygons* that use those textures that can create the problem. In FSX, removing a texture will make an object disappear so, one might have the wrong impression of having fixed the problem, but it lost the object as well.
An altitude conflict might be created by:
- Another afcad that is still active
- Another mesh that has been put on top of Ohare. The scenery has an embedded native FSX flatten to prevent this so, if it stays on top, it will be able to flatten all terrain elevation underneath, without any need to provide a custom mesh.
- Another scenery with ground polygons. If a scenery range was badly programmed, even a scenery on the other side of the world might create issues at KORD.
- Video card with not enough z-buffer precision. z-buffer settings usually can only tweaked using tweakers.
I would like to point out that I'm still unable to reproduce this problem, even by playing with FSX settings, there's absolutely no bleeding or visible flickering.
The issue that might happen with XGraphics might be a different one, but it's not really a bleeding, it's more like a see-through. Since they replace default runways textures with their version that, for runways, includes details like tire markings, since we *also* have tire markings, but on a different layer and in much higher resolution, it's possible that you might see both, if KORD is used with XGraphics. But that wouldn't look like a bleeding. And, it should work the opposite as observed, meaning it should only appear with XGraphics enabled.