I have posted this in other forums around the FS community but still dont have any soloution to the problem :This has happened about three times now in three months where as below no aircraft is showing on external veiws, just the lights ...I can fix this by uninstalling and reinstalling FSX but this is now getting really anoying especially when reinstalling all the addons after ...Any ideas fort a solution ?Its all aircraft default and addon.Im running 2 x Nvidia 8800 GTX cards, 4 mb Ram, Intel Quad Core Extreme QX6850 and a Ageia 128 mb physics card.Ive tried to run FSX in both DX9 and DX10 preiveiw, and Ive tried reinstalling the service packs for the PMDG 747X and MD11 as suggested in a previous forum ...Im really stuck and I dont beleive Im the only one who has ever come accross this problem .... there must be a fix somewhere in the universe ...Thanks,Gary B ;o)

I have posted this in other forums around the FS community but still dont have any soloution to the problem :This has happened about three times now in three months where as below no aircraft is showing on external veiws, just the lights ...I can fix this by uninstalling and reinstalling FSX but this is now getting really anoying especially when reinstalling all the addons after ...Any ideas fort a solution ?Its all aircraft default and addon.Im running 2 x Nvidia 8800 GTX cards, 4 mb Ram, Intel Quad Core Extreme QX6850 and a Ageia 128 mb physics card.Ive tried to run FSX in both DX9 and DX10 preiveiw, and Ive tried reinstalling the service packs for the PMDG 747X and MD11 as suggested in a previous forum ...Im really stuck and I dont beleive Im the only one who has ever come accross this problem .... there must be a fix somewhere in the universe ...Thanks,Gary B ;o)

If it's not a DX10 problem conflicting w/DX9 textures, and you're seeing this with both default and commercial aircraft (you indicate periodically), then it must be a memory issue. Try reverting to default settings under the scenery tab or lower some of the sliders and see if this fixes it. I've read that if your sliders are up too high, it could cause memory problems and aircraft textures will not show. But no, this is not a common problem and usually only happens when you are using DX9 textures with DX10 preview turned on. In the picture you provided, it appears you are near dusk and this is a time which uses a lot of memory resources.If you haven't already, you might also check out your aircraft.cfgs and make sure the textures are properly identified and the cfgs are not corrupted, and that the texture folders are there. This is the least likely cause but I suppose it could still happen.Best regards,Jim

If it's not a DX10 problem conflicting w/DX9 textures, and you're seeing this with both default and commercial aircraft (you indicate periodically), then it must be a memory issue. Try reverting to default settings under the scenery tab or lower some of the sliders and see if this fixes it. I've read that if your sliders are up too high, it could cause memory problems and aircraft textures will not show. But no, this is not a common problem and usually only happens when you are using DX9 textures with DX10 preview turned on. In the picture you provided, it appears you are near dusk and this is a time which uses a lot of memory resources.If you haven't already, you might also check out your aircraft.cfgs and make sure the textures are properly identified and the cfgs are not corrupted, and that the texture folders are there. This is the least likely cause but I suppose it could still happen.Best regards,Jim

Thanks Jim,I came accross a random subject when looking for a solution a few minuites ago where the FSX.CFG is renamed FSX_BSOD.CFG ...Im glad to say this worked but how I have no idea ...Can you shed some light on the reason why this worked ?Gary B ;o)

Thanks Jim,I came accross a random subject when looking for a solution a few minuites ago where the FSX.CFG is renamed FSX_BSOD.CFG ...Im glad to say this worked but how I have no idea ...Can you shed some light on the reason why this worked ?Gary B ;o)

My guess is that by renaming the fsx config file you have caused fsx to build a new one. The action of causing FSX to build a new config file has been mentioned in this forum many times as a solution to odd problems. You could always check if your have both your renamed file and another called FSX.CFG. If so then FSX has built a new config file. It is more ususal just to delete your config file in order to cause FSX to build a new one but renaming it would give a similar result. If your problem is now fixed then clearly your old config file was messed up somehow.Glad to hear that your frustrating problem is fixed.