Make sure that there is no space between the =and the 0.

O, I didn't do that... The instructions that ******* posted don't say that so I left a space there. How did you know you shouldn't put a space there? I will try it again tonight without that space... (Can't imagine it would make a difference, but we'll see. :( )

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 :)

Ah... I thought texture corruption/black screens were artifacts...? I am a bit confused now. BTW I am not behind my FSX computer but I remember seeing two folders where the compiled shader folders are: one was called Shaders (and that one I deleted) but there was also one called Shaders12 (or something like that). Should I also delete that one...? Well, I will have another close look at it all tonight. :( BTW 2: Since these shader files are made everytime you start FSX, there is no need to make a backup, I guess...?

O, I didn't do that... The instructions that ******* posted don't say that so I left a space there. How did you know you shouldn't put a space there? I will try it again tonight without that space... (Can't imagine it would make a difference, but we'll see. :( )Ah... I thought texture corruption/black screens were artifacts...? I am a bit confused now. BTW I am not behind my FSX computer but I remember seeing two folders where the compiled shader folders are: one was called Shaders (and that one I deleted) but there was also one called Shaders12 (or something like that). Should I also delete that one...? Well, I will have another close look at it all tonight. :( BTW 2: Since these shader files are made everytime you start FSX, there is no need to make a backup, I guess...?

No, don't delete Shaders10. I get graphical errors if I do that... they are not recreated.But anyway, this whole thing from MS, seems very weird to me and MS typical infact: making things more complicated than they are. Why with BP=0 everything is faster? Meaning hardware has a potential to run it faster, the engine simply sucks...

But anyway, this whole thing from MS, seems very weird to me and MS typical infact: making things more complicated than they are. Why with BP=0 everything is faster? Meaning hardware has a potential to run it faster, the engine simply sucks...

Yes, hardware has a potential to run it faster but... at the time FSX was created this hardware was not available yet...! Back then there weren't graphic cards with 1 Gb of RAM, so they HAD to use normal RAM for specific things. BP=0 works so well (if you are lucky) on modern systems with the right hardware because setting it to zero will move all of the workload (as far as BP is concerned) to the GPU ram (afaik, I am no expert). Older cards with less ram just can't do that so when FSX was created normal ram had to be used and this gives stutters (when specific things have to be replaced in the ram... or something like that...).So in fact, instead of blaming MS for something, you could also say they did a great job in making FSX configurable, so even though the program is quite old by now, we can still use it and even optimize it for modern hardware! Not much games have that possibility... :( This is the reason why we will never stop talking about tweaks and FSX, because new hardware makes new tweaks possible... even in a way that MS and Aces never could have known.

Yes, hardware has a potential to run it faster but... at the time FSX was created this hardware was not available yet...! Back then there weren't graphic cards with 1 Gb of RAM, so they HAD to use normal RAM for specific things. BP=0 works so well (if you are lucky) on modern systems with the right hardware because setting it to zero will move all of the workload (as far as BP is concerned) to the GPU ram (afaik, I am no expert). Older cards with less ram just can't do that so when FSX was created normal ram had to be used and this gives stutters (when specific things have to be replaced in the ram... or something like that...).So in fact, instead of blaming MS for something, you could also say they did a great job in making FSX configurable, so even though the program is quite old by now, we can still use it and even optimize it for modern hardware! Not much games have that possibility... :( This is the reason why we will never stop talking about tweaks and FSX, because new hardware makes new tweaks possible... even in a way that MS and Aces never could have known.

Well, I must say, you are right about that. I kinda compare this situation with a non-car-mechanic trying to repair a car. Eventually and maybe successful, but also through many failures and tryouts.Anyway, did anyone try my tweak with BP=1?Some other things I observed: with my new PMDG JS4100, I was doing tutorial in windowed, with a tweak applies, BP=0, after an hour or so, I wasn't doing much, just loaded and pressing some buttons in VC, but over a long time, machine rebooted with Kernel-Power failure. I repepated the same thing, but this time I got snow, even in windowed (I never went to full). I then reverted to no BP, default shaders, and no tweaks, I was flying until I caught on engine fire ;-) It was much longer than the 1st time.

If bp=0 ( unlimited ) cannot be used be some, why not try a very high value like 400-2000 mb, depending on the memory size of the graphics card.

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.

I had not seen any issues with texture corruption with BP=0, however I wanted to see the consequences of applying this tweak. What I noticed immediately is some legacy FS2004 aircraft (those that seem to have been generated using FSDS 2) "lose" various parts. There's a number of such aircraft I use in FSX, including those of my own design but also aircraft like the Munch Bro's Rotorway Exec, arguably my favorite copter in FSX. So I think a word of caution is in order, as with all tweaks. What often happens is someone will apply a tweak like this, fly for several weeks or even months, then fire up that old aircraft in the closet for nostalgia's sake. What often happens is the tweak is long forgotten, and someone will painfully uninstall and reinstall FSX.I always keep notes of tweaks I've applied, and there haven't been many. Also I log all my add-ons, including the date installed. As a result I've yet to reinstall any flavor of MSFS in many years of simming. Within the first week of applying any tweak like this or the original BP tweak, I suggest to exercise the sim as much as possible and try as many different aircraft, flight scenarios and scenery combinations as possible.Regards,John

Hi John, what OS are you running, is it XP?, after switching to XP I have no graphic glitches whatsoever, it's literally a miracle.

Without vsync I get severe tearing though.

Apparently there is a way to force vsync in window mode. Take a look a the 6th post down by Anthony:http://www.simforums.com/forums/forum_posts.asp?TID=33631Regards.Henry

Hi Henry,It was posted here at AVSIM yesterday, here's the link. While others have had some luck with this added to the fsx.cfg file, I know J van E was unable to get it to work. Strange how it works for some and others have no luck, maybe the OS has something to do with the success or failure of this added config statement.http://forums1.avsim.net/index.php?showtopic=278540

Apparently there is a way to force vsync in window mode. Take a look a the 6th post down by Anthony:http://www.simforums.com/forums/forum_posts.asp?TID=33631Regards.Henry

I might have tentative good news. I have been flying for over two hours within PNW with the topic duo and have not had any ARTIFACTS or crashes of any kind.Perhaps artifacts are not just necessarily Vram exhaustion on a 1GB card, but is a hit and miss with the driver package you are running with.I loaded up this driver suite two days ago, and have not had any issues, but with clear and vivid scenery at 30 FPS.Give it a try and see if you can fly at least 2 hours over any terrain without the big 'A' showing up as well. The best I ever got with the driver set one below this, was about 1/2 hour to 3/4's of an hour before it was all over....Mitch IMPORTANT POST EDIT: I no sooner typed this post...then went back to flying, and severe ARTIFACTS shut me down. I simply cannot use BP=0. The closest I can get is BP=500000. I'll just stick with that.

I tried it all over again (the shader tip) but still no luck... However, here is something else to think about: I've been testing the BP=0 mainly with the Carenado C182RG, C185F and the default Bell 206. Almost always it ended with artifacts (unless I ran FSX in windowed mode). Today I reinstalled the Quest Kodiak (after finding a fix for some problems I had with it) and... I've done three complete flights with it and I only got artifacts once, for a split second (and I didn't even have to go to windowed mode to restore it all). In full screen, that is! I could even land at Darrington without problems (Extremely dense autogen!). The Kodiak is heavier on the system than the Carenado (but not too much), so I expected to see artifacts sooner... But I was wrong. And all that without compatibility mode etc. Just BP at 0. (TBM at 70 right now btw.)It's getting more and more weird... So now I will fly the Kodiak for a few days in full screen with BP=0 and I'll see what happens. Might it make a difference what plane you fly........?!? :( :(

Frustrating, isn't it...?BTW Do you fly with specific planes all the time? This evening I installed the Quest Kodiak again and I have completed 3 flights without artifacts (apart from one single one that didn't have any consequences). Before this I always flew two Carenado planes or the default Bell 206. It sounds weird but maybe another plane works better...?P.S. I also posted this in the 'big BP=0' topic, so if you want to talk about BP=0 and various planes, let's do it there, otherwise we'll get posts about this all over the place. :(

Frustrating, isn't it...?BTW Do you fly with specific planes all the time? This evening I installed the Quest Kodiak again and I have completed 3 flights without artifacts (apart from one single one that didn't have any consequences). Before this I always flew two Carenado planes or the default Bell 206. It sounds weird but maybe another plane works better...?P.S. I also posted this in the 'big BP=0' topic, so if you want to talk about BP=0 and various planes, let's do it there, otherwise we'll get posts about this all over the place. :(

-------------------------------------------------------------------------I usually fly with two Carenado planes; The Mooney, or the Station Air 6 Amphib version. I haven't tried using the BP=0 with a standard FSX plane as per its Mooney. I would have used the BP thread except I really thought I had something here...and wanted to make sure people saw it. Turned out to be another lame BP=0 duck, :(Like you said, back to the BP=0 thread, if any. The frustrating part...is that BP=0 gives the best performance to date, period! I just can't hang onto it.Mitch

Can you provide a definition of "artifact". Seems like it could cover many different things.scott s..

I believe the artifacts bug is related to the driver settings. are you using nhancer? I am too and suddenly get artifacts right after the flight loads up. Maybe setting the 3d settings through the nvidia control panel rather than nhancer will fix it? I am so tired of tweaking I have given up for now