Out of curiosity, what screen resolutions are people using? I lose some textures from the VC of my 737NG when I change the resolution of the game from 1680x150 to 1280x1024. I regain them once I revert back to my LCD's normal resolution of 1680x1050.Mike Shannon

Out of curiosity, what screen resolutions are people using? I lose some textures from the VC of my 737NG when I change the resolution of the game from 1680x150 to 1280x1024. I regain them once I revert back to my LCD's normal resolution of 1680x1050.Mike Shannon

I still get this issue and never change my native monitor resolition of 1920x1200

Hello fellows...But through all the post and reactions i can not find a list of what to do step by step. Anybody? I can not found for example how to change exactly the soundquality. Regards peter

The sound fix is this:1. Control Panel > Sound > Speakers > Properties > Advanced > Default Format > 16 bit, 8000Hz (Telephone quality).2. Go back to the "Sound" page. Make the same setting change for all playback devices. Then go to the "Recording" page. Make the same setting change for all recording devices. (Note: this step is probably unnecessary: just changing the quality for the speakers should be enough: but I would try making the same change for all devices at first, "just in case").3. If your settings don't include the "Telephone quality" option, then the fix is less likely to work, but try choosing the lowest quality option. Let us know how you get on. HOWEVER: I should say that your symptoms don't look quite like the disappearing textures I have had on my PC, for which the sound fix is a cure.Tim

The sound fix is this:1. Control Panel > Sound > Speakers > Properties > Advanced > Default Format > 16 bit, 8000Hz (Telephone quality).2. Go back to the "Sound" page. Make the same setting change for all playback devices. Then go to the "Recording" page. Make the same setting change for all recording devices. (Note: this step is probably unnecessary: just changing the quality for the speakers should be enough: but I would try making the same change for all devices at first, "just in case").3. If your settings don't include the "Telephone quality" option, then the fix is less likely to work, but try choosing the lowest quality option. Let us know how you get on. HOWEVER: I should say that your symptoms don't look quite like the disappearing textures I have had on my PC, for which the sound fix is a cure.Tim

Hello,Here i'm again. I will start to make the same flight again, and test. What i changed:There was no sound quality called Telephone. So i did put it from 32Bits to 16bits 44100Hz CD Quality.For the other question: My screen resolution is: 1920x1200x32Peter

I too am still getting the texture loss, very much like the previous VC picture. I'm starting to think the MD-11, with all the FSX addons, is just too much of a memory hog with Win7. I found the trick of lowering the sound-quality effective against texture loss while using the 744X and the black-screens while pressing alt-enter. But for the life of me, I can't figure out why I still get texture loss and some alt-enter issues on the MD-11, and still an eventual CTD. I am pretty sure the lowering of the sound-quality is a placebo affect of unloading the PCI bus or perhaps allocated RAM, thereby giving the user just a little more room to spare.Andre Fokers mentioned in a post earlier this year, that the GPU/PCI-e buss can just become overloaded and start to crash the driver and eventuly the fsx.exe process. And, that they never really pin-pointed one exact event that routinely triggers the situation. I tried lowering my cloud-distance slider as well as lowering my REX clouds from 4096 to 1024 along with changing the Texture_Max_load variable in the fsx.cfg back to 1024 to no avail as well. I have tried all the diffrent combinations of Nvidia drivers 182.5x to 195.39 beta with different nHancer versions from 2.5.1 to 2.5.7 as well as no nHancer at all. Still the same.On my WinXP-x64 box, where I don't remember having these kinds of issues before upgrading to Windows7 a few months ago, I had as few as 24 processes running in the background. Still using NickN's guide, following the more recent Vista/Win7 meathodology, under Win7x64 I have no less than 44 processes running in the background.I'm really starting to think this is a user-adress-space problem and the MD-11 is just too much. By user-address-space, I mean the 2GB limit max for each process and I've already seen my FSX.exe process up around 2.1GB. Maybe it's a combination of how Win7 allocates more GPU buffer space than in WinXP and it's just sending me over the top. I have the exact same fully-loaded configuration I used on WinXP x64 and yet the miriad of texture problems presist. Much more noticable with the MD-11.What concerns me more are the memories of PSOLK and myself fighting the early days of the 32-bit OOM crashes near our destination airports shortly after Ultimate Terrain (UT) for FS9 came out and how we fought those issues for at least six months. Not even PMDG could tell us why, but it always happened with their planes, much more readily than models from other developers. In the end, it took the likes of Phil Taylor to reaffirm that we were indeed just running out of user-addressable space and a 64-bit tagged executable along with a 64-bit OS will allievate the issue. This is how Phil got word to tag the sp2 version of the fsx.exe with the large_address_aware flag so we didn't have to do it ourselves after every FS patch was released.I just wish PMDG would give us more customize options to help the user decide what we want to consume our precoius user-space with. I would prefer to be able to turn off 2D panels and failure-subsystems all toghether, as I don't usually use them. Maybe an option to use DXT3 textures instead of DXT5 or DDS textures.I just don't know right now, but I feel like I'm stuck between my growing affection for Windows 7 and my long-time success of WinXPx64, FSX, and PMDG. Who's going keep a presence on my spindles, I'm just not sure. I can't and won't go through the 32-bit OOM fiasco again, with everyone standing around scratching their heads. A few of us with heavy systems are already seeing this issue; more will surely follow and I don't know who's going to fix it. It won't be ACES studios this time my friends.FSX Server: FSXsp2, GEX, REX, UTX, SceneryTech, FSGenesis, NaviGraph, WoAI/MRAI (or UT2), FSUIPC, FSDreamTeam, FSPassengersX, PMDGFSX Client: FSUIPC Wideclient, FSX Simconnect-client, ActiveSky Advance (ASA), FS Flight Keeper, TopCat, Radar Contact

