So in this thread we are now on to disabling part of the FSX effects pool to solve your BlackScreen problems?You guys have fun with that.

Um, yeah, not something I would be ready to do...

After doing various tests I found out that on my computer BP at zero works well in windowed mode. In full screen mode I get artifacts, but when I switch to windowed mode they are gone. So I am now starting to do some tests in windowed mode (where the windows is as big as it can be but not maximized, so you can see the edges).Doing this I can fly above Orbx's Darrington with autogen at Extremely dense and very good performance! After that teleported to Seattle, a very heavy city in PNW, and even though performance wasn't as good and smooth as it was above Darrington, I could fly without any problems and lowest average fps was at 19. Fps doesn't say everything, as we all know, but all in all performance was good enough to actually enjoy flying there (although I do like the bush more). With autogen at Extremely dense it looks great down there!Now my only problem is that in windowed mode vsync won't work... And that's a pity. So right now I have to make a choice: fly above Darrington etc. in windowed mode, BP at 0 with great performance but no vsync, or fly above Darrington full screen, BP at 500000 with stutters but also vsync... (BTW I also have stutters with autogen at Very dense and BP at 500000).Anyone knows a method to get vsync working in windowed mode? :(

After doing various tests I found out that on my computer BP at zero works well in windowed mode. In full screen mode I get artifacts, but when I switch to windowed mode they are gone. So I am now starting to do some tests in windowed mode (where the windows is as big as it can be but not maximized, so you can see the edges).Doing this I can fly above Orbx's Darrington with autogen at Extremely dense and very good performance! After that teleported to Seattle, a very heavy city in PNW, and even though performance wasn't as good and smooth as it was above Darrington, I could fly without any problems and lowest average fps was at 19. Fps doesn't say everything, as we all know, but all in all performance was good enough to actually enjoy flying there (although I do like the bush more). With autogen at Extremely dense it looks great down there!Now my only problem is that in windowed mode vsync won't work... And that's a pity. So right now I have to make a choice: fly above Darrington etc. in windowed mode, BP at 0 with great performance but no vsync, or fly above Darrington full screen, BP at 500000 with stutters but also vsync... (BTW I also have stutters with autogen at Very dense and BP at 500000).Anyone knows a method to get vsync working in windowed mode? :(

I have the same problem. Everything but 0, stutters, no snow in windowed, also no vsync. As soon as in full, with 0, snow.

I have the same problem. Everything but 0, stutters, no snow in windowed, also no vsync. As soon as in full, with 0, snow.

Hm, okay... I have to say though that performance in windowed mode is so much better (with BP=0) that I will give windowed mode a try for some days. Maybe I can get used to having no vsync...

Hm, okay... I have to say though that performance in windowed mode is so much better (with BP=0) that I will give windowed mode a try for some days. Maybe I can get used to having no vsync...

Without vsync I get severe tearing though.

Sure Stephen!, thanks for your offer.YOU NEED to read carefully and follow the steps EXACTLY, then report back your findings.1) Locate the ShadersHLSL inside your FSX folder.2) Now, locate and browse inside the 'Common' folder inside ShadersHLSL3) You'll see a file called: Common.fxh, make a backup of it, because you'll be editing it.Locate the following line in the Common.fxh file: dword State_TextureWrap : STATE_TEXTUREWRAP = D3DTADDRESS_WRAP;and change it to: dword State_TextureWrap : STATE_TEXTUREWRAP = 0;REMEMBER, after you make the above change, you'll need to delete the shaders cache (so it is rebuilt again using the new parameter) the shaders cache is located in C:\Users\USERNAME\AppData\Local\Microsoft\FSX\Shaders where USERNAME is your Win/Vista username. If you don't delete the shader cache, the above change is useless.Stephen, to properly test you need to have a situation where you can replicate, consistently, a black screen/corruption scenario. So, don't run Vista compatibility mode, that mode helps prevent the black textures.report back with your observations, in my particular case, texture 'corruption' and or black screens was an event I was able to 'replicate' consistently always at the same place/location.

Hi *******,Thanks for replying. I will follow the procedures outlined above and take my first test flight (with bufferpools=0).

Thanks for replying. I will follow the procedures outlined above and take my first test flight (with bufferpools=0).

