Tim (TFM), if your out there, perhaps you can give this a whirl and also let us know how it works for you. If memory serves me right, you are still running at 800hz.

If you go back in this thread a bit, Tim did try Alchemy, and like me it seemed to cure the texture issues, but introduced sound problems. Start from the following post for details: http://forums1.avsim.net/index.php?showtop...p;#entry1585382A few posts down from that one, he stated he lost the callouts using Alchemy. I didn't have that issue, but there were other sound glitches as I mentioned above. When there were problems, there was a huge error log in FSX directory indicating sound buffers could not be created. I tried tweaking the Alchemy settings, but could never get rid of the buffer errors. Given time, it might be possible to find a combination of Alchemy parameters that work in all situations. It seems like there is no single solution. Either we have graphics with sound problems, or sound with graphics problems. XP64 still seems to be the best of both worlds, but the OS is getting long it the tooth, and I would like to move up to Windows 7 again at some point.

If you go back in this thread a bit, Tim did try Alchemy, and like me it seemed to cure the texture issues, but introduced sound problems. Start from the following post for details: http://forums1.avsim.net/index.php?showtop...p;#entry1585382A few posts down from that one, he stated he lost the callouts using Alchemy. I didn't have that issue, but there were other sound glitches as I mentioned above. When there were problems, there was a huge error log in FSX directory indicating sound buffers could not be created. I tried tweaking the Alchemy settings, but could never get rid of the buffer errors. Given time, it might be possible to find a combination of Alchemy parameters that work in all situations. It seems like there is no single solution. Either we have graphics with sound problems, or sound with graphics problems. XP64 still seems to be the best of both worlds, but the OS is getting long it the tooth, and I would like to move up to Windows 7 again at some point.

