reported One or more cores reaching 100%

[Loukuins]

I stopped playing for 8 month, come back, and the issue is STILL HERE, 4 threads at 100% usage, lost 100fps, now running at 60fps, instead of before V-sync locked 175fps.

[jackill]

I have basically the same CPU, but from, the beginning I am using mt.lua added to Saved Games\DCS\Config and for fps limiter just Radeon Chill.

multithreading =
{
	exclusiveMainRenderCore = false
}

Maybe you could try it.

[scommander2]

20 minutes ago, jackill said:

I have basically the same CPU, but from, the beginning I am using mt.lua added to Saved Games\DCS\Config and for fps limiter just Radeon Chill.

multithreading =
{
	exclusiveMainRenderCore = false
}

Does it mean that all available CPUs can be opted in the render core rather than DCS defaults the few specific CPUs   Thanks. 

[Loukuins]

3 hours ago, jackill said:

I have basically the same CPU, but from, the beginning I am using mt.lua added to Saved Games\DCS\Config and for fps limiter just Radeon Chill.

multithreading =
{
	exclusiveMainRenderCore = false
}

Maybe you could try it.

The screenshot was taken with the lua file. I've been using it since it was released on the forums 

[scommander2]

4 hours ago, scommander2 said:

4 hours ago, jackill said:

I have basically the same CPU, but from, the beginning I am using mt.lua added to Saved Games\DCS\Config and for fps limiter just Radeon Chill.

multithreading =
{
	exclusiveMainRenderCore = false
}

Expand  

Does it mean that all available CPUs can be opted in the render core rather than DCS defaults the few specific CPUs   Thanks. 

There is my research about "exclusiveMainRenderCore".

The search mentions that:

Quote

When troubleshooting performance issues in DCS World, especially on Intel 11th Gen and newer CPUs with hybrid core architectures (P-cores and E-cores), the term "exclusiveMainRenderCore" sometimes comes up. 

 

In this context, "exclusiveMainRenderCore" refers to the core(s) that DCS World's main rendering thread is assigned to by the operating system (Windows) scheduler.

Since Intel 11th gen+ with two different cores:

Quote

• DCS and Hybrid CPUs: Some users have reported issues where DCS's main rendering thread is occasionally assigned to inefficient E-cores instead of the high-performance P-cores on Intel 11th generation and newer processors. This can lead to performance problems like lower frame rates and stutters.

For AMD, there is no P/E cores.

I think that DCS has handled this matter already.  According to the dcs.log, both, render/common, cores should be assigned with P-Cores only.

 

Edited 22 hours ago by scommander2

[jackill]

4 hours ago, Loukuins said:

The screenshot was taken with the lua file. I've been using it since it was released on the forums 

I removed it, and then DCS seems to max out core 0 (see screenshot).

 

3 hours ago, scommander2 said:

For AMD, there is no P/E cores.

I think that DCS has handled this matter already.  According to the dcs.log, both, render/common, cores should be assigned with P-Cores only.

Interesting. For sure I am seeing some changes how cores are used, but maybe it does not have any impact over performance. I never had issues with stuttering, just on some scernarios I was CPU bound.

Edited 18 hours ago by jackill
Adding scr

[Papamiraculi]

vor 20 Stunden schrieb jackill:

I have basically the same CPU, but from, the beginning I am using mt.lua added to Saved Games\DCS\Config and for fps limiter just Radeon Chill.

multithreading =
{
	exclusiveMainRenderCore = false
}

Maybe you could try it.

I sometimes get 100% on a single core too. Not Always, and I haven't found a reason why it's not always the case. I suspect DCS just puts too much stuff on the main thread. Running 9800x3d.

But I will definitely try this. Thanks for bringing this up.

An observation when looking at your screens: it looks like both are actually maxing out a core. Core 9 seems rather maxed out here in this screenshot with your mod engaged, very similar to your second screenshot, which maxes out core 0 with the mod disengaged.

Are you sure it doesn't just move the main thread from core 0 to another core? This is what happens if I deactivate the maxed out core while DCS is running. The main thread will just move to a different core and max out that one.