Hi,Processors only affect frame rate. Faster is better.A "real" card that supports at least DX9 is required to have any chance of half-decent performance if nothing else.Vista x86 or Vista x64 - no difference. If it is going to run out of memory, it will do so.FSX is a 32-bit app - the same restrictions apply to it whether it is running on a 64-bit OS or a 32-bit OS.Now we've got all that out of the way...Remember FSX is less than a great piece of software. It is buggy, glitchy and is far from well-written. It is the ultimate piece of 3rd generation (at least) bloatware.If like me, you run other graphics and system intensive programs, you will soon know if your system is not up to scratch. It won't be just FSX showing glitches - it will be everything you run on the system. If you do not see glitches for hours at a time in other games, you can be 99% confident your rig is fine.I highly recommend you ditch Anti-virus, Anti-Spyware, Anti-Malware, Anti-Phishing, Anti-Bugs, Memory Compactor, Memory Optimizer, Windows Dresser, Windows Curtains, Windows Decorator Plus, etc... and get back to a basic operating system. These apps are far from optimal, eat CPU time, eat memory, and generally kill your computer.Once you've cleansed your computer of JunkWare, try disabling everything you run inside of FSX, and get back to the basics of troubleshooting.If you are finding with EVERYTHING non-standard disabled in FSX, and just the plain vanilla FSX install plus the aircraft are still glitching, it is likely the aircraft (or FSX, or both). At that point you can start pulling your computer to pieces to look elsewhere (drivers, hardware, etc).If in the basic config the aircraft is fine, you must test each individual add-on seperately, looking for a hint of a problem. If you don't do this, you'll never find the cause.Eventually you will do something to provoke the problem. Now you can start looking at what you added, and start trying different combinations of only those things you installed.One point to note is that if you run high-res clouds in the sim, these will all be eating away at the memory space of FSX (not the OS). FSX only has 2 Gb to play with (forgetting the LARGEMEMORYAWARE flag, as it appears people still run FSX SP1). There may be moments where FSX needs to do something, tries to allocate more memory than is available, and runs out. Usually this is accompanied by OOME.If the case is that you run out of kernel memory - this is ugly. The system may not crash immediately, but will start glitching. It will eventually lead to a crash.If something in FSX is leaking memory, or FSX itself is leaking memory, this will not register except as an apparent creep in memory usage when flying over, say, water for 6 hours. The sim isn't doing much, so memory usage shouldn't increase much, if at all. If it increases 500 Mb, you've got a problem.DX9 vs. DX10. If as above you're getting a lot of crashes under DX9, but not under DX10, look at your graphics card drivers. FSX is stable in DX9 mode, as are most DX10 capable graphics cards, so if you have issues, look at your drivers first.I personally run FSX on DX9 hardware, all day, without problems. It ran fine (albeit slowly - this is OS related, not memory) on XP, and runs fine under Vista 64-bit. Windows 7 32-bit - wow. Speechless.Finally - don't upgrade your hardware unless performance is unacceptable for you. I run FSX on an E6700 (dual core, stock speeds), so whoever was saying the QX6600 is poor, is frankly talking rubbish. I get a cool 28 FPS on the ground at Heathrow 2008, and triple digits above 4000 ft AGL. 200+ FPS is not uncommon in the cruise with the MD-11.Sorry for this post going on a bit, but I strongly suggest looking at all the other software and add-ons you're running before you go and splash out on hardware. Even new high-end rigs can struggle to run FSX in real-world testing, so you could likely be throwing money at nothing (unless you have other uses that could benefit from such a rig besides FSX).If you must change your operating system, wait for Windows 7.Best regards,Robin.

Guys, I think everything we can possibly say on this issue has been said. It's NOT our code that's doing it, it's something with FSX itself - people have seen this with LDS and several other addons as well if I recall from an earlier thread.Vin (the guy who made the models here) has a Core i7 920/6GB/GTX285 machine running Vista 64 just like some of you in this thread and he has never seen this occur. If people with with identical hardware to the developer's machine are seeing different things, then clearly this isn't something we can effectively troubleshoot.Did you guys try the sound acceleration thing that was mentioned in a different thread as a potential fix for this?

hi ahve u tried uninstalling fsx sp 2 than reinstalling since i had ttoubles with missing textures but not with the pmdg 747 though worth a try solved my prob

same issue here with the starboard side disappearing.core2 3.04gb ramvista x64nvidia 285 video cardfsx w sp2no dx10 enabledlatest nvidia driversnhancer tweaks from nicks suggestionI have noticed removing the bufferpools tweak helps, but it still happens when accessing the menus, and sometimes switching views. either its the virtual cockpit that disappears or the external textures. So annoyingI have uninstalled and reinstalled and run no other addon airplanes but still get this issue. My last try is to remove all pmdg airplanes, and only install the 747x not the md-11 after.

can anyone help! So far I miracuously completed one flight, KORD to PHNL. But since then I can't get through half a flight without the virtual cockpit or outside disappearing. I have made sure never to use the pause menu but still it corrupts itself! Please help!

you know that makes me think of something. when it happens fsx is changing times. so its going from day to dusk, or night... so yes maybe active sky is doing it?? I removed all pmdg airplanes, and only installed the latest 747X installer. Time to go post on active skys board

