I, like sargeski, also tried FalconAF's high priority tweak, but it didn't make any difference if i don't use BP=0. Just BP=0 and TBM=60 does it for me. Smooth sttuter free flight anywhere.

J van E: I know it may not work for "everybody". I'm not stupid. However, my post was designed to get "everybody" to TRY it and see if it solves their problem. That is no different than what this whole darn THREAD...now over 7 pages long...is doing by getting "everybody" to try the Bufferpools and Affinity Mask "tweaks". If "my" solution...which is a lot simpler than "tweaking" those two settings for hours on end...solves the problem, then there is no need to "tweak" anything. THAT is the point of my post...and why I spend MY time making these kind of posts.

No, I still won't try it past the affinity mask and bufferpools. :( Anywho, I don't remember NinckN ever suggested to change the pirority.Thanks for the ideas, guys. They are all worth to try out and find the one dear to your heart.Dirk.

Anywho, I don't remember NinckN ever suggested to change the pirority.

With all the respect and the friendship which comes to Nick, he is not (and I'm sure wouldn't like to be) a guru.There is also a bunch of talented guys with technical skills around here and Nick never pretended holding the one and only truth and knowledge.Personaly I think there is a serious drift following word for word anyone's advices.I believe we should try, tweak by ourselves, learn from other but not following blindly anyone's biblical words :--))Just my two cents!

......Guys, I've done IT for over 35 years. Been flight simming since the Commodore 64 came out......

Many of us have the same level of experience in "IT", not that it is the same field today as it was 35 years ago. I have worked on, supported, and developed programs for PC's since their introduction. Same as you. I've been simming as long as you. In my career I rose from a lowly desktop support role to Team Lead on the largest network rollout in history (at that time) and traveled the four corners of the earth plying my trade. Now that I have a family (I had mine late in life), I don't travel any more but I am still working as a Senior Engineer. Microsoft allowed me to be on the FS2004 and FSX betas. I've served time as a mod on these forums, and used to (when I had the bandwidth) offer technical advice as often as I could. And you know what? None of that matters when it comes to our hobby because the page gets rewritten with every new add-on, hardware release, peripheral release, and so on. There is no "certification" in FSX. Everyone's platform and mix of programs, sim add-ons, and added hardware is different. Nothing should prevent one from coming in here with a tweak, someone flying FS-X as long as we have, and offer their tweak without someone trying to rain down their "experience" in their thread as the voice of reason. And I should know, I used to do the same thing here and was called out by some very young and enthusiastic simmers who offered good ideas. I didn't reply to your post to flame you, just to comment on your thoughts.You could have opened your own thread and offered your suggestion. I am sure some would have thanked you for it, some would have pointed out it's been offered before, some would have said it helped them, some would have said it hadn't, and some would have accused you of pushing snake oil. Get the picture? Instead you entered this thread and posted a thinly veiled put down of the OP in the process. Some members may not be as articulate as other members here, but we're all equals in this forum when it comes to our passion for the hobby. -John

With all the respect and the friendship which comes to Nick, he is not (and I'm sure wouldn't like to be) a guru.There is also a bunch of talented guys with technical skills around here and Nick never pretended holding the one and only truth and knowledge.Personaly I think there is a serious drift following word for word anyone's advices.I believe we should try, tweak by ourselves, learn from other but not following blindly anyone's biblical words :--))Just my two cents!

Amen!

And you know what? None of that matters when it comes to our hobby because the page gets rewritten with every new add-on, hardware release, peripheral release, and so on. There is no "certification" in FSX. Everyone's platform and mix of programs, sim add-ons, and added hardware is different. Nothing should prevent one from coming in here with a tweak, someone flying FS-X as long as we have, and offer their tweak without someone trying to rain down their "experience" in their thread as the voice of reason. And I should know, I used to do the same thing here and was called out by some very young and enthusiastic simmers who offered good ideas......Some members may not be as articulate as other members here, but we're all equals in this forum when it comes to our passion for the hobby. -John

Amen and Amen!Stephen

About your high priority suggestion, you have to set it everytime you start FSX ?Ulisses

On my system I use a simple two line Batch File:cd /d "G:\F_S_X"start /high fsx.exeThe first line changes directoty to the FSX folder, the second line starts FSX with High priority.I've changed my FSX shortcut to run the batch file instead of FSX.EXE.

These are just some results with my System (see profile), using Orbx's YMML, DX9, ENB series mod.

