I think no one will mind if you two use the PM-system to fight this one out... :(

sorry about that. besides, we are not fighting, just civil discussion of personal point of views.

dword State_TextureWrap : STATE_TEXTUREWRAP = 0;

Set the above back to 1, like this:dword State_TextureWrap : STATE_TEXTUREWRAP = 1;delete the cache, try again and report back. if it WORKS, then tell me what 'default' aircraft loads when you start FSX. I also suggest you read what JohnCli wrote two pages ago.

I just wanted to thank the original post for this miracle cure. This is simply remarkable.I thought I needed a new card. After loading the 196.21 and the BP=0 teak, I can't believe the performance boost.I do have textures that flash and spikes, but I know it's only a matter of time before I find the right TML setting.Thanks a million.

I just wanted to thank the original post for this miracle cure. This is simply remarkable.I thought I needed a new card. After loading the 196.21 and the BP=0 teak, I can't believe the performance boost.I do have textures that flash and spikes, but I know it's only a matter of time before I find the right TML setting.Thanks a million.

Sorry Jose, what do you mean by the right TML setting ?Is there a link between artifacts and TML? :( (I'm a bit lost in this looooooooong thread...)

Sorry Jose, what do you mean by the right TML setting ?

I think what he meant was TBM, but used TML for TextureMultipLier.

David,My bad. :( TBMJesus,This tweak shows how important drivers and "tweaks" are for FSX. I can't think of any software in history that has been tweaked more by its users. LOLI know I have tried just about everything.

*******,This tweak shows how important drivers and "tweaks" are for FSX. I can't think of any software in history that has been tweaked more by its users. LOL

be very careful with the latest nvidia drivers :) I'm sure you know the problem about fan control don't you? I think there is a warning on the nvidia site!

be very careful with the latest nvidia drivers :) I'm sure you know the problem about fan control don't you? I think there is a warning on the nvidia site!

Drivers are not longer on the site. Latest are those 196.21s.

be very careful with the latest nvidia drivers :) I'm sure you know the problem about fan control don't you? I think there is a warning on the nvidia site!

Hi *******,This thread gets more intersting by the page. :( Can you elaborate on what you mean by the latest Nvidia drivers fan speed? I am aware of the overclocking software issue with 196.21. Are there other negative issues associated with the last series of drivers? I use 185.50 still which seems safe and secure.Stephen

Can you elaborate on what you mean by the latest Nvidia drivers fan speed? I am aware of the overclocking software issue with 196.21. Are there other negative issues associated with the last series of drivers? I use 185.50 still which seems safe and secure.

No need to worry, as Word Not Allowed pointed out, they were removed from nVidia site, but it is possible someone have installed those drivers. Here's the official nVidia alert to customers:http://www.nvidia.com/object/196.75_customer_support.html

Maybe for the same reason as I have: I'm very curious how this wild-goose chase will end up. Started off as a holy grail tweak. Now there is some "deep and systematic" testing to be done to determine wether artifacts, when using the holy grail tweak, are caused by the CPU or the GPU. I'm now anxiously waiting for the next chapter...My recommendation to people having problems with the tweak would be to either revert to "normal" BP setting, turn down some display settings a notch or two, lock fps at 25 and enjoy flying the sim instead of tweaking away the best time of their life,orif needed build a high end computer and enjoy FSX with high display settings instead of tweaking away the best time of their life.I remember that Mitch some months ago build himself a real good FSX computer. No need for any tweaking then! Now Mitch is one of the persons eagerly searching for the holy grail, instead of flying. IMO this is insane. I wonder what Mitch and all other tweakers will think of this holy grail next year?Just my thoughts. Sorry!

----------------------------------------------------------------------------------Well....since buying my Dell XPS 730x i7-975/GTX285, I pretty much have FPS always hovering around the 30 FPS range. I do have to say though that with BP=0, the scenery was dead on smooth in animation, FPS's that were trying to break out of the 35's even locked down...and I have to say that this one 'tweak' kicked butt like no OTHER tweak, EVER! Also...having said that...it in fact does cause artifacts around the 1/2-3/4 hour mark of FSX running. I get about 98 percent the efficacy of the BP=0 with a BP of 500000. Very slight micro-stutter here and there...but still enjoyable. For the boost to anybody's system that BP=0 gives...I'd have that running always in my config in a heartbeat and enjoy whatever it brings to the table. If someone can isolate the artifact eventuality...then it will become permanent. Other than that, I don't bother with 'tweaking'. I DO TUNE UP THOUGH, by proper maintenance of my O.S. and hard system.:)More flying...and much less tweaking since last July/2009! :)BTW, was the first ride of the season on my bike today, 66 F and no issues with FPS...just police hiding out behind billboards and coming out of donut shops behind you....Mitch

*******,I'm NOT running the latest. I was aware of the overheating problem.Now with the 21's I do get these flashes and scenery spikes despite the outstanding performance. I've tried other BP settings but they yield stutters in my highly dense sceneriesI hope that a future driver will help my cause. At least I know how it works now.I'm going to assume that my 1 gig card just can't keep up.

You may find this funny, but the bufferpool setting that works for me (and NOTHING below that does) is:[bufferpools]PoolSize=590000000This is a NVidia 285 with 2GB VRAM, Win7 64bit 8GB RAM. 3.2GHz clock speed (oced from 2.83GHZ).Scenery complexity extremely denseAutogen density very dense.FSX folder with addons (lots of large photoscenery like VFR Germany or FSDreamscape's Utah) is more than 300GB. 403 scenery entries. :-)With 590MB Pool size, I can enjoy flights with nice visuals and good framerates.Problems with lower bufferpool settings are:1) Crackling sound2) Black screen after loading3) Loss of autogen trees and clouds4) My plane with parts in silly places (flaps on top of the cockpit)5) 5-8 fps where I normally have 30fps.I CAN use lower bufferpool settings when I reduce autogen to dense or normal. Then I can go as low as 290MB

David,My bad. :( TBM

:--))Thanks Jose.When reading TML I thought you were speaking about TEXTURE_MAX_LOAD

You may find this funny, but the bufferpool setting that works for me (and NOTHING below that does) is:[bufferpools]PoolSize=590000000This is a NVidia 285 with 2GB VRAM, Win7 64bit 8GB RAM. 3.2GHz clock speed (oced from 2.83GHZ).Scenery complexity extremely denseAutogen density very dense.FSX folder with addons (lots of large photoscenery like VFR Germany or FSDreamscape's Utah) is more than 300GB. 403 scenery entries. :-)With 590MB Pool size, I can enjoy flights with nice visuals and good framerates.Problems with lower bufferpool settings are:1) Crackling sound2) Black screen after loading3) Loss of autogen trees and clouds4) My plane with parts in silly places (flaps on top of the cockpit)5) 5-8 fps where I normally have 30fps.I CAN use lower bufferpool settings when I reduce autogen to dense or normal. Then I can go as low as 290MB

Yep, this thread does indeed get more and more interesting. That's quite a difference of opinion I'd say - from Bufferpools=0 to Bufferpools=590 million, and quite a few in between. Glad we are narrowing this down!

:--))Thanks Jose.When reading TML I thought you were speaking about TEXTURE_MAX_LOAD

David, I finally fell for it. Tried to squash the bug with my thumb!Stephen