investigating MT running with E-cores only

[divinee]

Hi,

Seems that DCS is running with E-cores on my system. This causes massive increase in frametimes. With ST CPU frametimes in hornet's ready on the ramp instant action were about 8ms. With MT CPU frametimes increased to ~16-17ms. After parking all the e-cores, dcs refuses to start at all. System is on my sig. Forgot to mention that running with native OXR and G2 with 100%.

edit: tried slow repair but it didn’t help

edit2: noticed that when dcs starts it loads up one P-core. Same thing when loading mission. After load is done all the P-cores are idling and E-cores are doing all the work.

DxDiag.txt dcs.log

Edited March 11, 2023 by divinee
system

[Furiz]

I have the same issue on i5 12600k:

Edited March 11, 2023 by Furiz

[Wu70]

It works fine on my system with P+E cores (12600k), significant load across all cores

[BIGNEWY]

Please remove all unofficial mods 

C:\Users\sm00t\Saved Games\DCS.openbeta\Mods

then run a slow repair or verify if steam. 

If you are using any third party tools like reshade try without. 

Also delete your fxo and metashader2 folders in saved games dcs.openbeta folder

Restart dcs and allow time for new shader creation 

thanks

[divinee]

12 hours ago, BIGNEWY said:

Please remove all unofficial mods 

C:\Users\sm00t\Saved Games\DCS.openbeta\Mods

then run a slow repair or verify if steam. 

If you are using any third party tools like reshade try without. 

Also delete your fxo and metashader2 folders in saved games dcs.openbeta folder

Restart dcs and allow time for new shader creation 

thanks

Thank you for the reply.

I did all those in said order, but saw no change in the situation. New log file attached.

edit: and DCS still refuses to start if i disable all e-cores from bios. I cannot find any info anywhere what can cause this kind of behavior.

dcs.log

Edited March 12, 2023 by divinee

[divinee]

Seems like i found a solution. There was high performance selected in windows power plan. Changed it to balanced and cpu-frametimes dropped to 3-10ms in the same scenario as in the original post. Also there seems to be more even load to P-cores. 

edit: nah, might be a false alarm. Restarted everything and frametimes went back to 16-17ms. I think i somehow managed to trigger windows core scheduling to notice that dcs is gaming workload, not utility load. But still changing the power plan was a step to the right direction.

@BIGNEWY 

Edited March 12, 2023 by divinee

[bomber]

Same for me 13700k. 8 xP @5.1., 8x E.@4.2, hyperthreading.  4090. 64gb.  

better performance( thank you dcs). 

In SP using e cores 100%  hardly using p cores. I did think that on multiplayer that P core would come into their own with all the calcs, but no, very little use. 

Will try suggestions above

 

Edited March 12, 2023 by bomber

[BIGNEWY]

Do you have HAGS enabled in windows? and windows game bar? 

If so disable and see if you notice a difference 

[gottel]

Plane used is Appache, running MT (ckecked via process) on Intel 13900KF, Nvidia 4090, Hardeware accelaerated GPU shed. and gamebar is off

2D, Windows 11

 

Edited March 13, 2023 by gottel

[RuskyV]

I had the same issue with my 12700KF,

I’m using process lasso to de-selected the e-cores from the DCS.exe. This forced it onto the physical cores.

[divinee]

2 hours ago, BIGNEWY said:

Do you have HAGS enabled in windows? and windows game bar? 

If so disable and see if you notice a difference 

Hi,

HAGS and game Bar are both off

[bomber]

1 hour ago, RuskyV said:

I had the same issue with my 12700KF,

I’m using process lasso to de-selected the e-cores from the DCS.exe. This forced it onto the physical cores.

Seems like a good stopgap. Will try.

[divinee]

I also tried to block E-cores with Lasso and the load clearly moved to P-cores. I didn’t notice any change in the frametimes though..

[Furiz]

My processor is heating up more than usual, working from 70-80C while with other games it works at around 60C.

[breetai]

Same here, I have a 13900k and it's using all E cores and 1 P core.

[JuiceIsLoose]

Same issue here using an i7-12700K. Its putting all the load on the E-cores. Noticed almost no change in FPS when switching from ST to MT. In MT it says I am still CPU bound. I have a GTX 3080TI and a i7-12700K. Noticed my CPU clock speed was low for it being CPU bound and then noticed DCS was only using the E-cores. 

[gorzasty]

Hello

I have checked also my utilisation and it looks strange. Does it should look like this or it uses E-cores instead of P cores so something is wrong? I can see also, that P core 0 is utized at 100% that is why I have CPU bound even in the main menu. 

 

null

Edited March 12, 2023 by gorzasty

[bomber]

After following a full repair the allocation of P cores improved for me, I am however running much hotter

5 hours ago, Furiz said:

My processor is heating up more than usual, working from 70-80C while with other games it works at around 60C.

even though downgraded cpu P cores to 4.9

13700, 4090, 64gb.         VR.

Edited March 12, 2023 by bomber

[KoleTang]

I have a 13900K and 4090 with 64 GB.  I have no issues either.  

Everyone should realize that since MT is using more of your CPU,  temps should go up expectedly.  There is no free lunch.

[divinee]

Please, put a note in the post if you are running with 2d or vr so we can rule out possible causes.

[breetai]

3 hours ago, breetai said:

Same here, I have a 13900k and it's using all E cores and 1 P core.

This is in VR.

[Ben Diss]

13900K, 4090, 64 RAM

VR: running all e-cores, p-cores idle.
Monitor: runs one p-core at 100%, all e-cores.

In VR, no difference in frame rate between ST and MT bins.

[diego999]

2 hours ago, KoleTang said:

Everyone should realize that since MT is using more of your CPU,  temps should go up expectedly.  There is no free lunch.

 

We have higher temps and a single core maxed out while looking at the main menu. Something is clearly wrong here.

[YoYo]

On 3/11/2023 at 8:00 AM, divinee said:

Hi,

Seems that DCS is running with E-cores on my system. This causes massive increase in frametimes. With ST CPU frametimes in hornet's ready on the ramp instant action were about 8ms. With MT CPU frametimes increased to ~16-17ms. After parking all the e-cores, dcs refuses to start at all. System is on my sig. Forgot to mention that running with native OXR and G2 with 100%.

edit: tried slow repair but it didn’t help

edit2: noticed that when dcs starts it loads up one P-core. Same thing when loading mission. After load is done all the P-cores are idling and E-cores are doing all the work.

DxDiag.txt 100.72 kB · 0 downloads dcs.log 61.37 kB · 2 downloads

 

Noticed the same (e-cores), however I see better results, thx for this topic!

Edited March 12, 2023 by YoYo

[JuiceIsLoose]

5 hours ago, JuiceIsLoose said:

Same issue here using an i7-12700K. Its putting all the load on the E-cores. Noticed almost no change in FPS when switching from ST to MT. In MT it says I am still CPU bound. I have a GTX 3080TI and a i7-12700K. Noticed my CPU clock speed was low for it being CPU bound and then noticed DCS was only using the E-cores. 

So to update this. I tried forcing DCS to p-cores using Process Lasso like some others have suggested. No changes. I even went into my BIOS and disabled E-cores. DCS MT will not launch when I have the E-cores disabled....which was very interesting.

Using Reverb G2 with the force XR runtime added into the DCS MT executable.