No truer words were ever posted here or anywhere else, but that also applies to a 60 Hz refresh rate. No tweaks or other silliness are needed to make P3d run smoothly, except the above advice. People don't like this type of advice because it's both easy to understand and expensive. Either one has to come to grips with the fact that one's hardware can't handle maxed out settings or one has to go out and buy  new hardware. 

 

This goes for XP10 also. And I can't wait until "the end of the year" when the DTG Flight Simulator is released and people make the same blunders with it also.

Have to agree with your initial comments Jay but - as for the last sentence..... 'blunders'? .... What are you anticipating?

Have to agree with your initial comments Jay but - as for the last sentence..... 'blunders'? .... What are you anticipating?

I'm pretty sure he was referring to people continually pushing more eye candy than what their equipment can maintain (we all do it, do we not?)  

To be more fair to the frustration of simming, the line between software and hardware is blurry. We often don't know whether it is hardware problem, or some kind of software problem that is not really our fault.

but the key to successfully utilize 30Hz approach is to establish a balance between YOUR hardware and P3D settings to maintain 30 FPS.

 

You have to define what balance is and what the line between hardware and software is. I suggest that the "truth" be re-written as:

 

....but the key to successfully utilize 30Hz approach is to establish a personally acceptable level at which you are getting 30HZ most of the time, then once you have determined what the faults and limits of the underlying software are, then find a balance between YOUR hardware and the P3D settings to maintain 30 FPS.

Have to agree with your initial comments Jay but - as for the last sentence..... 'blunders'? .... What are you anticipating?

If the DTG Flight Simulator is everything that has been promised, it will be a 64 bit version of FSX with a state of the art graphics engine. Seriously, does anybody think that the same small group of people will show restraint with their 4 year old PCs and run the new sim at modest settings? Nope, they will make the same "blunders". They will slap on all available add-ons and push the settings to the max. They will "discover" undocumented tweaks and throw that into the fray. And then when the sim is brought to its silicon knees, they will whine to DTG that it crashes, stutters and siphons money from their bank account. Fortunately, most people that use flight simulators are more thoughtful than that. They might experiment with "overkill" settings, but in the end, they will either settle for a compromise IQ or they will buy new hardware. It will happen. And there will a Rob A. who will try to be the voice of reason regarding the DTG sim.

 

It's just human nature. If it's broke try to fix it. If it isn't broke, then try to break it.

It's just human nature. If it's broke try to fix it. If it isn't broke, then try to break it.

MUST encase this in plastic and keep in wallet!

 

So true!!!

 

Vic

jabloomf1230, on 19 Mar 2016 - 12:13 PM, said:

It's just human nature. If it's broke try to fix it. If it isn't broke, then try to break it.

I disagree that it is human nature. If that were true, then we would all not accept that the lights in our house are working to provide light - we would deliberately smash them so as to put new light globes in?

 

No, it is because of expectation. We push the simulator to the limits because we expect more performance than we are getting for nothing, because we think that the performance we want is the performance that everyone else is already getting (the pilots we never meet).

 

EDIT: or the performance we believe "ought to be justified".

-------------------------------------------------------------------------------------

 

Anyway, the ANSWER to my originally posted problem:

 

It was the video driver. I installed the latest from nVidia, 364.xx.  My friend Thomas told me that the 364.xx series were bad on his system -- lower frame rates and bad stutters -- and that he'd gone back to 361.43 and it solved all that.

 

So I tried that ... and it made all the difference!

 

Pete

 

Thank you, thank you for this hint!

I had exactly the same issue, hesitations of about 1 sec. I thought it was a newly installed scenery, but now I reverted also back to 361.43 drivers.

 

 

After v3.2 my performance is very bad.

 

 

I'm finding this too.  Cloud seems to induce stutters more than with any previous version for me.  It's actually unflyable.

Stutters are caused by AI Traffic. Turn it off and you will see.

If the DTG Flight Simulator is everything that has been promised, it will be a 64 bit version of FSX with a state of the art graphics engine. Seriously, does anybody think that the same small group of people will show restraint with their 4 year old PCs and run the new sim at modest settings? Nope, they will make the same "blunders". They will slap on all available add-ons and push the settings to the max. They will "discover" undocumented tweaks and throw that into the fray. And then when the sim is brought to its silicon knees, they will whine to DTG that it crashes, stutters and siphons money from their bank account. Fortunately, most people that use flight simulators are more thoughtful than that. They might experiment with "overkill" settings, but in the end, they will either settle for a compromise IQ or they will buy new hardware. It will happen. And there will a Rob A. who will try to be the voice of reason regarding the DTG sim.

 

It's just human nature. If it's broke try to fix it. If it isn't broke, then try to break it.

 

And then after they get DTG's sim  all tweaked out Steam will do one of their favorite updates that one is forced to accept, and all your tweaks will disappear instantly.    Don't ask me how I know.  

Thank you, thank you for this hint!

I had exactly the same issue, hesitations of about 1 sec. I thought it was a newly installed scenery, but now I reverted also back to 361.43 drivers.

I've gone back to these drivers, I can now stay within 2-3 frames of locked 30 fps instead of dropping to as low as 22 fps (running Real Air Turbine Duke with ASN at Orbyx KJAC). I'm very happy with what I have now. I keep restarting just to be sure it's not a fluke.

Stutters are caused by AI Traffic. Turn it off and you will see.

 

 

I have no AI traffic, no planes, no cars.  I'm purely testing out my fresh install from yesterday

 

This is around Sandane (default airport) in FTX Norway today with real weather using ASN - Carenado Navajo.  Nothing too onerous.   When I climb toward or through cloud. REX soft clouds too. Stutterfest.   My previous install could manage this.   P3D gives and P3D takes in equal measures it seems. All things being equal.  

nVidia actually recalled that 364.47 driver about a week and a half ago...was buggy and unstable for a lot of people besides us flight simmers.  There's supposedly a new beta out in that series, but no WHQL-certified versions yet.

 

http://www.techpowerup.com/220760/nvidia-pulls-geforce-364-47-whql-driver-over-critical-bugs-outs-364-51-beta.html?cp=2

 

So...with that said, I'm still on 358.50 with a dual SLI 980Ti configuration.  Anyone using a later driver with SLI and P3D 3.2 they'd recommend?

 

Regards

I have no AI traffic, no planes, no cars. I'm purely testing out my fresh install from yesterday

 

This is around Sandane (default airport) in FTX Norway today with real weather using ASN - Carenado Navajo. Nothing too onerous. When I climb toward or through cloud. REX soft clouds too. Stutterfest. My previous install could manage this. P3D gives and P3D takes in equal measures it seems. All things being equal.

Do you have FPS problem?

Do you have FPS problem?

0

Selective Quote

Quote

MultiQuote

 

Yes. FPS drops to the low teens at times. My video card is a 970gtx 4gb.