Its shame that in 5.3, we have to still "play" with cfg files again... Hey, it's 2021 

On 12/11/2021 at 11:53 PM, DonMuskopf said:

Up until now, I have always had to lock my frame rate at 30 to 35 FPS to keep the LP0 utilization rate below 100% and free up CPU resources. The most effective way to this for me was setting the Max Frame Rate in NCP to 35 and setting the P3D Target Frame Rate to 120 FPS or Unlimited.

To my amazement in v5.3, I now find that if I turn off the Max Frame Rate setting in NCP and set the P3D Target Frame Rate to Unlimited, LP0 utilization drops from 100% when it was locked at 35, to 50% to 60% at unlimited.

I know this makes no sense, but this is what is happening for me. Can anyone else duplicate this?

What is happening, is that if you lock your FPS at less than the FPS you would get with the Target Frame Rate set to unlimited, then LP0 utilization will jump to 100%.

For example, if FPS is 50 when the Target Frame Rate is unlimited, but you had capped your FPS to say 40, LP0 utilization jumps to 100%. On the other hand, if you set your FPS above 50, say 60, LP0 utilization will drop significantly below 100%. So setting your Target Frame Rate to unlimited will keep your utilization below 100%, if your system is capable of it.

Well, HF1 fixed this problem for me. I can now lock my frame rate at 35 FPS and keep the LP0 utilization rate below 100%. My LP0 utilization rate is now in the 50% to 65% range, even better than v5.2. As far as performance goes, I'm a happy camper again.

5 hours ago, DonMuskopf said:

Well, HF1 fixed this problem for me. I can now lock my frame rate at 35 FPS and keep the LP0 utilization rate below 100%. My LP0 utilization rate is now in the 50% to 65% range, even better than v5.2. As far as performance goes, I'm a happy camper again.

Locked at 35 in the sim or NCP?

On 12/13/2021 at 9:42 AM, gaab said:

Yes and No 😉

This and other symptoms are pushing me toward a full Windows re-installation 😞

And I hate this idea..

Any way - thank you for taking the time to test and answer.

Gérard

Just to let you know that full clean Windows 10 re-install (including C formatting) was the solution.

It's like I have a brand new PC 🙂

Gérard

Edited December 22, 20214 yr by gaab

Removing core O load just passes this on to another core and todays Multi core CPU you may end up on a weaker core, you will always have a main core that runs as master. 

https://www.flickr.com/photos/154944674@N05/51765522590/in/dateposted-public/

 

Edited December 22, 20214 yr by G-RFRY

8 hours ago, CaptKornDog said:

Locked at 35 in the sim or NCP?

Target Frame Rate in P3D 120. NCP Max Frame Rate 35.

 

4 hours ago, G-RFRY said:

Removing core O load just passes this on to another core

In general, capping your frame rate takes a load off your CPU and reduces the load on your graphics card. Instead of both working hard at maximizing your frame rate, more resources are freed to address other things like AI traffic or scenery loading.

4 hours ago, G-RFRY said:

you will always have a main core that runs as master. 

This is true. When I say LP0, I am referring to the main thread.

On 12/12/2021 at 4:13 PM, dave2013 said:

This didn't work for me.  Core 0 still maxed out at 100%.

I have a core i7 9700K with 8 cores, no HT.  I have the target frame rate unlocked in sim and use Nvidia settings to limit max frames to 33/sec.

I set my Affinity Mask and CoreP3DAffinityMask to 127, or 01111111, to avoid using core 0.  This setting did actually reduce the load on core 0 as its utilization stays between 90-95% most of the time, whereas before it was always 100%.  Now, if I don't limit frames to 33/sec using the Nvidia settings, core 0 stays pegged at 100%.  P3D loves using core 0.

I also tried setting the MainThreadScheduler to core 7, but as soon as P3D is started this setting is forced back to 0.

Dave

Try 254 that's what I use with my 9700k . P3D v5.3 doesn't use core 0 at all 

4 hours ago, sonny147 said:

Try 254 that's what I use with my 9700k . P3D v5.3 doesn't use core 0 at all 

Yeah, that's what I did.  Now Core1 is heavily utilized.

I haven't noticed any performance improvement or degradation so I'll just leave it at 254 for now.  Time to give core0 a break!

Dave

Depending on the CPU, that might not be a good idea. On some of the newer Intel CPUs (generation 8 upwards), the CPU overclocks itself when it considers that it is safe to do so. Download something like CPU-Z and run it: on a CPU that is ostensibly clocked for 3.5Ghz, you'll find the CPU hitting anything up to 5.0 GHz. On some CPUs it is just core zero, but on others it applies to all cores. I have an i9-9900KF 'Coffee Lake' CPU in here which is sold at 3.6GHz; currently CPU-Z says it's busy banging away at between 4.6 and 4.8Ghz with no overclocking from me. Even Windows Task Manager says it's running at 4.5Ghz.

The long pauses and stuttering that seems to randomly occur are still present with the latest version. LM still has a lot of work to do. 

Stuttering + Freezing Still Occurring - Prepar3D Forums

5.2 perfect, 5.3 long pausing and stuttering is unflyable - Prepar3D Forums