Hi All,This is not directly caused by ASA. However, running FSX, complex add-ons including ASA, can use up system resources and when this happens we know that one symptom is a loss of textures.Thanks,

I getting that kind of issue with the Wilco airbus, I don't own any PMDG at the moment, waiting for the J-41...I just upgraded my graphic card from a GTX260 to a GTX285 and cleaned drivers and reinstalled the 190. Problem still occurs but very randomly... I stopped flying wilco planes anyway. I just hope this will not happen with the J41... If it does, I'll do a complete reinstall of my PC and FSX... When I think of it, the problem occured when going from day to dusk with Rex 2.0 weather engine... Thomas Eklund

Someone on a dutch FS forum noticed that the problems went away after he decided not to use Active Sky anymore.

When Active Sky is installed it asks to modify panel.cfg's to add the XGauge. I had the installer APPEND Xgauge to the PMDG panel. Then I was having problems with my aircraft turning transparent.I reverted to the original panel.cfg that DOES NOT INCLUDE Xgauge. My tranparency problems disappeared. So I'm thinking it has something to do with X Gauge. I also have the problem with the Wilco V1 Airbuses (not V2's) but I blame the V1's cruddiness in general for that particular problem.

I will uninstall nhancer and reinstall my video drivers, but then I would have to check use anti aliasing in game which eats up system resources and does not work as well as forcing nhancer settings

Disable the DX10 preview option. Best regards, Robin.

Robin, as an aside, could you please tell me how to enable DX10 Preview ? I seem to be somewhere in the dark with respect to the hardware aspect !! :( Regards,GodfreyG :(

Robin, as an aside, could you please tell me how to enable DX10 Preview ? I seem to be somewhere in the dark with respect to the hardware aspect !! :( Regards,GodfreyG :(

There is a simple test. I learned hard way. I was having many transparent plane problem for a long time. I have a high-end PC with 8GBRAM.1- IF you have Navdia GTX high-end graphic card.These cards designed based on DX:10 Mode2- IF you have Vista 32 or 64, they are also designed based on DX:10 mode3- If you fly with FSX DX:9 mode, then you will have a " weak link" in the system (That is my opinion) GTX DX10, GTX Driver 190.38 (It is a DX10 and I have perfect experience with this driver) Vista DX10 and bottle neck occurs with FSX DX9 mode ,with PCs experiencing"Transparent Plane" problems.Simple test with FSX DX10 Review Mode:Go fly the same flight route with same weather/daytime that you experienced "Transparent Plane" with FSX DX:10 review mode. 1-Make sure in FSX Aircraft Settings page check "Preview Direct X102-Check "Anisotropic Filtering"3-Check "Anti-Aliasing"I solved my horrible "Transparent Airplane" and many related other problems just switching to FSX DX10 review mode. This is a just fact finding test. Lets hope it will solve your problems also.Regars,Sanal :( lThe only way to find if FSX

There is a simple test. I learned hard way. I was having many transparent plane problem for a long time. I have a high-end PC with 8GBRAM.1- IF you have Navdia GTX high-end graphic card.These cards designed based on DX:10 Mode2- IF you have Vista 32 or 64, they are also designed based on DX:10 mode3- If you fly with FSX DX:9 mode, then you will have a " weak link" in the system (That is my opinion) GTX DX10, GTX Driver 190.38 (It is a DX10 and I have perfect experience with this driver) Vista DX10 and bottle neck occurs with FSX DX9 mode ,with PCs experiencing"Transparent Plane" problems.Simple test with FSX DX10 Review Mode:Go fly the same flight route with same weather/daytime that you experienced "Transparent Plane" with FSX DX:10 review mode. 1-Make sure in FSX Aircraft Settings page check "Preview Direct X102-Check "Anisotropic Filtering"3-Check "Anti-Aliasing"I solved my horrible "Transparent Airplane" and many related other problems just switching to FSX DX10 review mode. This is a just fact finding test. Lets hope it will solve your problems also.Regars,Sanal :( lThe only way to find if FSX

High-end machine, GTX280, Vista 64-bit. I was having a major problem trying to start a 747 flight at night. As soon as I switched on the lights, the plane lost its skin. This happened three times. Then I came across this thread, moved to DX10 review mode, and the problem went away, on this occasion, hopefully for ever. Completed a 12-hour night and day flight from London to Singapore, no problems. So I'm inclined to support the theory that running DX9 with DX10-capable hardware and software is a bad idea.

I don't use any bufferpool setting and the problem occurs... I don't want to use DX10 preview... The flickering stuff is really annoying....

I get a transparent cockpit on night flights only in the MD11.20 min or so into every night flight my cockpit starts going transparent. It spreads across more of the pit as I change views until I can see to the ground except for parts of the panel. very annoying as it makes any night flight unuseable more than 20 min (a bit short for a long haul A/C).Thought it might be lacking hardware (was running Q9550 @ 3.6, 8GB Dominator, GTX260 Core 216, Vista 64 and DX9)Switched to ([email protected], 6GB Dominator, (2) GTX275's, W7 64Bit and DX9) same issues return.Can post pics if you like.John Skibo