I have been running a reduced BP (800000) for a year or so now, after seeing a recommendation from Rob Young. It without doubt reduced some of the wild fluctuations in frame rate when running 'unlimited' - raising it would only degrade performance, esp. above 50000000, and above 100 mil aircraft models could become corrupted.I had not considered running a zero, until reading this thread, and have now been using FSX with this value for three days and see nothing but positives

QuoteThe first ever recorded suggestion to use PS=0 :) (It's in French, so I don't have any idea what they are talking about)http://www.libertysim.net/forum/viewtopic.php?t=10833BTW, David, check this post: http://forums1.avsim.net/index.php?showtopic=233158

:( I'm very probably getting old!!

This is what he said, in May 2007!Hi, Small tip discovery Libertysim for FSX By adding this: [bUFFERPOOL] PoolSize = 0 Me I get a very clear improvement in FPS. Bye Livai :(

What do you bright lights think is causing severe flashing of textures when I try BF 0. That really confounds me. hmmmm...Stephen

Hi all First off thanks to the OP for bringing the tweak up and to everyone whos posted worthwhile replys :)Just thought id share a few of my own findings after playing with this tweak for the last few days First off my specs are [email protected],260GTX 768 216sp (196.34 beta's) ,4Gb main mem,Audigy2,Hanns.g HG281D 27.5" 1920x1200 LCD win7 x64Now as i only have a 768mb GFX card i want to try and find a way to use this tweak with out getting the autogen warpping and flashing textures,Run it stright as BP=0 in the config would pretty much double my unlimited frame rate but would always cause the system to reset its GFX clock back to 2d modes or lock up the system totally within 2-3 mins of take off,now in not going to babble on about my ins and outs of testing various modes of AA/AF to regin it in i'll just get to the meat Using BP=0 in combination with the FPSlimiter set to 30fps i was able to move up a level of autogen (now both dense no tree/building cfg tweaks) and run Waterx2 high this is with 4096 custom clouds+water normal & also a 4096 paint scheme (goose HD redux) with Force nHancer AFx16 AAx8 & clamped negitive LOD and it stay at 30fps 99% of the timewithout BP=0 in the config the same settings only got up to about 12-15 fps!with BP=0 but without fpslimiter 40-60 fps but flashing/warping or resets/lockup with in a few mins So if you've tryed BP=0 and gotten lockups or flashing/warping autogen try using it in combination with the FPSlimiter (the java based on not ingame) it might help you like it did meDisclaimer hehe ;) These are results from MY system and you might not get the same im just posting to tell ppl of the sucess ive had with it on my system,give it a shot after all it will only take a few mins to set up/testCheersGizmo

After initializing a couple of flights in NYC for testing, my FSX displayed zero noticeable difference with this tweak. Perhaps more testing is needed.

Hi all First off thanks to the OP for bringing the tweak up and to everyone whos posted worthwhile replys :)Just thought id share a few of my own findings after playing with this tweak for the last few days First off my specs are [email protected],260GTX 768 216sp (196.34 beta's) ,4Gb main mem,Audigy2,Hanns.g HG281D 27.5" 1920x1200 LCD win7 x64Now as i only have a 768mb GFX card i want to try and find a way to use this tweak with out getting the autogen warpping and flashing textures,Run it stright as BP=0 in the config would pretty much double my unlimited frame rate but would always cause the system to reset its GFX clock back to 2d modes or lock up the system totally within 2-3 mins of take off,now in not going to babble on about my ins and outs of testing various modes of AA/AF to regin it in i'll just get to the meat Using BP=0 in combination with the FPSlimiter set to 30fps i was able to move up a level of autogen (now both dense no tree/building cfg tweaks) and run Waterx2 high this is with 4096 custom clouds+water normal & also a 4096 paint scheme (goose HD redux) with Force nHancer AFx16 AAx8 & clamped negitive LOD and it stay at 30fps 99% of the timewithout BP=0 in the config the same settings only got up to about 12-15 fps!with BP=0 but without fpslimiter 40-60 fps but flashing/warping or resets/lockup with in a few mins So if you've tryed BP=0 and gotten lockups or flashing/warping autogen try using it in combination with the FPSlimiter (the java based on not ingame) it might help you like it did meDisclaimer hehe ;) These are results from MY system and you might not get the same im just posting to tell ppl of the sucess ive had with it on my system,give it a shot after all it will only take a few mins to set up/testCheersGizmo

Hey Gizmo,Thanks for your report. I am using FPS Limiter, which is one of the best little programs worth its wieght in gold, so to speak. Stephen

Hey Gizmo,Thanks for your report. I am using FPS Limiter, which is one of the best little programs worth its wieght in gold, so to speak. Stephen

For me :FPSL + BP=0 >> artefactsBP=0 without nHancer >>artefactsFSX.cfg with any AffinityMask entry >> artefactsTBM > 60 >> artefacts

For me :FPSL + BP=0 >> artefactsBP=0 without nHancer >>artefactsFSX.cfg with any AffinityMask entry >> artefactsTBM > 60 >> artefacts

David,LOL :( So, does that mean that you got artefacts no matter what you did? Stephen

NO :--)As I said previously:After few tests, some good hours and lot of coffee I think there is a balance to find between TBM and BF=0 to avoid artefacts.For me it is TBM=60, using nVidia latest driver, Dx9 + nHancer + FSX display fps limited @ 25. (no fps limiter!)And the result is really spectacular!and... the latest directx !

severe flashing of textures when I try BF 0. That really confounds me. hmmmm...

Hi Stephen,When I first tried BP=0 I experienced exactly the same thing...I found out that 'forcing' FSX to load bigger textures fixed it. (by forcing bigger textures I mean using Max 2.0 Water, Dense autogen, Dense scenery etc. forcing your video card to do MORE work in VRAM usage and GPU usage) This is pure speculation on my part, but, I think that when BP=0 is used something changes in the process priority schedule in FSX, IF you don't stress the VIDEO card enough you get flashing textures... notice that David claims that NOT using nHancer made him experience flashes/artifacts! so, it might be a reasonable theory.If you read all my posts you'll see I already recommended this... of course sarcastic police jumped in making fun of my comments, so, if you want to experiment, by all means! go ahead and report back.

Hmm - quick test on my system basically gave me rolling waves in the landscape as I was moving.Anyone take stock of which OS are reporting success vs failure?It seems that most running w764 are getting good results while Vista & xp are so so.Running Xp64 q9650 @3.88 4G 1700 8-8-8-24 1t gtx280 182.50 nhancer ENB bloom locked at 30 with no issues

I have my Sim-Truth and you have yours!

:(

Bufferpools = 0 has greatly enhanced performance for me! I guess that it might have increase FPS by at least 30%. However, I also encounter graphical anomalies, but I only see those when my FPS are way high (like 60) as with default aircraft or VFR flight.. In my Level-D 767 or PMDG MD-11 at payware (larger) airports I do not see them, yet I do experience some flickering textures (though I'm okay with that given the amazing increase in the smoothness of my sim). As to solve the issues with default aircraft / VFR flying, I wanted to try FPSLimiter, but I can't seem to get it to work anymore. Previously it worked fine, but I did a complete reinstall of my FS a few weeks ago or so and haven't installed the limiter since. After creating the .bat file, I double click it and the DOS screen pops up but then immediately closes again and FSX does not start. After launching it a few times, I noticed that the DOS screen says something like 'could not create game process' before it closes! I'm running FSX in DX9 mode so it could not be related to DX10 or whatever I guess.. for other specs, see my signature. Anyone one here to have an idea on this issue? Hope that having FPSLimiter working will have my FSX work like never before :)

After creating the .bat file, I double click it and the DOS screen pops up but then immediately closes again and FSX does not start. After launching it a few times, I noticed that the DOS screen says something like 'could not create game process' before it closes!

Sounds like the path to your FSX.EXE isn't correct in the file. That would give exactly that result. I've never used a Batch file, I just run fps limiter with command line parameters entered in the shortcut's properties, i.e like "/F:30 E:\FSX\FSX.EXE".Another thought. If you've let FSX install itself into "Program Files" or "Program Files (x86)" on Vista or Win7, then its folders are protected and that might be stopping FPSlimiter. You might need to run it "as administrator" in that case.RegardsPete

I've had that FPS problem before, and I think it was an issue with Java, try to update that, or maybe re-install FPS...Weird you folks get so mucho better performance with "the buff=0 tweak" !Anyhow... Nice to hear it's working for some...