Of course its a open discussion!Always has beenUp to a certain point what we had was.. "USE BP=0!!" and the explanation of how it worked was

but at least now we are looking in a direction that has the potential to define real merit with respect to those effected and how they may go about using it!thats all I was after :(

at least now we are looking in a direction that has the potential to define real merit with respect to those effected and how they may go about using it!

100% in agreement!, it was the result of 'healthy debate' and opinions by those who care and want to understand the impact of changing settings that affect how we enjoy our hobby!

100% in agreement!, it was the result of 'healthy debate' and opinions by those who care and want to understand the impact of changing settings that affect how we enjoy our hobby!

You should take very close note of what people like sargeski, Noel, wkd6, Flyingbits and tfm say in these forums.. like myself may not be guru experts in MSFS code but they have a VERY STRONG background in working with this title and tuning hardware, and, their powers of observation are very keen with respect to real results.and by all means.. tweak on! :(

Don't know if this explanation works for you.. I tried my best on using plain descriptive terms for the benefit of all.

Thank you, that is a very easy to follow argument. Indeed, I seem to have found a decent sweet spot. What I have never done yet is do anything with Vista other than disable UAC. I don't know if it's worth anything to make modifications beyond vanilla w/o UAC. I believed I have my memory timings well optimized, thanks to NickN. But I do run a fairly sluggy FSB by some accounts, at 405mHz quad pumped. Is there a compelling reason to play around with this area? CPU & memory timings I doubt I can improve safely. I fried another mainboard, which happened right after I o'cd the FSB to 440. It's made me afraid to go up much on my mainboard now, in part because I don't appreciate what role some of the various BIOS voltages play to harm/protect the NB or other components. I have such a poor understanding of the architecture of the various components (PCI bus, FSB, NB, etc) that I just don't have a clue what is "safe" and what is not. I don't want to fry another mainboard! What affects PCI bus bandwidth? Anything in my setup? I'm guessing not.I had audio popping problems with ANY driver since 182.50, which I guess points to latency problems on the PCI bus. The cure for this has been specifying lower BP settings. I was running default (not specificed) at 4MB. At 0, 1, or 2mb, I get no audio popping with the latest drivers. Gives me stereo 3D to play with ;o)I'm guessing one could spend some time optimizing Vista, and not see much in the way of gains (in smoothness or other aspects of FSX performance). But that is just a guess. I used to use Black Viper for XP and set up hardware profiles so that a super lean boot happened, so that there was no need for FSAutostart.

I've refrained from using the The DPC Latency checker thus far with the BP=0 setting because I have not experienced any anomlies while running FSX that would indicate high latency.However, this evening, just for kicks I performed mutiple runs in FSX with bufferpools set to 0, 4MB, 10MB, 50MB and 100MB while utilizing the DPC Latency Checker and as I would expect had the same results as Ulf. The latecncy was excellent and consistent across the different bufferpool settings. As I posted above, in a given situation with BP=0 flight is smooth anything else will result in some form of stutter/microstutter occuring some where during the flight.Thus far I only think the DPC Latency Tool is going to prove to some that they have latency issues and massaging the BP entry can reduce that latency for them. On the other hand the tool does nothing to explain why I get better performance with BP=0 on my system and Ulf gets better performance with a BP=10000000 on his system.Nils,I am curious as to exactly what your hardware specs are? I had the exact same problem when pushing FSX very hard when I was running a QX9650 on a Asus P5E3 Premiuim (The same CPU and MOBO combo Noel has issues with). Since going to an i7 and a P6T Deluxe v2 the issue is gone (all the other hardware in the computer is the same with the exception of the memory).

I have now upped my locked FPS to 40...and 2 sliders up 1 more notch...BP=0 has revolutionalized my FSX

And neither of us want that!! who likes 'mistery tweaks' that work because god knows what??? so you, UlfB, John, Stephen, Paul and countless others have in one way or another contributed to the discussion trying to 'understand' the implications of a particular tweak.

No,I participated because I got curious on this DPC tool and the figures that Nils got during his testing. This quest of yours regarding the BP=0 tweak started of very wrong (holy grail and such), but now it seems to be so many different variables and settings for the BP=0 to work fore some. It would be nice if somebody had the time, set of different computers and technical skills to perform a systematic investigation on this.I have excellent graphics quality and smooth flights in FSX without the BP=0 setting.By the way, here is a picture of Charlotte Kalla. A lovely swedish girl that yesterday performed a low altitude bush flying in Vancouver.

systematic investigation

And don't forget DPC Latency checker!

And don't forget DPC Latency checker!

I guess that DPC would only be one of the tools that a skilled technician would use. I wouldnt't be surprised if such an investigation should end up with a lot of variables that show some correlation with the BP=setting, but no proof to build a solid formula on. But that's only my best guess.

I am curious as to exactly what your hardware specs are? I had the exact same problem when pushing FSX very hard when I was running a QX9650 on a Asus P5E3 Premiuim (The same CPU and MOBO combo Noel has issues with). Since going to an i7 and a P6T Deluxe v2 the issue is gone (all the other hardware in the computer is the same with the exception of the memory).

Despite any issues which I think now are just the limitations in this as in all platforms, I have pretty dang good performance by all measures ;o) I will be staying with this combo for another year or two, after which all bets are off!Noel

