Gents-This is caused when the machine is not able to meet resource demands. It is most frequently found in areas where there is significant scenery data being crunched from things such as UTX, FSGEnesis, and a complex airport scenery. We've seen this a number of times- and the solution is pretty straight forward: Reduce the sound quality settings in Windows.We chased this without any ideas for quite some time- and discovered that it happens with many different complex add-ons.

Gents-This is caused when the machine is not able to meet resource demands. It is most frequently found in areas where there is significant scenery data being crunched from things such as UTX, FSGEnesis, and a complex airport scenery. We've seen this a number of times- and the solution is pretty straight forward: Reduce the sound quality settings in Windows.We chased this without any ideas for quite some time- and discovered that it happens with many different complex add-ons.

Hmmm I am not convinced and - please dont be offended cause I dont mean to offend - I furthermore think your answer is biased. Here is why:1. I had this exact problem with my 747x, and was told that it was lack of memory and physical resources on my part, even though I explained I had successfully played with the same configuration for months. My pmdg 747 had worked wonderfully for some time before the "incident". The incident that time happened when I tried to install Flight!s fokker 100 addon. My pmdgoptions.dll somehow got corrupted and my whole fsx install got unstable. The problem persisted through several reinstallations of FSX, accel and pmdg 747. It turned out that I somehow ended up with two installations of FSX during the reinstallation, and that made the "invisible" 747 problem persist through reinstallation. When I cleaned both versions completely off my PC the problem was solved. People said the problem was hardware related from the beginning, though. I found the solution to my problem on my own - a detectives work that went on for a couple of days. A funny sidenote is that the MD11 was actually untouched by this error. Go figure! 2. I flew the 747 for some time before wanting to install the md11 again. I installed it again - pretty straight forward. Unzipped the installation file, and validated. I noticed right from the "preview window" of the aircraft (the window where you press "fly now!" that something was wrong; the jet engines werent rendered properly, although the body itself looked quite alright. Going into the sim the aircraft looked like a mess, however - exactly like the 747 problem I had with the skin of the plane not rendering at all. Now again people say that the problem is hardware related - that I lack physical resources on my pc to render the airplane.OK - then why is my pmdg747 just fine and dandy? Why am I suddenly now in a situation that seems to reverse my problem: Now its my MD11 that isnt rendering properly while my 747 is, and my first problem was initially that my 747 didnt render but my md11 did..?

For as far as I know, I have seen exactly this problem with other people on these forums, and what robert said worked always: reduce the sound settings of windows (although I have no idea where you should do that, sorry...) and all should be fine again. It worked for those other people, so you might want to give it a try. You never know, right?

Gents-This is caused when the machine is not able to meet resource demands. It is most frequently found in areas where there is significant scenery data being crunched from things such as UTX, FSGEnesis, and a complex airport scenery. We've seen this a number of times- and the solution is pretty straight forward: Reduce the sound quality settings in Windows.We chased this without any ideas for quite some time- and discovered that it happens with many different complex add-ons.

I can't say as I agree at the moment. Although lowering the sound acceleration slider does allow me enough resources to depart a complex airport such as FSDreamTeam's KLAS or ImagineSim's Heartsfield Atlanta without catastauphic deteriorization of textures and screens, the problem eventualy rears its ugly head near the end of trans-Atlantic flights (hours later).

I can't say as I agree at the moment. Although lowering the sound acceleration slider does allow me enough resources to depart a complex airport such as FSDreamTeam's KLAS or ImagineSim's Heartsfield Atlanta without catastauphic deteriorization of textures and screens, the problem eventualy rears its ugly head near the end of trans-Atlantic flights (hours later); only with the MD-11; not the 744X, not the JS41, not the LvLD767, etc. I'm sorry, but reducing sound acceleration just doesn't not sound like a very scientific solution in the long run, but more along the lines of a band-aid to other issues. I agree in that it is resources related, what's causing it is debateable.

I have read most of the material on the missing textures for 747 and md11. I dont think my problem is quite the same as anybody elses, because what seems to be common for the others is that this problem occours AFTER A WHILE. My problem starts from the very start; first when selecting the aircraft the engines wont render, and then ingame (from the very start) my entire aircraft is hardly rendering at all. I have of course tried to set machine accel of the sound to minimum, and disabling sound altogether - without results. I think my problem is related to registry and installation more than to memory and other resource problems. Problem for me is - I still dont know how to fix it. I might spend hours completely reinstalling everything and end up with the same problem... So if I cant get any help for this then I might just have to live without the md11 :( I wish I could get a refund though.

I have read most of the material on the missing textures for 747 and md11. I dont think my problem is quite the same as anybody elses, because what seems to be common for the others is that this problem occours AFTER A WHILE. My problem starts from the very start; first when selecting the aircraft the engines wont render, and then ingame (from the very start) my entire aircraft is hardly rendering at all. I have of course tried to set machine accel of the sound to minimum, and disabling sound altogether - without results. I think my problem is related to registry and installation more than to memory and other resource problems. Problem for me is - I still dont know how to fix it. I might spend hours completely reinstalling everything and end up with the same problem... So if I cant get any help for this then I might just have to live without the md11 :( I wish I could get a refund though.

Way off idea, but have you run the registry fix?

Way off idea, but have you run the registry fix?

What is the registry fix? :)

A simple free tool from Flight1, registry entries for MSFS are often corrupted by add-ons. This tool fixes those, and is found at the Flight1 web site under utilities I think.

It didnt help :( And now the problem has escalated:I bought and downloaded LevelD 767 today, and the invisbug is there from the start as well... I think this might have something to do with my registry not being clean. What do you guys think? My pmdg 747 is fine - but now it is the only addon that IS fine... :( Dont get me wrong - I love my 747 very much, but it would be nice to have a choice... How do I check my registry? Specifically, I belive i might have references to an old installation on my E: drive that might make this problem. My fsx folder is currently on my C: drive.

If you are not familiar with the NT (XP, Vista, W7) registry, I don't recommend going there.You may have success if you uninstall all addons and the MSFS from the control panel. Then after a reboot try installing one thing at a time and testing to see if the invisbug is gone.Otherwise, someone needs to use the regedit utility to go into the registry and look for the errors. Mind you, I can do this without being an expert but I am very careful.

Gah I guess I'll be reinstalling the whole thing this weekend :( Thanks for your advice and support, though, Dan! Much appreciated :)

Gah I guess I'll be reinstalling the whole thing this weekend :( Thanks for your advice and support, though, Dan! Much appreciated :)

I heard from PMDG that the order of installation doesn't matter for the MD11 and 744.

Ok finally I have very very happy news:My addons are working ok again! Woot! I finally got hold of a registry cleaner, and did a complete uninstall of fsx and absoultely all addons related to it. Rebooted and did reg-cleaner, and rebooted again, and installed fsx, accel, and then pmdg 747. It was alright. Installed md11 - and it was alright too! OMG! :D Then I installed Level D 767, and it too was fine! I nearly fell out of my chair..! So I installed Fsuipc4, and it still was alright. Then FSinn, and still fine. I've had a few flights tonight, and just smiled as I came in for landing at ENGM in rain and snow. Quite nice hand landing with my MD11 if I might say so myself.So thanks again for all your help and patience, people! And the trick that finally did it was: Registry cleaning.

This has been an issue for a while, I have seen it happen with my PMDG and LDS aircraft (though oddly not with my CS 757 and 767).Frankly, any "solution" that includes a complete reinstall is not realistic given the number of add-ons many of us run.With respect to this sound setting adjustment, what exactly would that entail within FSX?Thanx.

This has been an issue for a while, I have seen it happen with my PMDG and LDS aircraft (though oddly not with my CS 757 and 767).Frankly, any "solution" that includes a complete reinstall is not realistic given the number of add-ons many of us run.With respect to this sound setting adjustment, what exactly would that entail within FSX?Thanx.

I think it is important to notice the little, but distinct, difference in the problem that has been discribed here for a long time that has to do with aircraft stopping to render properly a ) AFTER A WHILE, and my problem which was aircraft not rendering properly b ) AT ALL (from the very start up of Flightsim X). If you experience problem A then chances are that you are seeing the symptoms of memory shortage, and may find the lowering of sound accel to be the solution for you. If you are suffering from B then none of the solutions that applies to A will work, but a complete reinstall (make sure you uninstall properly like described in this thread) and registry cleaning will solve it. So problem B is connected to the registry, while A probably is not. The interesting thing is of course that the symptoms look very much alike...