57 minutes ago, Nemo said:

Just to come back to my original statements. I've never questioned that Core0 should not be using 90-100% most of the time. But full 100% all the time, no matter what settings or location, locked or unlocked frames, does not look right to me. Why?

1. My own experience. It was not like that (always 100%) after 4.5HF. I know because I made a lot of performance testing after 4.5HF came out.

2. Just look at Rob's Honolulu video, you will recognize that core0 is not always at 100%. But I don't know his settings.

Use Locked 20 with all sliders to the left  with your most heavy scenery + most heavy AC + most heavy weather conditions. 

Check your cpu core 0 load. It should be less than 100%.

Start adding detail with your sliders till the cpu core 0 load is at 95-100%.

With the exception of this most heavy scenario you wil always have some headroom.

Just now, GSalden said:

Use Locked 20 with all sliders to the left  with your most heavy scenery + most heavy AC + most heavy weather conditions. 

Check your cpu core 0 load. It should be less than 100%.

Start adding detail with your sliders till the cpu core 0 load is at 95-100%.

With the exception of this most heavy scenario you wil always have some headroom.

You're missing the point. For some people, the CPU 0 is at 100% all the time no matter what the load is even when P3D is "idle" or the FPS is locked at 20FPS and all the sliders are to the left. I just checked exactly what you said above... CPU 0 was not less than 100%.

I'm kinda confused by some statements. If LM did that intentionally and it serves a purpose why everybody is not experiencing the exact same thing? 

1 hour ago, Tomaz Drnovsek said:

You're missing the point. For some people, the CPU 0 is at 100% all the time no matter what the load is even when P3D is "idle" or the FPS is locked at 20FPS and all the sliders are to the left. I just checked exactly what you said above... CPU 0 was not less than 100%.

I'm kinda confused by some statements. If LM did that intentionally and it serves a purpose why everybody is not experiencing the exact same thing? 

Then it might be something on your end .A not correct installed Windows update for instance. Did you try with a clean cfg file and clean Shaders ?

 

20 minutes ago, GSalden said:

Then it might be something on your end .A not correct installed Windows update for instance. Did you try with a clean cfg file and clean Shaders ?

 

No, it is supposed to be something on the LM side.

23 hours ago, JoeFackel said:

as far as i can recall NOT recommended by LM.

Would you be so kind and provide a link where LM is not recommending that.

48 minutes ago, Tomaz Drnovsek said:

Would you be so kind and provide a link where LM is not recommending that.

Somewhere in their forum, can't find the post from Beau with a quick search.

4 hours ago, GSalden said:

Use Locked 20 with all sliders to the left  with your most heavy scenery + most heavy AC + most heavy weather conditions. 

Check your cpu core 0 load. It should be less than 100%.

Start adding detail with your sliders till the cpu core 0 load is at 95-100%.

With the exception of this most heavy scenario you wil always have some headroom.

...

Then it might be something on your end .A not correct installed Windows update for instance. Did you try with a clean cfg file and clean Shaders ?

That's more or less exactly what I did ...all sliders left, locked @ 20 fps (or unlimited) at default location with default a/c, new .cfg, deleted shadercache, ...  CPU0 = no headroom at all, full 100% all the time. I also don't see any background process hammering it. Only P3D. And that's why I find it a bit strange.

Please note, I don't complain about performance. I have stutters here and then (who has not) and low fps in demanding areas, but overall it is ok. But I also don't know if it could be better without CPU0 @ 100% all the time.

Edited September 18, 20196 yr by Nemo

To everybody who is suggesting to lower the settings - please understand the following: if we do the toggle thing (off/on) than CPU 0 is no longer at 100% but in line with all other cores! So it's not at 100% because of too much load from P3D but, as some here indicated, because LM intended that sort of behavior. What I don't understand is why everybody is not experiencing the exact same, CPU 0 at 100%, behavior, if that is indeed the case?

Edited September 18, 20196 yr by Tomaz Drnovsek

All these years and people still wonder about the P3D single core usage 🙂

