A few things are clear from this thread:
1. No one should be posting bug reports on this blog. This is not a bug reporter!
2. “Flickering” is a really vague term. I have heard the term flickering applied to Z-thrash (flickering of two near surfaces due to incorrect depth testing on the GPU) and also to temporal anti-aliasing) the flickering of small 3-d details as the camera moves.

So I guess I can say two things:

If you see a particular art asset flicker, even when you are close to it, that’s a bug. File a bug using the bug report. Here’s what we need: take TWO screen shots in a row, capturing the art asset in both phases of flicker. For example, if the roof is changing color, take a few screen shots in a row and send in two where the camera is in ALMOST the same place but with different colors on the roof. We can then go find that art asset you showed us and see what’s wrong.

Over time we will continue to adopt better anti-aliasing technology as it is invented and becomes available. In the meantime, users who are unhappy with the anti-aliasing in X-Plane can do a few things to cope:
* Turn up X-Plane’s anti-aliasing setting and turn down the screen resolution to compensate for the fps hit.
* Turn off HDR, then run at a high non-HDR anti-aliasing level like 16x.
* Turn down the world level of distance: temporal anti-aliasing is heaviest for small features on screen, which come from far draw distances for 3-d.

There is some flickering with HDR off as well. I think its the same buildings. Maybe there is an error with the art work ?

I have same issue with the flickering. Its seems like its certain apartment buildings and certain types of comercial buildings that flicker. I haven’t noticed the residential housing flicker. When you zoom in with the camera, you will notice the roof flickering from white back to black.

are there any plans on changing / improving the antialiasing algo´s to get rid of this awful looking texture flickering? Also the next question: When i fiddle around with AA i only have the CPU being maxed out, the gfx card still idles around (well… 0.2 to 0.999). Could it be that the AA is not computed on the GPU in certain cases? (GTX 570 and GTX 680 tested here, both nearly the same results, on an i7 3770). Thanks!

Thanks, Ben. Will do. I’m surprised — after digging about this issue on the .Org, with even the likes of Tom Curtis having issues in one thread I stumbled on, I would have thought this would be known. They even invoked your name. But no matter, I’ll be happy to file another bug that happens….with *any* aircraft. 🙂

Hi Steve,

I have no open bugs on exclusion zones. Someone should file a bug on that. I believe that the problem is _probably_ user error, perhaps caused by poor documentation, but only with a real bug report can I even know what people think they are seeing.

cheers
Ben