Hi Nils,interesting enought I don't see *ANY* change in latency either... regardless of BP value, are you using SLI? is your northbridge/BIOS set to Auto/16x or 8x for the PCI-e bus?? the ONLY thing which (in my opinion) changes when using different BP values is the PCI-e bus for your video card... if you are using 8x (under SLI mode) this could be the case! OR if for some reason your mother board is defaulting to 8x instead of 16x.I don't use YMML, however... Manhattan X at dusk with foggy weather plus rain and REX2, UTX, GEX is also taxing on any system!

Which version of Vista do I set the compatablilty for? I have W7, and I have choices for Vista, Vista SP1, Vista SP2. Do I just choose Vista, or what?

What's your GTX285?1 or 2 Gb.?

1Gb

Which version of Vista do I set the compatablilty for? I have W7, and I have choices for Vista, Vista SP1, Vista SP2. Do I just choose Vista, or what?

Doesn't matter. All Vista compatibility modes revert back to WDDM 1.0, but.. I would test with Vista (SP2). Besides, there IS a performance impact, yes, insignificant, but THERE IS ONE. WDDM 1.1 seems to have problems 'swaping' video memory, probably because it is a less mature driver architecture than 1.0, I would investigate further, but I think I'm getting tired of making comments and having a bunch of sarcastic folks come here and argue without ANY KIND of techincal facts the validity of the claims made by me or other posters... I can't believe well established members would say 'It doesn't work because Phil said so' or worst.. call 'Gems' advise which is EVIDENTLY misleading.

******* + Ulf,Thanks, i'm not using SLI, im using the latest drivers, everything is configured properly and the BIOS is also correctly configured and the latest version for my board.There is no BIOS option to change the PCIe rate (i've also checked with strg+f1) and GPU-Z and the NV driver are reporting PCIe 16x.If i use FSX in Vista SP2 compatibility mode, i can use BP=0 without getting red spikes. I've tested many drivers, disabled everything i could (sound, network, usb..), plugged the GTX260 into the second PCIe slot, which is also PCIe 16x 2.0, but i'm still getting those spikes with FSX.According to WPT the nvlddmkm.sys (nvidia) seems to be the culprit but i think it's more a bad correlation between some components and Win7.

******* + Ulf,

Weird indeed... One more suggestion, I'm pretty sure you are well are aware that motherboards share IRQ, buses, PCI bus bandwidth depending on the SLOT a cards is positioned right?Have you tried the option in BIOS that says NOT to use a PnP OS? and what about removing all cards and testing only with Video Card and on-board sound, will it make a difference? SOMETHING is swamping the bus, and If I had the problem, the VERY FIRST thing I would try is 'Sound card' and/or IRQ, address space assignments.

Doesn't matter. All Vista compatibility modes revert back to WDDM 1.0, but.. I would test with Vista (SP2). Besides, there IS a performance impact, yes, insignificant, but THERE IS ONE. WDDM 1.1 seems to have problems 'swaping' video memory, probably because it is a less mature driver architecture than 1.0, I would investigate further, but I think I'm getting tired of making comments and having a bunch of sarcastic folks come here and argue without ANY KIND of techincal facts the validity of the claims made by me or other posters... I can't believe well established members would say 'It doesn't work because Phil said so' or worst.. call 'Gems' advise which is EVIDENTLY misleading.

Bejote,My friend, there are many more silent people that respect good advice than the outspoken who mock it. This is like a large room filled with many different kinds of people, each of whom bring and display all their individual character strengths and weaknesses for the others to experience. Please don't let those who act negatively change the way you react positively. We need smart people like you to help not so smart people like me, so please just shrug it off and tell us about any other ideas you may have. Stephen

not so smart people like me

Thanks Stephen, however:1) By your actions2) Comments3) Willingness to try new things without braking anything4) and for keeping your cool even with the hasty comments some members makeI think you are a lot smarter than pretty much most of us :) I can't keep it cool and I find myself being sarcastic and/or confrontational sometimes.. I really appreciate your kind words... back to flying :)

Weird indeed... One more suggestion, I'm pretty sure you are well are aware that motherboards share IRQ, buses, PCI bus bandwidth depending on the SLOT a cards is positioned right?Have you tried the option in BIOS that says NOT to use a PnP OS? and what about removing all cards and testing only with Video Card and on-board sound, will it make a difference? SOMETHING is swamping the bus, and If I had the problem, the VERY FIRST thing I would try is 'Sound card' and/or IRQ, address space assignments.

That's why i had disabled everything i could and why i plugged the GTX into the second PCIe graphics slot ;)I have no other extension cards (PCI or PCIe) and i see no way to change the shared IRQs. But i've already disabled the onboard sound, onbaord LAN, USB, and jmb36x via the BIOS and the problem persists.So... i will buy a new system.. i'm tired of this sh##..