One known issue in the "DX10 preview" mode are flickering taxiway textures (which also spills into runways). I exclusively fly in DX10 mode because it performs and looks better (except, of course, in areas where those texture problems occur). My question is simply: Is this bug hard coded into the binaries or could some driven developer do something about it? I would certainly be willing to pay some $'s to get that fixed once and for all! :(/Jonas

Hi Jonas,Someone in the french speaking forum wrote that Afcad files attached to sceneries cure this problem.That's why few payware sceneries get rid of the flickering textures.So there is probably a solution but no one took the lead unfortunately.I am one of those who solely fly in DX10, with a much smooth simulator and double (if not more) fps.

Hi Jonas,Someone in the french speaking forum wrote that Afcad files attached to sceneries cure this problem.That's why few payware sceneries get rid of the flickering textures.So there is probably a solution but no one took the lead unfortunately.I am one of those who solely fly in DX10, with a much smooth simulator and double (if not more) fps.

Can you (or someone else) describe how those AFCAD files can be fixed? Unfortunately I don't speak French... :( Cheers/Jonas

What's interesting is that not everyone has this problem with DX10. I do. It seems to be the concrete textures that are a problem. I suspect that if you change them to , say asphalt, the problem would go away. Bob

What's interesting is that not everyone has this problem with DX10. I do. It seems to be the concrete textures that are a problem. I suspect that if you change them to , say asphalt, the problem would go away. Bob

That's very interesting Bob.Could you please tell how to replace the concrete textures with the asphalt ones?Thanks.

That's very interesting Bob.Could you please tell how to replace the concrete textures with the asphalt ones?Thanks.

The solution, I think, is at this FS Insider link: http://www.fsinsider.com/tips/Pages/SA0002.aspx. The problem is Polygon Z-fighting and I can see how another AFCAD might be conflicting with another AFCAD from the same airport if both were being used BUT, the AFCAD sitting at the highest priority in the scenery.cfg would be the one that would prevail or so I have been told in the past. The airport at Friday's Harbor (the default airport) has this problem with DX10 running. I did some searching through Google for "Z-Fighting" and came up with many links relating to this problem which sounded very familiar to our problem. However, Phil Taylor was well aware of this problem soon after DX10 was released but stated it was a display driver problem and he was talking to Nvidia to work on a fix but Nvidia never came up with the fix (Nvidia was the only video card that had DX10 capabilities when DX10 was first released; ATI followed some time later). As discussed in the link I provided, it may be fixed using the FSX SDK but that's way beyond my paygrade even if it is possible. I was hoping for a SP3 to FSX to fix this problem but Microsoft decided to terminate the ACES Team and the FSX project. If you do a search in the video card hardware forum on AVSIM for runway flickering, you'll probably run into several long threads regarding this problem. When Phil Taylor was still working for the ACES Team and stated it was a display driver problem, I started a thread requesting everyone who had this problem to submit a problem report with Nvidia thinking a bunch of problem reports would get Nvidia's attention. I even provided the link to the problem report site and exactly what words to say in the problem report. Several of us did submit a report, including I believe David Roch who pushed the thread forward as he thought it was a great idea. Phil Taylor even provided comments about my plan and thought it was a great idea. But, alas, it failed and we continue to have flashing runways/taxiways and no arrows showing when you want to display the route to taxi to the gates and other problems mentioned in the video card forum. BTW, this problem is discussed frequently in the Nvidia forums too. Nvidia techs evidently do not believe this is their problem or the problem is way beyond their technical expertise (I doubt they could care less about us flight simmers....).Best regards,Jim Young

I don't use DX10 because I get worse fps. So I don't mess with it. However, as an experiment, I just used ADE to change some concrete textures to tarmac, and display is proper in DX10. I suppose if someone were to write an app that did this for all concrete textures, it might work. I think this has been documented before, somewhere.Bob

"The solution, I think, is at this FS Insider link: http://www.fsinsider.com/tips/Pages/SA0002.aspx. The problem is Polygon Z-fighting and I can see how another AFCAD might be conflicting with another AFCAD from the same airport if both were being used BUT, the AFCAD sitting at the highest priority in the scenery.cfg would be the one that would prevail"It was funny to come from a thread discussing how inaccessible flight simming is to young people and why consoles are the future,and read the above.Wasn't Polygon Z-fighting a movie with Jean Claude Van Damme?Anyway, my impression is that DX10 was an interesting experiment but holds little value for most people. Since you guys obviously know what you're talking about, I hope you'll forgive the slight off-topic question of whether familiarizing myself with DX10 is worth it. I know some add-ons boast DX10 compatability, and other things act like it is garlic to vampires.