17 minutes ago, swiesma said:

All these years and people still wonder about the P3D single core usage 🙂

That's not the point. Some of us have full 100% all the time - not 99 or less. Others have fluctuating high values ranging from 80 to 100%. Why?

35 minutes ago, Nemo said:

That's not the point. Some of us have full 100% all the time - not 99 or less. Others have fluctuating high values ranging from 80 to 100%. Why?

Ask LM .

On 9/17/2019 at 8:31 AM, Tomaz Drnovsek said:

Just toggle CPU 0 off/on in Set Affinity in Task Manager and it won't be running at 100% anymore.

It may be convenient to just "touch" Affinity with a simple PowerShell script:
$Process = Get-Process Prepar3D; $Process.ProcessorAffinity=16777215;

Save this one line script as TouchAffinity.ps1 and run with PowerShell while Prepar3D is running.
I'm looking for a good way of executing that automatically from Prepar3D right after start.

Some comments:
16777215 is a decimal equivalent of 24 binary "1" - for 12 cores = 24 threads)
Using 16777214 mask (23 binary "1" + "0") in [JOBSCHEDULER]  section of Prepar3D.cfg prevents utilizing CPU 0 but Prepar3D will load CPU 1 to 100%.

I tried P3Dv5 - it does exactly the same - CPU 0 load = 100%.

54 minutes ago, Xingent said:

I tried P3Dv5 - it does exactly the same - CPU 0 load = 100%.

V5 uses CPU cores differently than V4.. so not everything that we learned in V4 is applicable.

Secondly, if you have Unlimited fps set in P3D, and Core0 is heavily loaded, you can limit fps in Nvidia NCP and your Core0 usage will drop..  I have mine set to 29 fps, and my Core0 is running at 40-60% load..

Please read the entire post. The situation that I described is an error, obviously. "Touching" affinity without changing anything gets the program to work normally, i.e. without that strange CPU 0 100% load. This may be P3D or Windows fault but it does not result simply from too high FPS.

Edited May 9, 20206 yr by Xingent
Some errors in my test data.

All this happened because I did not understand why on my extreme water-cooled rig P3Dv4 does not generate FPS higher than 60. Now, I followed Bert's comment on NVIDIA Max Frame Rate and did some additional experiments. The results are interesting:

I noticed that with Max Frame Rate = 30 the 100% load does not happen - see the tests below:    
1.P3D Target frame rate = 60, NVIDIA Max Frame Rate = 30 FPS  -> CPU 0 3% load for real FPS = 25 and 85% for FPS = 30 2.P3D Target frame rate = 60, NVIDIA Max Frame Rate = 100 FPS -> CPU 0 100% load for real FPS = 25 and FPS = 60
3.P3D Target frame rate = 60, NVIDIA Max Frame Rate = OFF        -> CPU 0 100% load for real FPS = 25 and FPS = 60
    The above suggests that NVIDIA must activate Max Frame Rate limit in order to get the real CPU 0 load (test 1. 

In my scenario: Simulation unpause, engines OFF and P3D options: VSync = ON, Target frame rate = Unlimited,
NVIDIA Max Frame Rate = OFF
The maximal generated frame rate depends on view complexity and is bound by CPU 0:
        1. VRS Superbug Outside Spot view  -> 45 FPS =  Total CPU load: 6%, CPU 0 load: 100%
        2. VRS Superbug virtual cockpit view -> 19 FPS =  Total CPU load: 7%, CPU 0 load: 100%
        
 After "touching" affinity using PowerShell script (my previous comments), the results for the above situations are:
        1. VRS Superbug Outside Spot view  -> 45 FPS =  Total CPU load: 6%,  CPU 0 load: 3%
        2. VRS Superbug virtual cockpit view  -> 21 FPS =  Total CPU load: 7%, CPU 0 load: 3%    
 GPU load was about 33% - so that another question for this case for this case:

With such a low GPU & CPU load why FPS is not getting higher?
One possibility: P3Dv4 is falsely detecting CPU 0 100% load and throttles FPS.