Pentium Core2Duo 2.6Ghz 3Gigs of RAM, and NVidia GTS450 (brand new) graphics running FSX. All drivers and programs up to date. Computer is clean and optimized, as well as un-needed programs disabled. This does not occur in FS9 or any other program. I don't want to reinstall FSX if I can avoid it.The problem started occurring once-in-a-blue-moon (can't recall when, but certainly before my new card), then more frequently. Now I can't run FSX without these flashing mix of (can't describe it) textures. Occurrences vary, sometimes there, sometimes not, almost always seems to be related to ground textures, though it has happened for me cruising at 16,000 feet in VC (to the aircraft itself) or exterior facing upwards too. On occasion, windowed mode or flipping between programs fixed it, but more often than not it didn't and only temporarily.Additional notes:-Not aircraft related (both 3rd party and default).-Not scenery enhancement related (no add-on scenery / X-Graphics reset to default textures).-Got in the F-18 at CYYZ Toronto (bad textures). Jetted up to high altitude and problem disappeared. Flew 100' off the ground out in the countryside (no problem). Did not reoccur until final approach to CYYZ. Does not relate directly to the Toronto area, just an example.-Again, YYZ in the ultralight problem looking southbound, and that's it. Went to slave lake, and no artifacts.-Happened at both scenery enhanced and default regions.-Played with graphics settings within FSX and no change.Any insight and help would be greatly valued.

What operating system are you on?

I just installed a new GTX 460 with 260.99 drivers and have seen the same happen.My previous 9600GT was rock solid - maybe it is the drivers, need to do some more [email protected] - Win32

Yeah, same thoughts here. I've got Windows XP Pro 32-bit with SP3. My new GTS450 graphics card has 1-gig memory. My old 8600 card with 256MB memory worked well (until it overheated and blew up). I have only one card with extra added cooling. On another forum, it was suggested to be a memory problem, but with the memory I have and even a fresh boot, I can't see how that would be the case. I am going to either reinstall or roll-back the NVidia drivers for my card (if I even have them).

NVidia doesn't make XP-32 drivers for the 4xx+ cards. Ok, I stand corrected I guess they still make XP-32 drivers.

Is it only me or are you using PMDG JS41 in all 3 shots - which makes me wonder, did you ever test any other aircraft or does it happen with other aircraft? I did see you wrote not aircraft dependable, but I still wonder since you posted one and only aircraft.Namely, I have different graphical problems with JS41 ONLY. As many other users do. PMDG didn't do squat about it and many complain - there was supposed to be a SP for this, but it never came out.Do you have your FPS locked?Do you have HIGHMEMFIX=1 installed?

Is it only me or are you using PMDG JS41 in all 3 shots - which makes me wonder, did you ever test any other aircraft or does it happen with other aircraft? I did see you wrote not aircraft dependable, but I still wonder since you posted one and only aircraft.Namely, I have different graphical problems with JS41 ONLY. As many other users do. PMDG didn't do squat about it and many complain - there was supposed to be a SP for this, but it never came out.Do you have your FPS locked?Do you have HIGHMEMFIX=1 installed?

Yes, as mentioned in other aircraft too. Haven't experimented enough to know if aircraft complexity affects it, but it still happens.Also, rolled back my drivers to a previous version (NVidia 260.89) with uninstall, and no change. At first I thought it might not happen in 2D panel mode, but indeed it does (in many instances it didn't happen in 2d panel view, but it did today!). FSX is almost useless until this is fixed. Considering a reinstall soon.

What if any chages have you made to the FSX.cfg?

What if any chages have you made to the FSX.cfg?

Hmmm....good idea. I don't recall exactly what right now - but I do recall something about a basic cfg file change to help improve scenery performance in FSX. Gonna start google-ing it now, but not sure what I'm looking for. Could have been on a previous install, but that was a while ago.Thanks for leading me that way...do you recall coming across that mod?UPDATE:::YESSS!! I found it thanks to you! My FSX cfg file had the "UseBufferPools" entries removed for increased performance (rather than just setting it to 0). On my first test, my performance went down significantly, but no more polygons!!I'll have to do further tweaking to see what I CAN do with my system, but thanks a lot.