Well here i'm again.With bad news, for me.... :( I just started a flight set up. With PMDG MD11. And YES from the beginning now, textures were missing at the ovehead panel.Antoher attempt of first loading a default plain and then PMDG MD11, resulted in the same issue.So NO CURE FOR ME here in sound quality downgrading.Also checked my drivers and they are up to date!SORRY i hope we will have more solutions. For now, i'm going to reset my computer, a new fresh install. And will report further.Oh one thing, i happend in night time again. So in day time i had this issue only once.Ciao Peter

I just don't know right now, but I feel like I'm stuck between my growing affection for Windows 7 and my long-time success of WinXPx64, FSX, and PMDG. Who's going keep a presence on my spindles, I'm just not sure. I can't and won't go through the 32-bit OOM fiasco again, with everyone standing around scratching their heads. A few of us with heavy systems are already seeing this issue; more will surely follow and I don't know who's going to fix it. It won't be ACES studios this time my friends.

Very well said! I have been plagued by this problem since moving to Vista x64 and have not found a reliable fix. At this point, I have really lost the fun in my MD11 (and FSX altogether)... :( Uwe Bubeck

I was having the same problems and although the sound and the FSX compatibility fix had some effect it still happened, once in a while. Until i noticed that a window from the menu opened in full screen would stay in memory. Like, for instance when i opened display settings a flash of a black screen with a window i opened 15 min's ago still in it. This made me think the black screen problem had something to do with menu windows opened in full screen mode. I started to open menu items only in FSX windowed mode (had to get used to that first), and since then i don't have this black screen problem anymore.Maybe this is another solution to try. Don't know if it's all menu windows opened in full screen or maybe only the extended menu items like, FSUIPC, FsPassengers, PMDG etc. kind of windows. But safest, open all menu windows in FSX windowed mode.Best, Gerrit

Well gents, I've thought it over, I'm gonna suck it up, and I'm upgrading back to WinXP_x64. I can't go through this trial-and-error thing I did before with FS9 and 32-bit OOM's. I think it has to do with how GPU cache is mapped in physical and user-space RAM and I'm not playing this game.Now let see, where did I put the WinXP x64 CD.... :(

Well gents, I've thought it over, I'm gonna suck it up, and I'm upgrading back to WinXP_x64. I can't go through this trial-and-error thing I did before with FS9 and 32-bit OOM's. I think it has to do with how GPU cache is mapped in physical and user-space RAM and I'm not playing this game.Now let see, where did I put the WinXP x64 CD.... :(

Yeah, I went back to XP-64 about 6 months ago after having the black screen issue with Vista 64 and the Windows 7 RC1. Haven't regretted the decision at all. Have flown many trans atlantic and pacific flights in both MD-11 and 747 since with no issues at all.

Hi All,Lurker here... :( I just wanted to add that I too have witnessed transparent textures at dusk in my just recently purchased 400X... I have no add-on scenery and did not have ASA running; I was actually going through the engine start up tutorial and had been sitting on the ground for a while at Boeing Field with my time divided between reading and cockpit work.I started the engines and went to spot view to check out my new bird all lit up and running... Of course I was quite surprised and dismayed to find that I was looking at nothing but seats and wings minus the engines. All other FSX scenery textures appeared fine. I never saw the black screen issue though...I restarted FSX and went through the tutorial a bit quicker this time and never got the transparent texture issue, albeit this was only my second (attempt at a) flight. I'm sure that if I was sitting at the tarmac as long as I had the first time that I would've lost my textures again.I have seen this similar issue pop up mid-flight in the CaptainSim 757; more specifically, their USAir repaint.I'll try the sound fix here and see what happens... Thanks all for working through this! I hope that we can crank our sound acceleration back up one day!My System:Windows 7 Ultimate x64Intel Q9550 2.83 GHZ Quad CoreGigabyte GA-EP45-UD3P v 1.14 GB Corsair XMS 800MhzNVidia GeForce GTX260 Black Edition2 x 160GB SATA Seagate Barracuda HDD's (system on C: and FSX on D:)Robert-

Everyone missed a very important post...Someone reported the problem gone when they uninstalled the HDMI driver. I have yet to buy a PMDG product though (hopefully this winter @ BestBuy!) so i can't confirm.http://forums1.avsim.net/index.php?s=&...t&p=1660642Make sure to disable and uninstall any ATi or Nvidia "High Definition Audio Device" in the device manager . Also make sure you uninstall through forceware or catalyst if possible. If you send audio through your HDMI cable your probably out of luck unless you have/buy a DTS, coaxial, or analag connector to your TV/sound system.John

the only audio device I have is the Creative sound card

That thing of audio with HDMI driver stuff i will check out later.But i was testing some things and switched to DirectX 10 preview. And noticed it was working all OK!!No problems....So who is running in DirectX 10 preview and who is not? Mayby it is nothing but for now no problems here....Peter

Hello,Here i'm again. I will start to make the same flight again, and test. What i changed:There was no sound quality called Telephone. So i did put it from 32Bits to 16bits 44100Hz CD Quality.For the other question: My screen resolution is: 1920x1200x32Peter

PeterUnfortunately, your lowest available sound quality setting, is much too high for this fix to work. Some people have had success with 11,000Hz quality rather than 8,000Hz, but 44,100Hz is not going to work.If you hunt around you might be able to find different drivers to run your sound card, which might let you choose a lower quality setting. Tim