fixed CPU runs +20° hotter in idle after update to 2.9.16.10523.

[TheBiggerBass]

vor 47 Minuten schrieb Flia:

We really need that hotfix, gentlemens.

î rather want a coldfix 

[MarkP]

I dont have issues, 13900k. 50°C in menu and 65°C in a freeflight.
Mind you i have an undervoltage on my system but still

[Oberst Struppi]

2 hours ago, TheBiggerBass said:

î rather want a coldfix 

Its not just a temperature thing. Even our dedicated server is affected by this issue. I cannot monitor temps on the servers CPU, but what we have is unplayable missions on the CW Germany map. Prior to .10523 everything was butterly smooth. Now it became unplayable.

Interestingly our Caucasus and Nevada based missions are still running on the servers side.

On the client side we see troughout alle maps higher CPU temps. 
 

 

[Belphe]

Not sure if this is related to THIS issue but it's definitely related to the CPU.

If your system is capable of running the SIM at high FPS but you're still experiencing stutters try this:

1. Run Task Manager when the SIM is running.

2. Go to Details tab and find DCS.exe

3. Right-click it and Set Affinity

4. Untick core numer 8.

Miraculously, the stuttering will disappear. Does anybody know what is core 8 doing in DCS? Disabling it IMHO has no negative effects and one that is a huge gain.

[scommander2]

14 minutes ago, Belphe said:

Does anybody know what is core 8 doing in DCS?

Someone did make off for the 8th core in affinity for the related issue and there was a thread about it.

I have checked ED tech support for the benefit of offing 8th core from the process affinity, and the tech support could not provide an explanation about this setting.  However, tech support said that if it works for users and why not.

Edited Wednesday at 01:52 PM by scommander2

[Dangerzone]

Core 8 would be the first of the E core's wouldn't it? I have DCS restricted to only P cores (Cores 0 through 7). Could it be E-core related? 

 

[TheBiggerBass]

vor 1 Stunde schrieb Dangerzone:

I have DCS restricted to only P cores (Cores 0 through 7).

How do you do that?

[scommander2]

2 hours ago, Dangerzone said:

Could it be E-core related? 

Not for my case.

According to my doc.log:

common cores: {8, 9, 10, 11}
render cores: {4, 5, 6, 7, 0, 1, 2, 3}
IO cores: {12, 13, 14, 15, 16, 17, 18, 19}
unavailable cores: {}

My P-cores are from 0 to 11 for i9-13900 CPU.  The 8th core is my P-core.

I will test for unclicking the 8th CPU from the process affinity. 

Edited Thursday at 12:01 AM by scommander2

[sleighzy]

12 minutes ago, TheBiggerBass said:

How do you do that?

You're on Windows 11. Just make sure you have core parking disabled (can use ParkControl for that). You shouldn't restrict cores as this makes them unavailable to DCS. Windows 11 is smarter about the cores and DCS is able to use the E cores for the right things.

[TheBiggerBass]

vor 9 Minuten schrieb sleighzy:

Just make sure you have core parking disabled

Already did that. I thought restricting cores to 0-7 might prevent overheat or fans going wild. I also restricted CPU load to 99% to avoid turbo mode on the i9-14900K but it didn't help either. I guess we have to be patient until ED releases another bugfix.

[Dangerzone]

8 hours ago, scommander2 said:

Not for my case.

According to my doc.log:

common cores: {8, 9, 10, 11}
render cores: {4, 5, 6, 7, 0, 1, 2, 3}
IO cores: {12, 13, 14, 15, 16, 17, 18, 19}
unavailable cores: {}

My P-cores are from 0 to 11 for i9-13900 CPU.  The 8th core is my P-core.

I will test for unclicking the 8th CPU from the process affinity. 

How bizzare. I have a 13900 too (13900KF), and this is what Process lasso shows me - 8 P cores, and 16 E Cores. Wonder what I'm missing...

 

8 hours ago, TheBiggerBass said:

How do you do that?

I use Process Lasso myself. I don't know - I hear a whole bunch of different things as to whether to restrict or not. All I know is when I make all cores available to DCS - the menu's FPS was horrible, and I was having serious performance issues. Restricting DCS to only P cores and restricting other non-essential apps to E cores fixed the problem for me. But YMMV because everyone seems to have differing opinions on what you should or shouldn't do. My advise is try it. It can't hurt - just note what you've restricted so you can undo it if it doesn't improve.

[trindade]

On 5/28/2025 at 9:01 AM, Flia said:

We really need that hotfix, gentlemens.

+1

[draconus]

2 hours ago, Dangerzone said:

How bizzare. I have a 13900 too (13900KF), and this is what Process lasso shows me - 8 P cores, and 16 E Cores. Wonder what I'm missing...

This is correct. 13900 has 8 P-cores and 16 E-cores.

https://www.intel.com/content/www/us/en/products/sku/230497/intel-core-i913900kf-processor-36m-cache-up-to-5-80-ghz/specifications.html

[scommander2]

2 hours ago, Dangerzone said:

Wonder what I'm missing...

No, it is correct.

DCS uses vCPU instead and it is same as Task manager processor affinity due to hyper-threading for all P-Cores.  And, PL looks the physical cores on another hand.

So, sorry that it is the interoperation issue.  Yes, I agree that we want the DCS render/common cores are on all P-Cores not E-Cores.

About the 8th core, it should go by DCS counts or PL counts and it is very questionable since the different CPUs have different P-Core counts.

Go back to the topic:  I disabled the 8th core according to DCS counts and it did not make different in my environment.

[Ironious]

Anyone have command to revert the dedicated server? I used dcs_updater.exe update 2.9.15.9599@release and it installed the full version.

Don't know what I did wrong but after reinstalling just the server I tried it again and it worked properly.

Edited Thursday at 09:59 PM by Ironious

[Dangerzone]

  

11 hours ago, draconus said:

This is correct. 13900 has 8 P-cores and 16 E-cores.

https://www.intel.com/content/www/us/en/products/sku/230497/intel-core-i913900kf-processor-36m-cache-up-to-5-80-ghz/specifications.html

 

11 hours ago, scommander2 said:

No, it is correct.

DCS uses vCPU instead and it is same as Task manager processor affinity due to hyper-threading for all P-Cores.  And, PL looks the physical cores on another hand.

So, sorry that it is the interoperation issue.  Yes, I agree that we want the DCS render/common cores are on all P-Cores not E-Cores.

About the 8th core, it should go by DCS counts or PL counts and it is very questionable since the different CPUs have different P-Core counts.

Go back to the topic:  I disabled the 8th core according to DCS counts and it did not make different in my environment.

 

Aaah - I have hyperthreading disabled. That might be why I don't see the p-cores go beyond 7. Anyway - on the 13900KF, with Hyperthreading disabled, C-State disabled, and DCS restricted to cores 0-7 I'm not seeing the same elevation in CPU temps that are reported here. Could Hyperthreading potentially be part of the issue?

Edited Thursday at 11:02 PM by Dangerzone

[Creampie]

On 5/26/2025 at 3:14 AM, draconus said:

Can we change the thread title to something like "High CPU usage in main menu/ME after update to 2.9.16.10523"?

CPU temperature is none of DCS concerns. It's on the user to keep their CPUs cool and safe enough even with full CPU usage. And it can't be idle either since it gets hot.

The group I play with have not noticed any increase in CPU usage, only temps. Even after rolling the update back just to compare. 

CPU temp is certainly the concern of DCS when their consumers are having issues due to an unexpected error with an update. However it is not of concern if people keep playing on the update and damage their hardware (not likely)

 

Not much though went into your proposed title change. 

[hannibal]

how can i test this?

i have 9800x3d, and dont see overheat

however, i disable Simultaneous Multi-Threading (SMT)

[speed-of-heat]

10 hours ago, Dangerzone said:

  

 

 

Aaah - I have hyperthreading disabled. That might be why I don't see the p-cores go beyond 7. Anyway - on the 13900KF, with Hyperthreading disabled, C-State disabled, and DCS restricted to cores 0-7 I'm not seeing the same elevation in CPU temps that are reported here. Could Hyperthreading potentially be part of the issue?

try restricting to physical only cores 0, 2, 4, 6, 8, 10 etc...  that will functionally remove hyperthreading from the equation 

6 hours ago, hannibal said:

how can i test this?

i have 9800x3d, and dont see overheat

however, i disable Simultaneous Multi-Threading (SMT)

you will more likely hear it first from what i gather as your fans will ram up 

more than normal

8 hours ago, Creampie said:

The group I play with have not noticed any increase in CPU usage, only temps. Even after rolling the update back just to compare. 

CPU temp is certainly the concern of DCS when their consumers are having issues due to an unexpected error with an update. However it is not of concern if people keep playing on the update and damage their hardware (not likely)

 

Not much though went into your proposed title change. 

i guess my question is ... by how much ... if its as much as 10 degrees , that might be just a change in ambient given the time of year  (YMMV)

[BIGNEWY]

Hotfix is planned for today the 30th of May 2025

thank you 

[BIGNEWY]

fix applied in todays patch, thank you for all of your reports here and in private messages.