Hmmm....good idea. I don't recall exactly what right now - but I do recall something about a basic cfg file change to help improve scenery performance in FSX. Gonna start google-ing it now, but not sure what I'm looking for. Could have been on a previous install, but that was a while ago.Thanks for leading me that way...do you recall coming across that mod?UPDATE:::YESSS!! I found it thanks to you! My FSX cfg file had the "UseBufferPools" entries removed for increased performance (rather than just setting it to 0). On my first test, my performance went down significantly, but no more polygons!!I'll have to do further tweaking to see what I CAN do with my system, but thanks a lot.

OK...screw it....it didn't work like I thought. I even deleted the cfg file and let FSX rebuild it from scratch, and the problem recurred.So here is what I have done most recently to my cfg file (today) to try and improve/modify performance:[bufferPools] (because before it was nonexistent)UsePools=1PoolSize=8000000RejectThreshold=98786 (as an alternative to using poo)[JOBSCHEDULER]AffinityMask=3 (dual core processor setting)[Display]WideViewAspect=True[Graphics]HighMemFix=1 (1024MB video card, previously nonexistent)SHADER_CACHE_VERSION=1[Main]DisablePreload=1I have played with enabling/disabling certain functions to find improvements, and I can't find anything that works. P.S. when I make changes to the cfg file, do I have to reload the flight, or the entire simulator for it to take effect?The one thing I can say is that with my old graphics card I didn't have this problem.

OK...screw it....it didn't work like I thought. I even deleted the cfg file and let FSX rebuild it from scratch, and the problem recurred.So here is what I have done most recently to my cfg file (today) to try and improve/modify performance:[bufferPools] (because before it was nonexistent)UsePools=1PoolSize=8000000RejectThreshold=98786 (as an alternative to using poo)[JOBSCHEDULER]AffinityMask=3 (dual core processor setting)[Display]WideViewAspect=True[Graphics]HighMemFix=1 (1024MB video card, previously nonexistent)SHADER_CACHE_VERSION=1[Main]DisablePreload=1I have played with enabling/disabling certain functions to find improvements, and I can't find anything that works. P.S. when I make changes to the cfg file, do I have to reload the flight, or the entire simulator for it to take effect?The one thing I can say is that with my old graphics card I didn't have this problem.

You have to reload the sim for the new cfg to take effect.Overclocking can lead to the same type of symptoms, have you thought of heat being a possible issue? If you think it could be a possibility try running with the side cover opened up, maybe even adding some airmovement via a portable fan.

The one thing I can say is that with my old graphics card I didn't have this problem.

I did not have this problem with my old card either. I do not believe that FSX has suddenlygone bad - it has to be the new components = the card and the driver.It only happens when my card is heavily stressed, like KSEA+PNW. When I go flying aroundthe default FSX world, no problem. I can recover by using alt-F-S (save the flight) and give it a name: say "t". This seems to reset some scenery parameters..Not sure I can find a pattern... for now, I am enjoying flying around less stressful scenerieswhere the new card is wonderful - great visuals and very fluid flight. But overstress it and itgoes ugly - picture attached

NEW UPDATE - Thanks to some found postings on YouTube videos, I learned that the NVidia 4XX series graphics cards (the GTS and GTX) have an issue with autogen scenery set to NORMAL AND HIGHER. Once I set the Autogen to low, the problem immediately went away. Jumped back and forth on the setting and this seems to be confirmed. This problem is also NOT apparent using Windows 7 using the same graphics cards (no notes on Vista). Seems to be driver/hardware issue on WinXP - though I can't really see why.Now I wish I got the 5 series. Alas, less autogen means I can improve on other things - though autogen was my favourite part. I'll keep my performance tweaks after all. Hope this takes us somewhere.

NEW UPDATE - Thanks to some found postings on YouTube videos, I learned that the NVidia 4XX series graphics cards (the GTS and GTX) have an issue with autogen scenery set to NORMAL AND HIGHER. Once I set the Autogen to low, the problem immediately went away. Jumped back and forth on the setting and this seems to be confirmed. This problem is also NOT apparent using Windows 7 using the same graphics cards (no notes on Vista). Seems to be driver/hardware issue on WinXP - though I can't really see why.Hope this takes us somewhere.

Interesting! I have Autogen set to normal and 99% of the time there is no incident.The problem only shows up when changing views (and only in Seattle thus far)

Missed the part that your on good ol XP, seems that is your problem, as this is not an issue on Vista/Win7 with the same cards.Seems NV is slow to support XP with the new serries cards.At least now you know.. :(