By the way, here is a picture of Charlotte Kalla. A lovely swedish girl that yesterday performed a low altitude bush flying in Vancouver.

:--))))))She is indeed lovely and probably doesn't have any problem of latency!!!!

I've refrained from using the The DPC Latency checker thus far with the BP=0 setting because I have not experienced any anomlies while running FSX that would indicate high latency.However, this evening, just for kicks I performed mutiple runs in FSX with bufferpools set to 0, 4MB, 10MB, 50MB and 100MB while utilizing the DPC Latency Checker and as I would expect had the same results as Ulf. The latecncy was excellent and consistent across the different bufferpool settings. As I posted above, in a given situation with BP=0 flight is smooth anything else will result in some form of stutter/microstutter occuring some where during the flight.Thus far I only think the DPC Latency Tool is going to prove to some that they have latency issues and massaging the BP entry can reduce that latency for them. On the other hand the tool does nothing to explain why I get better performance with BP=0 on my system and Ulf gets better performance with a BP=10000000 on his system.

Thanks for posting results, I was hoping you would.Therefore we are most likely looking at a combination situationa. Driver level + hardware which includes chipset/BIOS combinationb. OS driver model + hardware combination (can not rule out BIOS either)I agree and suspected this may be on the same lines at the sound crackle issue whereby some users are seeing results based on latency issues with their system they were not aware of and another category of users who have a key combination of hardware/drivers/OS which is why I posted earlier in the thread, this may come down to a trial and error check.The use of the tool is undefined at this point. I am hoping with enough reports we can isolate the common factors and see if the use of the tool may at the very least provide clues

Thanks for posting results, I was hoping you would.Therefore we are most likely looking at a combination situationa. Driver level + hardware which includes chipset/BIOS combinationb. OS driver model + hardware combination (can not rule out BIOS either)I agree and suspected this may be on the same lines at the sound crackle issue whereby some users are seeing results based on latency issues with their system they were not aware of and another category of users who have a key combination of hardware/drivers/OS which is why I posted earlier in the thread, this may come down to a trial and error check.The use of the tool is undefined at this point. I am hoping with enough reports we can isolate the common factors and see if the use of the tool may at the very least provide clues

This is absolutely totally OT, but NickN, I've been wondering for quite some time now why your posts always have so many hard returns and completely empy lines in them...! Every time you post something, half of the space is empty! I know, I know, yes, asking this it totally OT and completely uuterly useless, but I just had to ask it, in all seriousness (as far as such a question can be serious, of course!): only your post contain that much space! Sometimes I am TOO curious... :(

This is absolutely totally OT, but NickN, I've been wondering for quite some time now why your posts always have so many hard returns and completely empy lines in them...! Every time you post something, half of the space is empty! I know, I know, yes, asking this it totally OT and completely uuterly useless, but I just had to ask it, in all seriousness (as far as such a question can be serious, of course!): only your post contain that much space! Sometimes I am TOO curious... :(

I have no idea what you are talking aboutthis is an image of what I see with my post above if you see something different then that would be a prime example of why it is difficult at best to sort out issues across a span of hardware and OS/driversIf what I posted above looks correct and matches my original post then I have no clue what it is you see that is wrongof course if the image and what I posted match then that may explain a few things with settings and FSX results you see too :(J/K

I think what he meant Nick was why you put so many empty lines between paragraphs. Sometimes there are up to 5 empty lines between the start of a new paragraph. Like after you end a paragraph, you press the return key 5 times before starting a new sentence. I have often wondered this myself for the last few years but never gave any consideration to ask you why since it doesn't really make any difference.