I see,,, Thanks for the update Kyle I appear to have forgotten about that or missed it (I'm getting old fast ;-).It is nice though that we have knowledgable people will to test different things and help research this with different configs. Just wish there were a better solution than XP64. I have Win7 in my sites but no rush since I'll be waiting to see what nVidia has in store with their next line of DX11 cards. Just out of curiosity Kyle... Do you overclock? We haven't had much feedback on that being a possible contributer to this issue. We've had lots of mention of it and asked in several threads if anyone had this issue that DID NOT over clock but looking thru the trail don't see anyone with the issue that doesn't.

Just out of curiosity Kyle... Do you overclock? We haven't had much feedback on that being a possible contributer to this issue. We've had lots of mention of it and asked in several threads if anyone had this issue that DID NOT over clock but looking thru the trail don't see anyone with the issue that doesn't.

As a matter of fact, I am overclocking--getting 4GHz out of my 920 on water (temps never exceed 60C). You would probably be hard pressed to find anyone with an I7 not overclcoking. I never tried running stock, since the overclock has been so stable, and all works well in XP64--but Vista and Win 7 probably put more strain on the system. I am dual booting XP and 7, but don't have FSX installed under 7 anymore. If I get a chance, I may try reinstalling under Windows 7 and running at stock clocks, although, I probably won't be pleased wih the performance.

As a matter of fact, I am overclocking--getting 4GHz out of my 920 on water (temps never exceed 60C). You would probably be hard pressed to find anyone with an I7 not overclcoking. I never tried running stock, since the overclock has been so stable, and all works well in XP64--but Vista and Win 7 probably put more strain on the system. I am dual booting XP and 7, but don't have FSX installed under 7 anymore. If I get a chance, I may try reinstalling under Windows 7 and running at stock clocks, although, I probably won't be pleased wih the performance.

Yep, i7 920 here, and O/C to 3.2 (3.3 Turbo) on air. Mid 70's C tops. Doesn't appear to be an O/C issue, but...Ah yes, and sound cards. I'm also running Vista 64 and SB XFi and have tried with and without the card installed, using onboard (DFI LanParty x58 Marvel chip) sound. No difference, still the occasional freeze. Lastly, as many have hinted...I actually think I do have an Alt+Enter 'limit' per flight! Now, I might be all wet (as they say) but I swear if I am full-screen for an 8 hour flight and I NEVER alt-enter or go to menu - I will in turn NEVER have an issue. It's true. But, if I get "Alt-Enter happy", particulalry on approach after a longhaul, it's adios - instant freeze. Mighty strange, but it is repeatable behaviour: No menu or alt-enter, no problems. I have not a clue as to why that would be, only that it works.Cheers!(My setup: homebuilt Core i7-920 OC to 3.2Ghz, 6GB RAM, DFI Lan Party Jr. microATX motherboard, Vista Ultimate 64, WD Black FALS 1TB HDD, BFI GTS 250 O/C 1GB video, recycled SB XFi Extreme Music from old computer, recycled ViewSonic 22" 1680x1050 LCD, recycled gateway wireless keyboard from yet another old computer, recycled Logitech wireless mouse (from MX620 pair?), old Compaq case from previous computer sans bezel...)

Hi Patrick, The OC question comes up, because in this post and many others the question has been asked if there were anyone experiening this issue with a non-OC'd system, and personally I never seen one reply saying they weren't.The alt+Tab issue and many others tied to long flights is strange. I can alt+tab all day. I usually always have photoshop running and firefox,,, some folders etc... but like you said when coming to the point of T/D and approach I don't touch it or also get lock ups.To me it seems like fsx and windows in general doesn't know how to use ram, and has relocate blindness. I have 12 gb of DDR3 and never see above 5, not matter what I run and how many apps. It seems like when FS loads, certain data is put into memory, then squeezed out or lost over time. Like a memory leak. I have never seen it with other games. I actually had F.E.A.R paused a while back for over a week and was doing lots of photoshop and MS office, even some web work and when I unpaused it, there was a stutter for a few seconds but it picked back up like nothing happened and no time was lost.

Hi Patrick, The OC question comes up, because in this post and many others the question has been asked if there were anyone experiening this issue with a non-OC'd system, and personally I never seen one reply saying they weren't.The alt+Tab issue and many others tied to long flights is strange. I can alt+tab all day. I usually always have photoshop running and firefox,,, some folders etc... but like you said when coming to the point of T/D and approach I don't touch it or also get lock ups.To me it seems like fsx and windows in general doesn't know how to use ram, and has relocate blindness. I have 12 gb of DDR3 and never see above 5, not matter what I run and how many apps. It seems like when FS loads, certain data is put into memory, then squeezed out or lost over time. Like a memory leak. I have never seen it with other games. I actually had F.E.A.R paused a while back for over a week and was doing lots of photoshop and MS office, even some web work and when I unpaused it, there was a stutter for a few seconds but it picked back up like nothing happened and no time was lost.

Thanks Turbine - Yeah, that about sums up the observed behaviour - and I quite agree on the RAM-angle. I have heard anecdotally that Win 7 handles RAM better - and some claim these problems have disappeared or have been minimized. Personally, I think I'm going to give that a shot. What the heck - a 'clean' install usually has everything working better, with more

I have tried every tweak to fix this, I finally bit the bullet and went from Vista 64 to XP 64 and I wish I did this sooner, I have tried and tried to break some textures in FSX with the leveld and pmdg md11 and I just can't. Not at dawn or dusk I can alt tab, alt enter, where as before if I even looked at it the wrong way the textures would disappear. And not to mention that my pc as a whole is so much quicker with XP 64 my little Q6600 @ 2.70 is just blazing, no real improvement in fsx still got it locked at 30 fps and its smooth, but not having all the texture problems is worth it. knock on wood

I have been using this option for the past couple of days: FSX icon - check DISABLE VISUAL THEMES and DISABLE DESKTOP COMPOSITION, WinXP Compatibility mode.Just last night I was just sitting at a terminal and I have to Alt-Enter to look something up in the PDF manual I go back to full screen and I am missing a cockpit and the top half of the screen is flickering. I have to exit and shut down the sim.This current set back has pretty much nixed my idea about putting in a sound card - as said before this will not help any. I went ahead and lowered my sound quality to 8000 hz.I am now set on hooking up a smaller 2nd monitor to display a map and the pdf manual so I will not have to Alt-Enter/Alt-Tab anymore. One question: With a second monitor will I be able to still use Full Screen with FSX or will I have to use FSX in window mode?

I ve been following this thread almost a year now - since I did the upgrade to a better video card (GTX280) and sound card and the "Black Screen/Corrupted Grapics" came home....Since then I changed:* the OS from Vista x64 to Windows 7x64* the Motherboard to the latest state-of-the-art masterpiece by Gigabyte* the CPU to i7* the cooling (to liquid)* the HDD to SSD* the nVidia driver* the Alchemy* the memory to DDR3 + adding additional 4 GBThe result was - same....Sadly I realised that no matter what I change in the hardware and software outside FSX, after I load the FSX with all the add-ons that worth to be there the Black screens show up. There is a little bugger hidden in there, so little noone can see it. One solution was mentioned above - I just learned not to go in the menus anymore. Just print all the charts needed for the route, check all the weather before flight is loaded, go in and fly.... and hope the antivirus will not splash the "update complete" window in the middle of the take off run and ruin the day.I am not satisfied with that. I will not give up testing. Until the real cause is tracked down and taken care of.

One question: With a second monitor will I be able to still use Full Screen with FSX or will I have to use FSX in window mode?

Hi David, Answer is sadly to say, no on full screen.This is because MS decided to make radical changes to the directX window in FSX that no longer allows stand-alone EXE files to float on top because it takes control of the desktop (i.e both monitors on a twin monitor system get blacked out, under FS2004 they did not). You can of course use that second screen to drag things of the FSX environment to the second or third screens, but only things like panels, new windows from FSX etc... I normally run in windowed mode for this reason.

Question for both of you since you may have missed the question earlier.Are you both Overclocking your CPU?

Hi David,Answer is sadly to say, no on full screen.This is because MS decided to make radical changes to the directX window in FSX that no longer allows stand-alone EXE files to float on top because it takes control of the desktop (i.e both monitors on a twin monitor system get blacked out, under FS2004 they did not). You can of course use that second screen to drag things of the FSX environment to the second or third screens, but only things like panels, new windows from FSX etc... I normally run in windowed mode for this reason.

Does the Super 80 Pro have a GPS that I can drag over to that second monitor?Also, I guess I will go print out the manual.

Does the Super 80 Pro have a GPS that I can drag over to that second monitor?

I have no idea what the Super 80 Pro has, but if it has a gps, then yes. As I mentioned already anything or any window in FSX, such as a GPS can be dragged over. If this is a default plane that your talking about, I never used it and am not able to check at the moment.I would also imagine that it does have something, and of course can always be changed to a more realistic gauge/gps with some simple editing.

I use two primary aircraft: PMDG 747 and the Super 80 Pro and the texture issues happen with both of these...I know this is becoming off topic, but it's a work around for this major issue -How about this:http://fswidgets.com/shop/product_info.php...;products_id=44

I tried the following to resolve the black screen problem:RIGHT CLICK the FSX icon PROPERTIES then the COMPATIBILITY tab under SETTINGS select DISABLE VISUAL THEMES and DISABLE DESKTOP COMPOSITION then click apply.The above solution seems to have worked so far with my black screens - I do not know what the solution does to FSX negatively though.Initially I did try lowering the sound quality to 8000 Hz, but I did notice a drop in sound quality and wanted to try something different. If for some reason I start getting the black screens again I will settle for a drop in sound quality - I hope it does not come to that.I'm running the following:OS: Vista x64MB: ASUS with Onboard Sound - using the SoundMax driver of course.GPU: Nvidia GeForce 260 512MBFSX Gold EditionAddons: GEX, UTX, REX2, PMDG 747, Super 80 Pro, UT2, Air HaulerJust to recap the various solutions:1. Reduce sound settings to 8000 Hz.2. FSX icon - check DISABLE VISUAL THEMES and DISABLE DESKTOP COMPOSITION 3. Use WinXP x64 OS4. Adjust bufferpools anywhere from 500000 to 300000.5. Possibly disable onboard sound and install a new sound card - worked for one forum member, but has not worked for others using extensive testing.6. Adjust RAM settings/speed.7. Use DX10 Preview Mode.

But, DX10 is not supported in XP (of any flavor) - only Vista and up support DX10 (w/ of, course, a DX10 capable graphics card). I mean, I can quote the ACES developers on this one: http://blogs.msdn.com/ptaylor/archive/2007...isnt-in-xp.aspx Which is an article from none other than Phil Taylor (project leader at ACES for sp1, sp2 and Acceleration) titled - "Why DX10 wasnt created on XP and why it isnt in XP".Soooo...how are y'all pulling that off, having both XP and DX10 Preview?Thanks