17 hours ago, micstatic said:

But each new update should embrace newer and more modern hardware right?  It's not like the current version of sims stop working overnight. 

You are right of course, P3D doesn't. Not so that other sim. 😉

Karl

41 minutes ago, GSalden said:

Come on Dirk. You are cheating : a delitted CPU 🤠…

Delidded!! 

Why?

4 minutes ago, Dirk98 said:

Delidded!! 

Why?

Your CPU has been opened up and the top part has been taken off…

We simple simmers are having closed default CPUs…

😊

 

2 minutes ago, GSalden said:

Your CPU has been opened up and the top part has been taken off…

We simple simmers are having closed default CPUs…

😊

 

C'mon Gerard, just no IHS not a big deal ))

This thread has brought me one thing : checking the CPU temps.

My server has low temps ( LQS) but my left view client showed 85-92 under max load.

It has a 8700 @ 5 Ghz and when I overclocked it I left VCore to auto. So I changed it to Manually and set it to 1.32 and now the temps are 75-79 under max load.

So this thread has brought me a good thing 😀

1 minute ago, GSalden said:

This thread has brought me one thing : checking the CPU temps.

My server has low temps ( LQS) but my left view client showed 85-92 under max load.

It has a 8700 @ 5 Ghz and when I overclocked it I left VCore to auto. So I changed it to Manually and set it to 1.32 and now the temps are 75-79 under max load.

So this thread has brought me a good thing 😀

1.32v - you'll need to check the stability thoroughly yet to avoid confusion with exes' glitches. 

4 hours ago, Dirk98 said:

1.32v - you'll need to check the stability thoroughly yet to avoid confusion with exes' glitches. 

The system is stable, Tested it in the Amsterdam region with TE NL + FT Amsterdam + EA overcast weather…

In a few days I will try 1.31 and if that is stable 1.30….

Edited June 21, 20214 yr by GSalden

2 hours ago, GSalden said:

In a few days I will try 1.31 and if that is stable 1.30….

Just about right if you know what you're doing

13 hours ago, westman said:

Amd is a little differnt to INTEL, i have booth Intel and AMD up and running with a 3090 a run locked 60HZ with affinity to the fastet core use 9cores for p3d.the only diff 60 vs 30 is that gpu usage go from around 30% to 60% and the cpu usage is up to approx 90%.

My Harware: AMD 5950X , ram 32gb 4x16gb Amd runs better with 4 sticks, ram speed 3600mhz c15 1t synced infinity fabric 1800mhz. GPU Galax 3090 Hof OClab ed, cpu gpuH2O cooled custom loop

Nearly the same Setup as mine 

Edited June 21, 20214 yr by Ray Proudfoot
Quoted post shortened

Howdy:

Need some of your wizard insight please.

I have an i77700K no oc and HT on.  Also, I've NEVER modified my p3d.config. so no AM.

While running v5.2 I noticed all my cores are running close to max.  Do I still need an AM?  I though only if I had an AM, would I see all cores "in use".  

The only other programs I have running are P3D, Navigraph, Active Sky P3d, and a PDF open.

Thanks!

For years people complained not all cores where being used..Now the issue seems to be all my cores are being used… 🤔.

 

If the sim is running well with good FPS and no stutters, and your not getting blurries or other issues, just let the system do it’s thing. As was said above, what works on one system might not work on the next and if it ain’t broke no need to try and fix it.

 

that’s my 2c

Edited June 22, 20214 yr by KL Oo

3 hours ago, KL Oo said:

For years people complained not all cores where being used..Now the issue seems to be all my cores are being used… 🤔.

 

If the sim is running well with good FPS and no stutters, and your not getting blurries or other issues, just let the system do it’s thing. As was said above, what works on one system might not work on the next and if it ain’t broke no need to try and fix it.

 

that’s my 2c

The issue is that before we were able to use higher settings to have the same core load as now with v5.2. 

Myself I always tweak my settings till the edge so in my most heavy situation in v5.1 the pc was just able to handle everything. 
Now with v5.2 I get stutters in those situation. The same settings appear to be too much.

So everyone who had enough headroom in v5.1 might just make it without blurries / stutters in v5.2. But if you had  v5.1 configurered like I had you will experience them.

And that is what LM has acknowledged and what they are working on for the HF.

 

Edited June 22, 20214 yr by GSalden

1 hour ago, KL Oo said:

For years people complained not all cores where being used..Now the issue seems to be all my cores are being used… 🤔.

With HT enabled, there are two logical processors per core. In the screenshot below you see LP0 is used but LP1 is not so much. That is with P3D running so that's core zero being used even though LP1 is not in use. In this core zero the main task of P3D is able to get full bandwidth of core zero on LP0 without sharing to a task on LP1.

The problem with understanding P3D and FSX is they are hybrid multi-tasking programs.

That is, when they start up they 'look' at the CPU to 'see' the number of cores and allocate a task for each core. Those tasks are pinned to the core they are started on.

What is important to understand is that the main task of rendering requires consistent high speed. The background tasks take seconds to complete so are not affected by inconsistent speed.

The main rendering task is allocated to core zero, and the second task is on core 1, and the next task is on core 2, and so on.

The available throughput of the main task is important to frames per second and stutter because the main task is that which decides how many objects can be delivered to rendering and that task must remain consistent.

 

Consider the case of HT enabled.

P3D and FSX 'see' the number of Logical Processors (LPs, two per core). The tasks are now allocated with the main rendering task on LP0 (core 0), the second task on LP1 (core 0), the third task on LP2 (core 1), the fourth task on LP3 (core1) and so on.

So with HT enabled, and with high settings, the second task on LP1 is using bandwidth of core zero because it is sharing core 0 with the main task on LP0 - causing stutter.

If the second task is moved out of core 0 from LP1 to LP2 on core 1, then the main task on LP0 core 0 has unobstructed use of core 0.

The [JOBSCHEDULER] AffinityMask setting (AM) is made available to P3D and FSX config settings.

With HT enabled the AM is used to mask LP1 from P3D (or FSX) and leaves LP0 available so that only the main task is running on core zero without sharing the bandwidth of core zero to a task on LP1.

 

Furthermore:

We also use the AM to limit the number of P3D (or FSX) tasks because a system will have a finite throughput available that is divided between the tasks.

If we allow too many tasks the throughput is divided down too much to enable the main task to maintain processing speed - causing stutter.

That is with HT enabled or disabled, there is an optimum number of tasks per system. Too many or too few will not produce the best result. Each system is different. CPU, memory, GPU, user settings desired and so on, so the optimum will be different.

 

 

 

Edited June 22, 20214 yr by SteveW

Thanks Steve - a good explanation.

The reason HT OFF has always worked for me makes sense based on what you've indicated above. That said, if HT is OFF then as I understand it the main rending task is being undertaken on CORE 0 with subordinate tasks taking place on as many other cores as P3D chooses to use. 

So if thats the case then as you say, it really is a case of trying different combinations to see what works best, but it would seem the most common use for the AffinityMask option is if one wishes to leave HT enabled on their system but still ensure P3D is only utilising on LP per core, not too. Which is what I understand Ray is doing.

 

Cheers,