this is what I

Is that how it looks in FSX for you?I've seen that result in pictures I have captured, but it's not what it looked like in game, and I've never seen that happen in game. Whatever I was using just didn't capture all the surfaces into the picture; but at the moment I captured it, all the surfaces were there in game (I forget if I was using Snapshooter or the default picture capture method when I got pictures like that).I did have an issue where, when I turned all the sliders all the way up and had full traffic turned on at KBOS: many of the aircraft had translucent bodies, or were missing altogether (but you could see their nav and strobe lights). But it turned out I had misspelled the texture directory name for one of my default aircraft paints I had added. When I fixed that, the problem seemed to go away. But it wasn't a rigorous test. The problem seemed to crop up over time; as, initially, all the aircraft as they were drawn looked fine. But as I drove further and further around in the sim (I was testing my replacement of the default ai paints with real world airlines), I noticed more and more aircraft were translucent. I have a rather meager system (Dell D810 Lattitude, 1 Gig mem (at the time), 1.86 GHz Pentium M, 64 MB ATI Mobility X300), so it could also be memory related, that FS dynamically decides what to draw based on available memory (rather than running out of it and crashing). Or it could be a combination of the two issues (lack of mem and the missing texture directory name).Since then, I fixed the texture directory name, and I later added another GB of memory to the system (2GB now), and turned off the use of the graphic card's shaders, and I haven't seen that issue since.It looks to me like a driver or memory issue.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

I believe that this is a shader problem. Have you applied any shader tweaks? If so, remove them; if not, then suspect your video card. I know nothing about your card or what shader support it provides. R-

I agree with Thomas, it looks like a graphics driver or setting problem. I've seen it on my machine when I had an older graphics card. Have you tried reducing the sliders, or over clocking?I think the textures are not refreshing fast enough. Does the image ever fill in after some time?Ron

I

The first thing I would do is try to obtain older drivers for the video card and see if things improve.It sounds like FSX is having a tough time finding space to load the textures, either because the drivers are bad, or you might also be having a problem with memory chips somewhere.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

I haven

Oh, and as noted above, it could be a very bad implementation of the 2.0 shaders. Check out this tweak to turn off the usage of the advanced shaders (but still use the older shader models).http://forums.avsim.net/dcboard.php?az=sho...64015&mode=fullIn the past, the devices.cfg file was only read when building the FS9.cfg file. So I'm not really sure how to force FSX to read this file once you've modified it, nor am I sure how to tell if the tweak actually worked (except turning on 2.x water features and see if you notice a change. So, before you try it, take an image of water with 2.x features activated. Then after applying it, see if you notice a change).Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

Or maybe you got the Mermaid Man and Barnacle Boy version of FSX. Check the box, it'll tell you there. :)Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

>this is what I

lololo ... I don

and today I

What did you do after you added your adapter to Display.cfg?In the past, display.cfg was only read while building a new fs?.cfg file. Perhaps you might try backing up your fsx.cfg file and then deleting it, thereby forcing fsx to rebuild it when you start the program. Did you try that?I'm sorry for all your frustration here.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

A couple of other things to check. You said that the demo version displayed the aircraft OK. How much disk freespace do you have left, and did you defrag the drive after installing? You may get enough space by deleting the demo version, or saving some zip files on dvd or external drive. I think 25 to 30% freespace is a minimum target. You could also try using a utility like FSautostart to temporarily halt background processes while FSX is running.Ron

Also, which version of the demo were you using?Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180