Paul,Not a flame either, just IMHO, but after looking at his setup and gear, it indeed seems to be a simple step in the troubleshooting process to take - a step from which he could learn much. His kit can certainly handle it (DX10) as it it quite a bit more up-to-date than is typical for folks who have the problem he is describing.So, quite the contrary of suggesting "polished rims" or anything of the sort for a mis-firing engine - I'm suggesting he look at his engine management software (to continue with the analogy). Absolutely appropriate and on point to the issueSo, bottom-line, even though it is considered a "Preview" (I'd very much dispute the 'broken' assesment, though, as I use it every day with no issue and with zero 'tweaks' to my .cfg file) it is a troubleshooting step that does not cost any $$$ to try, is easily "undone" and is indeed a superb test as it utilizes a completely different vid software graphics architecture...indeed the one for which his vid card is designed for (DX10).What's to lose by checking that box and taking a fly around the circuit? Nothing.Let's here from him - I hope he gives it a try - up-to-date graphics driver, 'fresh' FSX generated .cfg & the DX10 box checked - and posts us with the results, good, bad or indifferent. I'd wager he just might be pleasantly surprised...Cheers!

Nice reply Patrick,1.Lets go with switching to the DX10 preview, if he doesnt run into the running out of memory situation he has now, what has he learned? Nothing other than he still has a DX9 issue that we cant pin down and yet needs to still be resolved that he has been sidetracked from.2. You truthfully can not say you dont have any issues with DX10, for one thing the only way to resolve the flashing runway and taxiway intersections is to have a new afcad for 99% of the airports, and still does not address the flickering of textures on some of the other 3d objects that persist. 2b. Many of the developers of FSX add-ons have no come right out and said they will not try to develop support for DX10 preview because it is broken, as a developer of scenery add-ons I feel the same way until some other solutions to problems that exist come along, as unfortunant as it is (the FPS improvements from just the batching of Auto Genalone are great).Quote from FSDreamTeam: 1/18/09:"Thats to be expected. We don't support DX10 in any of our sceneries, with the exception of JFK which, incidentally, took a lot of criticism for having less ground texture quality compared to the other ones.Quote:Q - I'm one of the many FSX users who run aircraft liveries and airports only in Preview DirectX 10 mode. If a livery or airport does not render properly in Preview DirectX 10 mode, I don't use it.FSDT - That's your own choice, but you are in a very small minority. DX10 Preview is so buggy, that not even the default airports renders correctly. Is really an unfinished work"

I let FSX rebuild my config, no help. Bloody Microsoft :(