Hey Guys.  I can't trace back to when this started, but I'm pretty sure it started in one of two places.  Either when I updated to 20H2 or more likely when I went from V5 to V5.1 HF1.  The stutters are not constant it's weird.  But I've had them in the 717, NGXu, FSLabs now.  Had them in day or night.  It looks like if it's not a setting/software thing it's the CPU and not the GPU.  In V5 i was butter smooth.  Now I've noticed on the ground during taxi I'll see choppiness.  Tonight I pushed back from the gate at YYZ.  My locked 30 was smooth and then almost immediately during pushback i saw it dip to 7.  Then about 5 seconds later it shot right back to the locked 30.  I'm really at a loss here.  I've tried:

-DDU'd nvidia driver and attempted today to use the newest to see if that would help (461.09 installed and still the same results)

-Deleted my p3d.cfg and let it rebuild

-deleted shader folder

-Turned off force feedback. (Should have been off anyway.  And as funny as it sounds I read somebody in another forum had an issue where it was causing problems. 

-My graphic setup that has worked for a long time from V4 all the way thru V5.0 has been to run unlimited frames in p3d/vsync on/tb on.  In NCP default but go under display/change resolution/refresh rate and set to 30hz.  My native is 60hz on my tv.  That setting has always resulted ins smoothness.  

I doubt it could be this, but would ticking enable full screen optimizations help?  I just turned clicked it on, but already in flight right now so can't do a full test until later.  

 

Like I said this appears to be CPU related as GPU has a lot of headroom and CPU seems to be maxing out.  When I upated to 5.1hf 1 i did the client+content+scenery separately.  Not sure if reinstalling is the way to go here.  All my usual tricks have not seemed to fix this.  Any help is appreciated.  

Edited January 8, 20215 yr by micstatic
fix

https://imgur.com/a/Ujz2kgQ  settings

I think I found it and will report back for anybody else with similar.  Unchecking the TB box

Edited January 8, 20215 yr by micstatic

Don't keep me in suspense! What is the "TB box"?

48 minutes ago, Christopher Low said:

Don't keep me in suspense! What is the "TB box"?

He means "TrippleBuffer" i guess.

So not "all of a sudden" how so often is asserted but "after fiddling with settings".

Edited January 8, 20215 yr by JoeFackel

@JoeFackel       I do mean triple buffering. And joe been doing this for a long time. I wasn’t fiddling with my settings. It was left on when I upgraded from 5 to 5.1. It was one of those issues that was causing me minor annoyance ever since. I only just started aggressively trying to track it down. Perhaps the reason it seemed all of a sudden is because 90 percent of my flying up until the last week or so was in the Q400 where performance is easy to be had. Then when I started flying the ngxu and others again it started sticking out. 

Check Enhanced turbo or MCE isn't set in bios Only the regular turbo is set as this was found to be auto/enabled and may have fried my cpu now resulting in cursor stutters even after formatting. Might help. You wont get the 5gig CPU speed but may save it from stuttering/frying. No silicon lottery here.

6 minutes ago, 40track said:

Check Enhanced turbo or MCE isn't set in bios Only the regular turbo is set as this was found to be auto/enabled and may have fried my cpu now resulting in cursor stutters even after formatting. Might help. You wont get the 5gig CPU speed but may save it from stuttering/frying. No silicon lottery here.

How do you know you fried your cpu?

I've found both vsync and triple-buffering can cause FPS problems or stutters sometimes, but it seems to be related to the display drivers rather than P3D itself - updating the drivers usually fixes it for me. 

I was having nasty stutters recently and turning off hyper-threading was the fix. I don't want to open that whole debate again, it's been done to death, but it was the only thing that improved performance, and pretty radically in this particular case. Just pointing out that it's always worth trying all the usual suspects when you have an unexpected performance problem. 

36 minutes ago, micstatic said:

How do you know you fried your cpu?

Continuous cursor stuttering on windows browser/screen in the last day , where as before i had no issues after a BIOS update the previous month. Don't quote me on it but just keep an eye on cpu temps when running into the 5 ghz speed and disable it if any issues with booting or windows start occurring. Enhanced doesn't mean disabling the entire turbo but my 10700k ran hot and hasn't faired too well with it over 5.0/5.1 So i had to now dial the turbo back to 4.7 and now I'm worried its fried or something. 

Edited January 9, 20215 yr by 40track

Yeah I run mine at 4.7 just to keep it from getting unstable or too hot 

5 minutes ago, 40track said:

Continuous cursor stuttering on windows browser/screen in the last day , where as before i had no issues after a BIOS update the previous month. Don't quote me on it but just keep an eye on cpu temps when running into the 5 ghz speed and disable it if any issues with booting or windows start occurring. Enhanced doesn't mean disabling the entire turbo but my 10700k ran hot and hasn't faired too well with it over 5.0/5.1 So i had to now dial the turbo back to 4.7 and now I'm worried its fried or something. 

Modern CPUs have thermal throttling and cut-out built in, though. I once ran a chip with (unknown to me) the CPU block not physically touching the TIM at all, and it ran fine but throttled instantly, and then eventually cut out, but no harm done and I'm still using that CPU years later. Certainly running at higher temps for longer reduces the working life of the chip and overclock stability, and CPUs do eventually wear out. I run the CPUs in both my sim machines at the max overclock they will sustain with speedstep and core parking disabled for max performance, and temps are certainly on the high side but not excessive thanks to good cooling. Still, I don't imagine they will last more than 3 years and I always plan to rebuild each rig with newer tech within that timeframe. I think it's part of the price we pay for needing higher single-threaded performance than almost any other use-case.  

7 minutes ago, neilhewitt said:

Modern CPUs have thermal throttling and cut-out built in, though. I once ran a chip with (unknown to me) the CPU block not physically touching the TIM at all, and it ran fine but throttled instantly, and then eventually cut out, but no harm done and I'm still using that CPU years later. Certainly running at higher temps for longer reduces the working life of the chip and overclock stability, and CPUs do eventually wear out. I run the CPUs in both my sim machines at the max overclock they will sustain with speedstep and core parking disabled for max performance, and temps are certainly on the high side but not excessive thanks to good cooling. Still, I don't imagine they will last more than 3 years and I always plan to rebuild each rig with newer tech within that timeframe. I think it's part of the price we pay for needing higher single-threaded performance than almost any other use-case.  

True about the 3 year life span and on the Thermal cut offs. As of now im just ruling out CPU/GPU or board fault here. Didnt think about core parking in windows. Im not trying to scare anyone just letting people know about it and keep a mindful eye on hardware throttling issues that may cause stutters. Yep did 2 upgrades this year alone (empty pockets as usual but simming is worth it).