19 minutes ago, GSalden said:

Myself I prefer they take it one step further and take more load of the main thread core and put it on the GPU. The 30 series are capable of so much more than what they need to do now.

The 30x0 are utterly incapable of one key requirement - being bought at a sane price. If P3D requires significantly higher specs than a much better looking MSFS, the die will be cast.

Cheers

24 minutes ago, GSalden said:

Multiple users in this thread and at the LM thread have reported the more CPU load / less GPU load issue. 
And I am one of them as I showed with a vid.

According to Marcus the HF is solving this so load will be back to v5.1 level.

Myself I prefer they take it one step further and take more load of the main thread core and put it on the GPU. The 30 series are capable of so much more than what they need to do now. Even with 2x 4K as one wide view and all GPU taxing settings at max.

Hopefully LM will release a HF that all of us pleases ✈️

We have seen some users with this issue when using AI. Kaiii3 contacted the devs and asked for help. We have to wait on their response. 

Marcus

@GSalden, agree completely with your comments about moving work from the GPU back to the CPU. A strange decision indeed and unwelcome for those with plenty of VRAM available.

I've removed the [SOLVED] tag on the topic title since it might lead others to think the overall issue is solved when it isn't.

27 minutes ago, mazelda said:

 

1. I have just moved over to the dark side and i'm now on a Ryzen 5950x, Can you turn hyperthreading off on a Ryzen? I knew how to do it on an intel bios but I think AMD call it something different?

Welcome. That’s a beast of a CPU 👍

Hyperthreading on AMD is called SMT (Simultaneous Multi-Threading). 
Look for SMT in the bios and disable that. 
 

From my testing AMD definitely works better in P3D with no Hyperthreading, I have tried various affinity masks with SMT on but nothing is as smooth as just having it disabled. 

I also use a program called Process Lasso to move as many programs as possible away from core 0. There are a few windows processes that cannot be moved away from that core, but the vast majority can. 

Edited June 20, 20214 yr by djbully

1 hour ago, mpo910 said:

We have seen some users with this issue when using AI. Kaiii3 contacted the devs and asked for help. We have to wait on their response. 

Marcus

No AI problems as I use PSXT + RT

14 hours ago, DonMuskopf said:

Ray thanks for all your efforts. I tried various Affinity Masks, including the one that worked for you. Unfortunately, none of them worked for me.

 

I did find a fix that worked. The problem for me was a combination of how I limit frame rates and the RXP GTN750.

 

Starting with P3Dv5.1, I set the frame rate limiter to 120 in the sim and set a max frame rate of 35 in NCP (most of you would probably use 30, but 35 works great for me with G-sync). With HT on, LP0 never hit 100%. However, with v5.2 this did not seem to work. I realized that all the aircraft that I used to test v5.2 had the RXP GTN750 installed. This seemed to be causing the 100% utilization on LP0 even with my method for limiting frame rates. The recent RXP GTN750 update did not fix the problem. So I uninstalled every trace if the GTN750 and did a clean install of the GTN750. That fixed the problem and I’m basically back to where I was on V5.1 with LP0 utilization.

 

So now with HT on, in sim frame rate limited to 120 and max frame rate of 35 in NCP:

● With EA off, LP0 utilization is between 65% and 85%.

● With EA on using legacy clouds LP0 is between 80% and 95%.

 

Everybody’s setup is so different, I’m not sure how helpful this is, but it worked great for me. LP0 never hits 100%. However, the other LPs do have higher utilization rates than v5.1. Not sure if this is better multicore utilization or just higher loads compared to v5.1.

 

The sim for me is now super smooth with no stutters or micro stutters. I love using EA with legacy clouds.

 

 

thanks for this.  I also have a GSYNC monitor so ill give this a whirl.

I apologize in advance if this old solution that also on P3D 5.2 solved the problem for me of CORE 0 to 100% has already been posted.

Obviously it is an "anomalous" procedure that must be done every time after starting P3D 5.2 but in waiting for a stable solution from LM, at least to me, it works with this procedure:

after starting P3D 5.2 and the chosen graphic scenario go to   Task management - Details - click on Prepar3d.exe - Set affinity - uncheck CPU 0 - OK-  Check that with Prepar3D 5.2 in
activity the CPU 0 does not work at 100% (to me it varies between 0/6%) then go back to  Set affinity e put  the check mark back on CPU 0 - OK.

I have verified that by re-enabling CORE 0 it no longer works fixed at 100% and that all COREs work with % more uniform between 50/90% with very rare peaks at 100% also noting a general decrease in CORE temperatures between 3/5 ° C.

12 minutes ago, bob 742 said:

I apologize in advance if this old solution that also on P3D 5.2 solved the problem for me of CORE 0 to 100% has already been posted.

Obviously it is an "anomalous" procedure that must be done every time after starting P3D 5.2 but in waiting for a stable solution from LM, at least to me, it works with this procedure:

after starting P3D 5.2 and the chosen graphic scenario go to   Task management - Details - click on Prepar3d.exe - Set affinity - uncheck CPU 0 - OK-  Check that with Prepar3D 5.2 in
activity the CPU 0 does not work at 100% (to me it varies between 0/6%) then go back to  Set affinity e put  the check mark back on CPU 0 - OK.

I have verified that by re-enabling CORE 0 it no longer works fixed at 100% and that all COREs work with % more uniform between 50/90% with very rare peaks at 100% also noting a general decrease in CORE temperatures between 3/5 ° C.

Bob, there’s no need to do that manually each time. Just calculate what AM you want using the Windows Calculator in Programmer mode.

Then add this to your prepar3d.cfg changing the AF value as necessary...

[JOBSCHEDULER]
AffinityMask=1365

I cannot imagine that would not work for you.

Thanks Ray,

I tried to calculate and insert AF on P3d.cfg but the CORE 0 always remained at 100% and, at least for me, the only solution is to use the procedure I described.

 

 

@bob 742, what CPU do you have and is Hyperthreading enabled in the BIOS.

I have never read anyone do what you suggest.

4 hours ago, GSalden said:

...Myself I prefer they take it one step further and take more load of the main thread core and put it on the GPU. The 30 series are capable of so much more than what they need to do now....

Not all of us have a 30xx.

Karl

4 hours ago, djbully said:

also use a program called Process Lasso to move as many programs as possible away from core 0. There are a few windows processes that cannot be moved away from that core, but the vast majority can. 

Is this fairly easy to do?

I've downloaded and installed it but not sure how to go about this.

Task manager at the moment show core 0 at 100% and thats in v 5.1 but thats with absolutely no tweaks and no affinity mask and with hyperthreading still enabled

14 minutes ago, mazelda said:

Task manager at the moment show core 0 at 100% and thats in v 5.1 but thats with absolutely no tweaks and no affinity mask and with hyperthreading still enabled

You definitely need an Affinity Mask setting with HT enabled. Look back a couple of pages to see how it’s done based on your CPU.

My suggestion is free. I use SimStarterNG for the other programs but you may prefer PL. But sort out the AM ASAP.

Thanks Ray,

I have simstarter ng so will have a look at it as well and go back over the thread.

I just downloaded PL so have no idea how to use it yet so simstarter may be an option.

Looks like i've been lazy for a while and now have to play catchup on tweaking again 

My 5950x has 16 cores so should i be looking at setting the affinity to only use those and ignore the other 16 that hyper threading enables?

1 hour ago, kaha said:

Not all of us have a 30xx.

Karl

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