The solution, I think, is at this FS Insider link: http://www.fsinsider.com/tips/Pages/SA0002.aspx. The problem is Polygon Z-fighting and I can see how another AFCAD might be conflicting with another AFCAD from the same airport if both were being used BUT, the AFCAD sitting at the highest priority in the scenery.cfg would be the one that would prevail or so I have been told in the past. The airport at Friday's Harbor (the default airport) has this problem with DX10 running. I did some searching through Google for "Z-Fighting" and came up with many links relating to this problem which sounded very familiar to our problem. However, Phil Taylor was well aware of this problem soon after DX10 was released but stated it was a display driver problem and he was talking to Nvidia to work on a fix but Nvidia never came up with the fix (Nvidia was the only video card that had DX10 capabilities when DX10 was first released; ATI followed some time later). As discussed in the link I provided, it may be fixed using the FSX SDK but that's way beyond my paygrade even if it is possible. I was hoping for a SP3 to FSX to fix this problem but Microsoft decided to terminate the ACES Team and the FSX project. If you do a search in the video card hardware forum on AVSIM for runway flickering, you'll probably run into several long threads regarding this problem. When Phil Taylor was still working for the ACES Team and stated it was a display driver problem, I started a thread requesting everyone who had this problem to submit a problem report with Nvidia thinking a bunch of problem reports would get Nvidia's attention. I even provided the link to the problem report site and exactly what words to say in the problem report. Several of us did submit a report, including I believe David Roch who pushed the thread forward as he thought it was a great idea. Phil Taylor even provided comments about my plan and thought it was a great idea. But, alas, it failed and we continue to have flashing runways/taxiways and no arrows showing when you want to display the route to taxi to the gates and other problems mentioned in the video card forum. BTW, this problem is discussed frequently in the Nvidia forums too. Nvidia techs evidently do not believe this is their problem or the problem is way beyond their technical expertise (I doubt they could care less about us flight simmers....).Best regards,Jim Young

Yes Jim, I remember your thread about submiting the problem to Nvidia and your efforts to get P.Taylor involved.Unfortunately we can't expect any kind of research from Nvidia given the fact that ATI's cards present the same problem and as you say they don't really care about FS.It is obviously a Microsoft/ACES glitch and unless one of us have the skills to find a solution we'll have to live with it.Really a pity!

I don't use DX10 because I get worse fps. So I don't mess with it. However, as an experiment, I just used ADE to change some concrete textures to tarmac, and display is proper in DX10. I suppose if someone were to write an app that did this for all concrete textures, it might work. I think this has been documented before, somewhere.Bob

To me it sounds like the "Z-fighting theory" conflicts with Bob's texture-replacement-solution. If it's Z-fighting (btw, Tim, I think that must've been Chuck Norris :( ) I don't see how a different texture could resolve it? The "driver theory" also sounds fishy btw. I have an ATI card and it has the same problem. Unless ATI and nVidia are using the same code base for their drivers it's very unlikely they would both end up with the same bug.Bob,I'll fiddle some with ADE and see what happens. Thanks alot./Jonas

KSEA had the problem of flashing runway and taxiway junctions before the 3rd runway was added. It would appear that editing an airport and resaving could be part of the solution?My 2 cents.Happy FlyingKen SummersGA-MA790GP-UD4H, Phenom II X4 940, 4 G DDRII, ATI HD4650 (DX10)

Yes Jim, I remember your thread about submiting the problem to Nvidia and your efforts to get P.Taylor involved.Unfortunately we can't expect any kind of research from Nvidia given the fact that ATI's cards present the same problem and as you say they don't really care about FS.It is obviously a Microsoft/ACES glitch and unless one of us have the skills to find a solution we'll have to live with it.Really a pity!

Totally agree David!Best regards,Jim Young

Any new developments on this matter? Has anyone been able to cure it?

DX10 is such a mixed bag that I doubt that there will be a "cure". Some people have no problem with it, and get better performance. Others, like me, find it unusable. With some drivers and a very high resolution monitor, display was OK. But in general, concrete and cement textures are very grainy. As well as flashing where concrete taxiways meet an asphalt runway. Changing those textures to something else make the display problem go away on my system. It seems to be a "problem" that no one really cares about. Bob