Too early to say here but so far seems much improved.  Remember how that issue was sometimes hard to predict where the impact would be intense w/ SGSS4X and where it wouldn't be?  I've had that happen anyway in 2.3.  So far it's seems it's much improved but not certain if there aren't situations where it's still awful--but I have done some heavy clouds and don't see the impact nearly as bad.  Yesterday flew out of KPDX>KDEN and some sections of intense clouds and no impact whatsoever.

Am I confused, is SGSS4X more demanding than SGSS8X and are you talking about the setting in P3dv3.2 and not the Nvida setting correct?

Then i am in the same boat  , about 30-35fps at FB KSFO in the PMDG777 on runway 28L/R

 

Really amazing even at night

 

Great job by Flightbeam btw. Could or should be THE airport to visit in my own opinion.

 

Thanks

 

Michael Moe

That's much higher than I'm seeing--I think I was down to 23-24 during TO, but taxiing was in the 27-28 range.  It's very smooth though anyway over about 20.

Am I confused, is SGSS4X more demanding than SGSS8X and are you talking about the setting in P3dv3.2 and not the Nvida setting correct?

Using NI for SGSS4X.   The alternate was not using SGSS versus using SGSS4X.

Today I bit the bullet and installed the Client and Content update of the v3.2 update. I intended holding back and just wait and read users reports on their experiences, I got so excited from all the positive feedback and visual depictions on uploaded youtube videos I couldn't wait any longer. I did the update as per Poppets thread and exactly how I updated from V3 to v3.2.

 

The biggest obvious observation, after the install, is a huge drop in framerates and the return of the dreaded stutters. I had v3.1 tweaked perfectly, using mid range slider settings and framerates locked at 30fps. Long, flawless flights were the  norm.  I am at a loss as to what is happening. If I use an example flight from EGPH, Edinburgh to ENBR Bergen with UK2000 EGPH, ORBX, EU and NORWAY and FSDT Bergen, ASN and REX soft clouds. I use the 737ngx with Fs2Crew. I used to be able to do this flight maintaining 30fps occasionally dropping to 20fps over some heavy scenery areas. Now, with v3.2 I'm lucky to maintain 20 fps dropping to 13fps, and now stuttering has returned. I am using the same tweaked cfg file, I rebuilt the sliders.

 

I am open to any suggestions on what is happening and to hear from anyone else experiencing notable framerate drops after the update, or reduced performance

 

System is [email protected] and GTX680 OC (which performed beautifully under v3.1)

 

 

I am open to any suggestions on what is happening and to hear from anyone else experiencing notable framerate drops after the update, or reduced performance....System is [email protected] and GTX680 OC (which performed beautifully under v3.1)

 

Hi Steve,

 

Makes one wonder if something was not setup the same in your Prepar3D.cfg file maybe?  Did you use an affinity mask previously and not now?  If you're 100% confident your 3.2 setup is the same as your 3.1 was, I'd be inclined to uninstall all 3 components, reinstalled all three, and see if you can't get back to where you were and then some.  I wonder if some of the increased performance some are seeing (manifested as better behavior in clouds perhaps, smoother total performance, and more are from using more of the CPU in which case your GTX680OC may not have enough headroom to take advantage.  That's pure conjecture and probably not well founded!

Hi Noel,

 

Thanks for the reply, I'm sure about the cfg and settings I copied the cfg to another location and captured each screen of the settings screens to cross check after installation of 3.2. I have read of some user's experiencing a corrupt cfg caused by the install. I'm thinking that maybe my gtx680 might be bottle-necking, indeed I had planned on replacement prior to my last tweak in v3.1, but, those last settings improved performance where I was getting a solid frame rate and no stutters so I kept it. I'm thinking maybe it's time for a gtx980.

 

I'll see what develops as 3.2 use becomes more widespread.

 

 

are from using more of the CPU in which case your GTX680OC may not have enough headroom

 

Oops, meant to say GPU, but you got the point.  I think this is a hopeful if doubtful explanation for your troubles.  I can tell you with certainty though I had 3.1 only in for a very short time I believe 3.2 is the sim we've all been hoping for all along in terms of total performance.  I only had to reinstalled FTX Global--all my regionals stuck.  I had not yet installed any non FTX airports so those are in now.