Shared cockpit      " PMDG aircraft when they're updated for that"   -   that's never going to happen.

Can someone help a brother out? A good starting point would be much appreciated.

 

Thanks,

 

Matt

Take out the overclock. SpeedStep will run FSX just fine at 3.9 GHZ.

 

Dave

Negative, Ghost Rider. Don't take out the overclock. Overclock it more. I have my 3770K running at 4.6 with no issues.

 

As far as tweaking, Matt, stop what you're doing and head over to Word Not Allowed's FSX and P3D setup blog (the link is prohibited here). His guide is the best, most systematic and objectively tested guide to setting up FSX available anywhere on the internet. Thanks to Word Not Allowed, I'm running FSX with real weather via AS2012, NGX or Majestic Dash 8 Q400, FTX EU, UT2 at 100% and most settings near max and achieving 30 fps in most situations. At a busy airport (say Heathrow), I don't go any lower than 20, which is to be expected with 100% traffic at a large addon airport.

Update - after trying everything that was suggested, I still was getting poor results in DX9, so I decided to make the DX10 switch. Compatibility issues aside, the performance and looks of DX10 make the switch worth it. Still getting ocassional micro-stutters when using PMDG aircraft, which I'm sure I can iron out if I spend some time with inspector/FSX.cfg settings.

 

Again, thanks for the help guys. Next step is to get SweetFX going in DX10.

Remove the terrain fiber FFTF=.15 so it's going to default 33 or you could even make it larger ;-)

 

 

 

Not true. Raising FFTF allocates more time to the CPU for texture loading and thus decreases the framerate. To increase the framerate you should lower the FFTF as Matt has done. Of course, too low and you'll get blurries. The suggested minimum for Orbx textures is about .20.

 

See http://support.microsoft.com/kb/555738

 

Can someone help a brother out?  

Matt

I thought I was the only one, my parents never told me I had a brother :lol:    :Just Kidding:

Not true. Raising FFTF allocates more time to the CPU for texture loading and thus decreases the framerate. To increase the framerate you should lower the FFTF as Matt has done. Of course, too low and you'll get blurries. The suggested minimum for Orbx textures is about .20.

 

See http://support.microsoft.com/kb/555738

 

Nope you are wrong in this case lol read again he wants the opposite in the hope to bring the system in balance, so raising

the fiber you will have less stress on the GPU bus because FSX will take more time to render...

Normally you would leave it at default since it's running always on the first core or if a balanced system you could lower it to free-up resources

It's not about to raise the frame rate via the old fashion way but to bring a system in balance and gain FPS ;-)

 

I'm well aware of how to raise FPS and tweaks and hence what FSX is doing from a technical standpoint ;-)

On a well balanced system the fiber tweak is useless anyway...

Awf - you are dead on the money. After raising the fftf to .5 and TBM to 90 I get solid frames and a good balance of cpu/GPU work. Micro-stutters are a slightly different beast, and it seems like it's an nvidia inspector setting. Currently running 3.20 drivers with the latest inspector...1/2 refresh rate, aa and aniso controlled by fsx, frames locked to 30 inside FSX, and DX10 enabled. Stutters are only noticeable with heavy VC, I.E. PMDG. That's a lot of acronyms..

Polaris, try running FSX at unlimited framerate in-game and limiting to half-refresh externally.

 

Sent from my HTC6435LVW using Tapatalk 2

 

 

After installing the chip, I disabled hyperthreading in the BIOS. I started with a clean FSX.cfg and applied the tweaks that are found in the tweaking guide here at avsim.

 

I also use the NVidia Inspector and use the common settings found here and elsewhere. I have the GPU controlling the Antialiasing and Anisotropic filtering.

 

Matt, have you got the DX9 problems sorted yet?

What AA settings do you have set in Inspector? Are they exactly the same as you had with your old chip?

Pay close attention to what Word Not Allowed says about Vsynch . It completely solved my stutters. I have an Nvidia 650 2mb.

Pay close attention to what Word Not Allowed says about Vsynch . It completely solved my stutters. I have an Nvidia 650 2mb.

Yes, that's eactly what I tried to get across above. Much of the "what settings should I use" banter could be averted if folks would just head over to Word Not Allowed's blog with a fresh FSX install in hand and READ. His approach is systematic and has helped many people. Getting the [insert top of the line CPU of the day here] isn't enough. You have to set things up correctly.

I completely agree with you guys and for years have been following what used to be *******' tweaks, Word Not Allowed's guide, and now the new Avsim guide.  The problem I see when trying to do this is that, depending on which information you are listening to and when it was written, some of it is completely counter-intuitive.  In addition, so much depends on the exact hardware set up that you have - what is your proc speed, overclock, how many cores, what is your GPU, how much RAM do you have, what are your memory timings, DX9 or DX10, ATI or NVidia, inspector settings, etc, etc.  

 

The good thing is that we have so many passionate folks within the community that are willing to help and offer their experience and advice regarding what the possible remedies are.  I could spend hours, and have spend hours just browsing old posts to find out what might be causing a particular problem, and then spend hours tweaking the .cfg and graphics settings to find that perfect balance.  And to be honest, I actually love it, and that's why I continue to upgrade and tweak and fly some more.

 

I'm very lucky that I have been flight simming since I was about 10 years old back in the days of FS 4.0.  It must be quite a daunting prospect for someone just getting in to the hobby to sift through the madness.

 

With that, I would like to say thank you again to all of you and I feel pretty confident that we can close this topic....that is until the next user can't quite get it right :-)