I gave it a try: instant artifacts. Luckily I backupped everything, so I was back into business in a few seconds. It was worth a shot...Anyway, I usually don't get artifacts in windowed mode, but that mode doesn't work with vsync, so I settled for this compromise (I also posted this elsewhere, but for completeness sake I'll post it here too): I fly with BP=0 in full screen (which gives the best performance by far) and when I do get artifacts, I switch to windowed mode (full screen but not maximized). Simple as that.I just did that with a flight from Firstair to Darrington. I got artifacts after a few minutes (still near Firstair, 'defaul't PNW). So I switched to windowed mode for a few seconds and back to full screen mode because I was curious to see if the artifacts would come back again. To my amazement... I could finish the flight all the way to Darrington without any artifacts... While Darrington (the payware addon) usually always gives me artifacts. :( And all that with good performance (and average fps didn't drop below 21 and usually stayed around my maxed 25).Computers... you gotta love them... :(I suppose this was one of those lucky flights again, but who knows. The coming days I will start each flight in full screen (BP at zero) and switch to windowed mode when I get artifacts. I will switch back to full screen again and stay there until I get artifacts again, etc. etc. etc. We'll see what happens... :(

*******,Making the shader changes and deleting the cache worked very well for me. I flew and reflew the places and circumstances that made the black screen and corrupted textures shut me down. I snapped around and around in and out of map and user bar settings. No problems, and full textures back each time, perfectly stable. This is with Bufferpools=0. There is the very occasional flashing texture (as before) but very smooth. I think you are onto something important here. By the way, I have 185.50 installed, use FPS Limiter and NHancer if that makes any difference. Stephen

I gave it a try: instant artifacts. Luckily I backupped everything, so I was back into business in a few seconds. It was worth a shot...Anyway, I usually don't get artifacts in windowed mode, but that mode doesn't work with vsync, so I settled for this compromise (I also posted this elsewhere, but for completeness sake I'll post it here too): I fly with BP=0 in full screen (which gives the best performance by far) and when I do get artifacts, I switch to windowed mode (full screen but not maximized). Simple as that.I just did that with a flight from Firstair to Darrington. I got artifacts after a few minutes (still near Firstair, 'defaul't PNW). So I switched to windowed mode for a few seconds and back to full screen mode because I was curious to see if the artifacts would come back again. To my amazement... I could finish the flight all the way to Darrington without any artifacts... While Darrington (the payware addon) usually always gives me artifacts. :( And all that with good performance (and average fps didn't drop below 21 and usually stayed around my maxed 25).Computers... you gotta love them... :(I suppose this was one of those lucky flights again, but who knows. The coming days I will start each flight in full screen (BP at zero) and switch to windowed mode when I get artifacts. I will switch back to full screen again and stay there until I get artifacts again, etc. etc. etc. We'll see what happens... :(

Jeroen,Are you sure you did it exactly as ******* said? Did you delete the entire cache (common, Fixed Function, General, Misc and Terrain files)? Did your shader change make sure ther is no space before the 0?Stephen

*******,I have now tried for over 3 hours to make this thing CDT, and can't do. I have toggled between everything on userbar, in and out of flight planner, maps as fast as I can, swapping aircraft, options, back and forth between windowed and full screen - and nothing. It is completely stable. What is the theory behind this? You have fixed the texture corruption, blackout - shut down CDT bug on my machine! If there are any side effects, I have not spotted any. How come you know these things? You can tell me, I will keep it a secret, honest! :(Stephen

Hi,Well, I'm up to the part of cleaning out the cache. Are you saying to erase all the files located in the following directories?.1. Common2. FixedFunction3. General4. Misc5. TerrainThanks

Hi,Well, I'm up to the part of cleaning out the cache. Are you saying to erase all the files located in the following directories?.1. Common2. FixedFunction3. General4. Misc5. TerrainThanks

Yes Mike, that is correct, delete those five files themselves and everything in them, but make copies first and be careful on the edit change. Make sure that there is no space between the =and the 0. This sure seems to be a real bug fix. I still can't make this CTD and I have been outright abusing it. :( Where and how does he come up with this stuff? Another resident genius? There are a few around here I think.Stephen

Hi,Ok, I'll give it a shot.

Yes Mike, that is correct, delete those five files themselves and everything in them, but make copies first and be careful on the edit change. Make sure that there is no space between the =and the 0. This sure seems to be a real bug fix. I still can't make this CDT and I have been outright abusing it. :( Where and how does he come up with this stuff? Another resident genius? There are a few around here I think.Stephen

Hi,Ok, I'll give it a shot.

Be careful... there are TWO shader folders!!1) the Source shader/effect Files2) the compiled shadersMake sure you delete the COMPILED ones!! and not the source!Source is called ShadersHLSL, that YOU DON'T DELETE.. just modify Common/Common.fhx inside as instructed.Compiled shaders are in C:\Users\YOURUSERNAME\AppData\Local\Microsoft\FSX\Shaders and you can delete that dir ENTIRELY, it is rebuilt everytime FSX is started.

I gave it a try: instant artifacts. Luckily I backupped everything, so I was back into business in a few seconds. It was worth a shot...

One thing.. this shader fix is not meant to 'fix' any artifacts! its simply a hack to 'avoid' texture corruption/black screens due to compression of animated textures. Tim (who originally started the official PMDG thread) already gave it a try and ask him about his results :)

Hey JesusI just want to thank you for bringing this to my attention, with this tweak I am ripping it in FSX.I switched OS to Winxp64 which has resolved all the texturing issues. Just for fun I slid all sliders forwards and took a flight around Miami in the Sky Unlimited p38 lighting a severe thunderstorm with 2048 clouds and my frames never dropped below 30.You have changed FSX for me, and I truly thank you.