In the beginning of the week, I reinstalled FSX to "clean" it. I had no problems with that, but today I was going to do the first flight with the MD-11 in the new istallation, but I found a weird problem with the graphics. Here are some pics to illustrate that:This issue is, somehow, affecting all my payware aircraft. The default ones are normal. The MD-11 systems are still operative, the J41 cockpit is normal, but the displays are off and the graphics issue won't let me get in the Duke's cockpit. I have them for quite some time, but never had such problem with any. I ran Flight1's registry repair tool, deleted the FSX.cfg, but none of them solved it. I tried reinstalling my payware planes, but no result also.I didn't installed anything different from what I had in the previous install of FSX and also didn't pay attention if that problem was already present when I installed FSX earlier this week. I already had my FSX tweaked by Bojote's tweaking tool, just like I did with the cfg from the previous installation of FSX, what means I already have "HIGHMEMFIX" added. I searched the forums for an answer, but didn't find anything conclusive, then I posted about this problem in the MD-11 Forum, but no response there.Hope someone can help!

You are using the shader 3.0 mod arent you? You need to add the line ALLOW_SHADER_30=1 to your .cfg.

Hi,I had once the same problem. I found out that I reinstalled fsx and reinstalled the planes without deleting the planes first.So after deleting and re_installing them again the problem was gone.Hope this helps.Eric

I'd like to know why as well. It happens to me alot, I do believer however it's an indication of memory shortage, it happens almost always when I try multitasking while flying, all hell breaks loose. I normally get an error saying smoething about me Using too much memory and FSX crashes.

You are using the shader 3.0 mod arent you? You need to add the line ALLOW_SHADER_30=1 to your .cfg.

Yup! I'm using that mod. But it didn't happened the last time I installed it. That entry is there in my cfg, but the issue is still present.

Hi,I had once the same problem. I found out that I reinstalled fsx and reinstalled the planes without deleting the planes first.So after deleting and re_installing them again the problem was gone.Hope this helps.Eric

That isn't the problem either. I removed everything related to FSX when reinstalling it. I used PMDG's guide to reistall FSX. I'm afraid I'll have to do all over again.

Did you delete the old FSX.cfg?

Did you delete the old FSX.cfg?

By everything, I really mean "everything"!. I used a program I have to remove FSX's entries from the registry. My PC had no clue it was here before.

I'd like to know why as well. It happens to me alot, I do believer however it's an indication of memory shortage, it happens almost always when I try multitasking while flying, all hell breaks loose. I normally get an error saying smoething about me Using too much memory and FSX crashes.

No memory shortage also. I believe since I bought FSX 2 years ago I only got OOM warnings twice. I always used FSX in windowed mode with a lot of other programs running behind with no problems. By "a lot", I mean ASE, IvAp, IvAe, IE, TOPCAT, vRoute and some others. Not them all at the same time, of course.

I've had this problem before. I seem to remember it had to do with a bufferpools tweak. I would recommend that you rename your current FSX.cfg file and let FSX recreate a new one the next time you launch FSX.

Yup! I'm using that mod. But it didn't happened the last time I installed it. That entry is there in my cfg, but the issue is still present.

If you modify core software, don't complain when it breaks.There is a reason FSX doesn't use it by default, and you are very likely looking at the reason why not.A few config file changes will not make software work better. If only software dev was so easy!Best regards,Robin.

If you modify core software, don't complain when it breaks.There is a reason FSX doesn't use it by default, and you are very likely looking at the reason why not.A few config file changes will not make software work better. If only software dev was so easy!Best regards,Robin.

... Yeah... Now that you said it... Makes sense. It's funny because I installed the mod before and had absolutely no problems with it. FSX remained working normally. Looks like I'll have to reistall it, again, and without the mod this time. I unnistalled the mod and renamed the cfg as Jeff suggested. FSX created a new one, but no results.Thanks for the help guys. Much appreciated, but I'll have to go extreme and do all over again, again.

... Yeah... Now that you said it... Makes sense. Looks like I'll have to reistall FSX, again, and without thet mod this time. I unnistalled the mod and renamed the cfg as Jeff suggested. FSX created a new one, but no results.

I never had any problem with that mod. But you know how this is.... bummer!!!In fact, i did a full reinstall a few days ago without any problems. The only difference is i did a format and re install everything from 0

Try this SHADER_CACHE_VERSION=1,2 or 3 I had the same problem and it worked

Try this SHADER_CACHE_VERSION=1,2 or 3 I had the same problem and it worked

IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!I removed the Shader 3.0 mod and inserted "SHADER_CACHE_VERSION=2" in the FSX.cfg and IT WORKED! It's running fine now. Thanks a lot mr. Crivelli! I admit I had already given up. Just didn't have enough energy to unistall FSX again. Now I'll reinstall the MD-11's liveries and my other planes.

IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!I removed the Shader 3.0 mod and inserted "SHADER_CACHE_VERSION=2" in the FSX.cfg and IT WORKED! It's running fine now. Thanks a lot mr. Crivelli! I admit I had already given up. Just didn't have enough energy to unistall FSX again. Now I'll reinstall the MD-11's liveries and my other planes.

That's great. Never did think of the shader mod being the issue, rather the actual shader folders themselves. If I remember correctly one has to delete the 2 folders in appdata\local\MS\FSX when adding the shader mod.

This is also a symptom of not having FSX up to date with all the latest service packs.