What is the effect of no using BP=0, but still using:TEXTURE_BANDWIDTH_MULT=400TextureMaxLoad=15I get numerous driver crashes on the GTX480 when using the BP=0.If I get rid of BP=0 but leave in the above entries the sim is just as smooth and the driver doesn't crash (not yet anyway).Would would happen is that the frame rate would slow to about 1 fps and the screen become more and more corrupted until it finally crashes.The OS would be fine, just a nvd3dum.dll crash.TIA

If I get rid of BP=0 but leave in the above entries the sim is just as smooth and the driver doesn't crash (not yet anyway).

Did you experiment lowering the LOD radius to 3.5? Also, what level of Antialiasing and Aniso are you using? Application controlled or are you forcing them higher?

Would would happen is that the frame rate would slow to about 1 fps and the screen become more and more corrupted until it finally crashes.The OS would be fine, just a nvd3dum.dll crash.

By the way, that crash, is a DRIVER RESET. Your GTX 480 clocks are defaulting to a very low value, I can help you troubleshoot it, but follow the steps I'm asking you so I can better understand the root cause. and I was able to replicate the exact same problem, but only when using a LOD of 6.5 so the increased radius DOES help induce the crashes.

Did you experiment lowering the LOD radius to 3.5? Also, what level of Antialiasing and Aniso are you using? Application controlled or are you forcing them higher?By the way, that crash, is a DRIVER RESET. Your GTX 480 clocks are defaulting to a very low value, I can help you troubleshoot it, but follow the steps I'm asking you so I can better understand the root cause. and I was able to replicate the exact same problem, but only when using a LOD of 6.5 so the increased radius DOES help induce the crashes.

I'll try that now. Antialiasing and anistropic are both application controlled.

I'll try that now. Antialiasing and anistropic are both application controlled.

In fact, I would suggest as a tip that you even go ALL the way with the autogen slider to Extremely Dense, this will cover the ground almost 100% so, having the LOD to 3.5 won't affect quality AT ALL because you can't see blurries under buildings :)

In fact, I would suggest as a tip that you even go ALL the way with the autogen slider to Extremely Dense, this will cover the ground almost 100% so, having the LOD to 3.5 won't affect quality AT ALL because you can't see blurries under buildings :)

Tried with LOD_RADIUS at 3.5 and same thing happens after about 7-8 mins flying around MegaCity San Francisco in the Nemeth EC-135 helicopter. This is repeatable.Driver does indeed stop responding and then recover although FSX does not.In GPU-Z max temp was 76'C, max memory was 558MB. At time of crash (maybe as a result) core clock on 480 dropped to 405.Sliders in FSX are:Target Frame rate: 25Resolution: 1920x1200x32 (I run in windowed mode)Filtering: AnistropicAntialiasing: TickedLOD Radius: Large (but used 3.5 for test as requested)Mesh: 100Mesh Res: 5mTexture Res: 7cmWater: 2.x HighScenery: Very DenseAutogen: Very DenseNo FSX traffic at all but use Ult Traffic 2 at 50%.Any more tests you would like me to try, let me know. I will now delete BP=0 to confirm it will not crash.

Could not get it to crash once the UsePools=0 entry was deleted from the cfg.Frame rates were the same, GPU memory usage was up slightly to 690MB.No bufferpools value forced in cfg so FSX using default (4M ?).Still using:TEXTURE_BANDWIDTH_MULT=400TextureMaxLoad=15GPU-Z must not be reporting the 480 clocks correctly. Was still showing GPU core at 405 MHz and Shader at 810 Mhz but FSX was not affected so probably flase readings.

Tried with LOD_RADIUS at 3.5 and same thing happens after about 7-8 mins flying around MegaCity San Francisco

Even a 285 with LOD_RADIUS 3.5 and EXTREMELY dense autogen is able to keep up, so, there is something not right. let me propose you an idea.. I'll give you personalized one to one support to help solve this one, what do you think? just private message me with your phone and I'll go over all the settings with you.

Even a 285 with LOD_RADIUS 3.5 and EXTREMELY dense autogen is able to keep up, so, there is something not right. let me propose you an idea.. I'll give you personalized one to one support to help solve this one, what do you think? just private message me with your phone and I'll go over all the settings with you.

Thanks for offer but I am happy without using BP=0. Just tried in Manhatten with ex dense scenery/autogen and water at 2 max and I was still getting 19-22 fps. Thats a great improvement over my 280.If I back off the scenery/autogen to v dense and the water to 2.x high I can get a locked 25 fps virtually anywhere (a lot of AI in and around NY causes problems but I only really fly there for testing!).Thanks again for all your help and the HIGHMEMFIX tweak is a godsend for the PMDG planes.Cheers, Daz.

Thanks again for all your help and the HIGHMEMFIX tweak is a godsend for the PMDG planes.

No prob!BTW, can you do a final test with BP=0? this time disable the ENBMod.Thanks,

No prob!BTW, can you do a final test with BP=0? this time disable the ENBMod.Thanks,

To test without ENB do I remove the files or is disabling via Shift-F12 enough?Would it also be worth finding at which Bufferpools level the crashes stop, i.e. start at say 50,000 and work my way up until they stop?