I'm new to FSX and in the process of getting my system set up properly. I've been doing alot of reading and research, and following Word Not Allowed's wonderful guide.

 

I had a question regarding VSYNC....

 

Most of the information I read assumes you have a standard monitor refresh of 60Hz, thus will show up to 60 FPS, and thus it seems common to lock your FPS at 1/2...or 30 FPS.

 

What if you've got a refresh of 120Hz, and thus will show up to 120 FPS. Should I lock my FPS at 1/2 of that...or 60 FPS? Or should I stick with the lock at 30 FPS anyway?

 

Thanks!

I switched my FPS lock off... Left it to "unlimited" as I found with it locked to 30FPS, it was stuttering slightly and dropping to 22+ frequently, but once unlocked, it flew super smooth at 45FPS the entire time.

 

Funny how what works for some, doesnt for others with this old banger of a flight sim we all love so much...

Thanks guys. And Thanks for writing that excellent guide Word Not Allowed! That really helps a newbie like me. I'm still working my way through it and my FSX install so far is basically stock. I don't even have that Nvidia Inspector. But that guide is sure helping.

 

That whole "Lock your FPS at" concept is a bit new to me. I'm very familiar with vsync but I haven't seen many games or other sims that have a slider to lock the frame rate. I understand the concept though.

Hiya Word Not Allowed

 

Funny you should say this because my PC is now very well balanced, and my FSX setup is also now well balanced too (Thaks to your guide), yet I'm finding it far far smoother with unlocked frames..

If I lock the frames at 30, it regularly keeps dropping to 22/24fps during flight and stuttering, yet left unlocked, it does its own thing, runs at 45+ and is super smooth.. Feels very balanced to me..

 

I still have more add-ons to re-install yet too though..

I have found that there is no one guide that can apply to everyone's individual hardware/software/installation.

 

On my last PC (Core2Quad), Word Not Allowed's guide worked to the letter for me, and gave me 10 FPS more than the Bojote tweak site.

 

Since I got an i7 and switched to an ATI card (This is no offence to Word Not Allowed and I'm sure he knows this!), Word Not Allowed's guide gives me 18 FPS, in a FSX scenario with the NGX and OPUS, where Bojote's tweaks gives me 30 FPS. :smile:

 

Yesterday, I was reading a thread where Rockliffe and others were saying they got much higher FPS by putting the AF to "application controlled" in their GPU panel settings, and turning it on in FSX. I had previously had my GPU control overridding FSX for AF, so tried the above - and immediately saw a FPS reduction of 50%! .......... :lol:

 

So it is just horses for courses, I believe.

 

With my i7 2500k, I have found that no [AffinityMask] setting works well at all for me. I have tried all the suggested values and all lead to a decrease in FPS, versus not having an [AffinityMask] setting.

 

I think most guides are more biased towards nVidia users (probably fair as a lot more people use nVidia than ATI it seems). But a lot of tweaks (such as the above AF example) respond very differently between ATI and nVidia cards.

 

Bojote's tweaks give me by far the highest performance gain against 'stock' as a i7 2500, ATI 5770 HD, Win 7 64bit user.

 

But for others, (like myself when I had my Core2Quad and an nVidia 8800GTX), Word Not Allowed's recommendations delivered the best results.

no one guide that can apply to everyone's individual hardware/software/installation.

Absolutely, it does seem that way, but we all have a lot to gain in the detailed explainations in Word Not Allowed's guide :-)

Even if it doesnt improve your situation, it will help improve your understanding of whats going on, and possibly why what is working for him may not work you another, and that I think is the critical bit..

 

Word Not Allowed goes into great detail on what everything is, whereas others just throw a bunch of code at you with no explaination of what your looking at or why they use specific numbers, thus you still have nothing to understand about what your doing, so at the very least, Word Not Allowed's guide gives you an understanding into what your actually messing about with, and why :-)