Core Affinity in Autoexec.cfg no longer working?

[wopski]

Running multiple dedicated servers it makes life easy being able to set core affinity in the autoexec.cfg but this no longer works both on dedicated server or client install?

 

Is this just temp thing, has it been replaced with a different command or just removed all together?

 

affinity_mask = ***

 

Kind regards,

 

WOP

[- J i n x -]

+1

[robgraham]

noticed this as well relaly would like to know

[wopski]

Affinty mask is still overridden in stable release on dedicated server??

 

Please can you tell me why? I'm sorry but i don't see a mention of it in change logs! OB or stable. ?

 

It even overrides 3rd party software firedeamon pro.

 

worked fine before 2.5.6

 

will post a video tomorrow

 

Kind regards,

 

WOPR

Edited May 30, 2020 by wopski

[davidp57]

Same question here, sorry that we don't have any answer.

I'm going to ping BigNewy.

[BIGNEWY]

Hi all, I will ask the team and let you know

 

Thanks

[alt.sanity]

I've also tried forcing the cpu affinity with cmd and it does not work for DCS.exe for some reason. Works on other executables on the same machine though.

 

For example this works:

start "" /affinity 0x3 /high "C:\Users\Admin\AppData\Local\Discord\app-0.0.306\Discord.exe" --test

But this doesn't:

start "" /affinity 0x3 /high "C:\Eagle Dynamics\DCS World Server\bin\DCS.exe" --server --norender -w DCSZA_1

[davidp57]

Yes, I think that DCS is managing its affinity itself, in its own code, hence the failure to do what Windows wants it to do !

[Cornelius]

Yeah,it isn't working anymore. I do not like to use extra software, but since some time now process lasso does its job. With DCS on first core I get constant stutters...

[Worrazen]

This may be either an intended or unintended consequence of a fix or partial workaround of what I reported some time ago, regarding thread racing between main and texture/asset loading threads. But Im currently in maintenance, didnt test anything myself in the last mont and probably for the next two.

[c0ff]

This may be either an intended or unintended consequence of a fix or partial workaround of what I reported some time ago, regarding thread racing between main and texture/asset loading threads. But Im currently in maintenance, didnt test anything myself in the last mont and probably for the next two.

 

Indeed it is, an unintended one. The next openbeta should fix this.

[davidp57]

Thanks for the info, c0ff !

[Cornelius]

uh, thought we will go back to the old situation with patch 52196, but Core Affinity still isn't working, furthermore it seems obsolete, as DCS seems to behave like it uses all of the 4 cores of my 4690k in a balanced way.:thumbup:

[speed-of-heat]

yes same observation from me

[Mustang]

For me with my i7 10700k I see core 12 and 15 being used close to 100% (core 15 is a hyperthread and not ideal) and the rest staying at a very low amount, I have to force a more balanced load via task manager core affinity setting for DCS.exe, just wished it worked properly via the autoexec.cfg.

[FoxTwo]

DCS seems to behave like it uses all of the 4 cores of my 4690k in a balanced way.:thumbup:

 

 

It's not. That's windows scheduler doing its job.

[Cornelius]

And why wasn't he able to do it before?

Edited July 18, 2020 by Cornelius