Windows updates

 

I keep up to date, as we should, but haven't had any issues so far.

 

You could unistall all the new updates and test again, just in case one of them is being naughty. Or system restore of course.

 

Personally, I tend to listen to the consensus- and then see what works "for me". We all have different set ups.

 

For example, as soon as I updated to my previous system, I found I could lock frame rate at 60, and not experience very many stutters. Now, with my new Ivy Bridge system, overclocked to 4.5 GHz, I see perhaps one or two stutters the entire flight.

 

My new system is locked at 50 though. I found that BP=0 generated some artifacts, simply as a result of the massive amount of data that was been fed to the GPU, with no buffer. By simply dropping back to a 50 FPS lock, it was enough to eliminate all artifacts. And yes, I believe I could run at unlimited quite successfully.

 

So to sum up, conventional wisdom would have it that we must lock at 30 to avoid stutters. However- that does not apply if you have the latest overclocked kit, and importantly, don't fly into hyper detailed payware airports with FSX sliders up to max.

 

Additionally, it also depends on the particular scenario. Some so called FSX gurus, recommend unlimited for some scenarios and locked for others.

 

What you may have read is to set FSX to unlimited, and lock the frame rate with a thrid party frame rate lock.