Jump to content

CPU Affinity Defaults to CPU 0 only...


Recommended Posts

All,

 

So I was having some seriously frustrating issues in the latest 2.5 beta with F-18 and the Persian Gulf map. I'd load a simple MP mission up and the ground textures wouldn't load. Cockpit textures would be all solid black.

 

Sometimes textures would load but if I went to the F10 map, and then back to the cockpit, the ground textures would disappear...

 

Long story short - after alot of messing about with settings (None of which made a difference), I discovered that DCS.exe was defaulting to use only one core of my 6 core/12 thread CPU.

 

Manually going into taskman and setting it to all cores, fixes all my issues. I can now run DCS with high settings and zero stutter or strange texture behaviour.

 

But... I have to do this every single time I launch DCS. I can't figure out why it continues to default to CPU0, but at least this work-around is easy.

 

Anybody else notice or experience similar behaviour?

 

Cheers,

Mack

Link to comment
Share on other sites

So I found the cause of this behaviour.

 

I'm running an older Broadwell-E CPU, (i7-6850K), with an MSI Tomahawk X99 motherboard.

 

One of the drivers it installs by default is called "intel Turbo Boost Max Technology 3.0". The utility included with it that's enabled by default, supposedly optimizes CPU affinity based on application demand.

 

Turning that thing off has solved the problem. DCS now defaults to use all 6 cores/12 threads.

 

Anybody running X99 should check/verify this thing is turned off as it's not running as designed or is bugged with DCS. (Yes I have the latest motherboard drivers, etc. And this is the latest driver/util that Intel has available for the X99 chipset).

 

Details on how to get rid of the utility entirely can be found here: https://www.pugetsystems.com/labs/support-software/How-To-Prevent-The-Intel-Turbo-Boost-Max-3-0-Software-From-Launching-On-Startup-1078/

Make sure you read the comments section as there are some additional details there you need to follow, that weren't covered in the initial article.

 

Hope this helps someone else out there!

 

-Mack


Edited by MackTheKnight
Link to comment
Share on other sites

So I found the cause of this behaviour.

 

I'm running an older Sandybridge-E CPU, (i7-6850K), with an MSI Tomahawk X99 motherboard.

 

One of the drivers it installs by default is called "intel Turbo Boost Max Technology 3.0". The utility included with it that's enabled by default, supposedly optimizes CPU affinity based on application demand.

 

Turning that thing off has solved the problem. DCS now defaults to use all 6 cores/12 threads.

 

Anybody running X99 should check/verify this thing is turned off as it's not running as designed or is bugged with DCS. (Yes I have the latest motherboard drivers, etc. And this is the latest driver/util that Intel has available for the X99 chipset).

 

Details on how to get rid of the utility entirely can be found here: https://www.pugetsystems.com/labs/support-software/How-To-Prevent-The-Intel-Turbo-Boost-Max-3-0-Software-From-Launching-On-Startup-1078/

Make sure you read the comments section as there are some additional details there you need to follow, that weren't covered in the initial article.

 

Hope this helps someone else out there!

 

-Mack

 

 

good work!!:)

Ryzen R7 1800x|EVGA FTW3 1080Ti|32gb Corsair Dominator Platinum@2666mhz|Samsung 750 EVO|LG 4k 50" Main Display|ASUS PB278Q Reference Display|

Link to comment
Share on other sites

That was a heck of a find! Congrats

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Link to comment
Share on other sites

I had the same problem. Rather than uninstalling ITBMT, I also use Process Lasso to fix it. I get best results setting DCS.exe as single-thread process/highest performance mode, so it uses only physical cores (0,2,4,6,8 and 10).

i7-6850K | GTX1080 | 32GB DDR4 | Windows 10 Pro

Link to comment
Share on other sites

Mack - do you have in-game MSAA enabled? If not can you try it? I had to turn it off completely to get reasonable performance and remove the microstutters. I'm running an i7-5820k, 16GB RAM, nvidia 1070

=============================

i7 5820k | 32GB RAM | Nvidia 2070RTX | 1TB SSD

Link to comment
Share on other sites

Hi Lefty,

 

Yes, I have MSAA set to 4X. In the Gulf map, I'm now getting FPS in the 60s at the air-field and 100+ up in the air.

 

Prior to figuring out the cpu affinity issue I was getting low 20's no matter what settings I tried along with constant micro-stutters every few seconds.

 

So happy to have it fixed now!

 

For reference I've a 1080Ti GPU OC'd to 2050/6005. (Under a custom water loop - don't try that on air)

 

-Mack


Edited by MackTheKnight
Link to comment
Share on other sites

Hey Mack, any chance you could post up a screen cap of Task Manager CPU performance tab while in flight?... im curious how the utilization is being spread among the cores on your system.. On mine, it is using 2,.. but the primary core is more saturated as of the 2.5.2.18144 update..

Ryzen R7 1800x|EVGA FTW3 1080Ti|32gb Corsair Dominator Platinum@2666mhz|Samsung 750 EVO|LG 4k 50" Main Display|ASUS PB278Q Reference Display|

Link to comment
Share on other sites

From that screengrab it looks to me like core 11 is actually doing most of the work. The spikes don't matter so much unless they're sustained. Core 11 is the only one that really shows sustained utilization. I was messing with resource viewer and I couldn't figure out how to get it to show CPU utilization for the DCS process only across all the cores - that would be the definitive view I think to prove if this is really working as you think.

=============================

i7 5820k | 32GB RAM | Nvidia 2070RTX | 1TB SSD

Link to comment
Share on other sites

+1

 

Same here with the 8700k, looks like the last core is doing most of the work...

[ i7 8700K@5Ghz (LC) - GTX 1080 TI (LC) - 32GB G.Skill Flare X 3200 - Gigabyte Z370 Aorus Gaming K3 - Samsung 970 PRO NVME SSD - LG 34" Ultra Wide - HTC Vive - Virpil MongoosT-50/WarBRD Base ]

Link to comment
Share on other sites

It's weird how some only have this problem with cpu utilization in DCS, I helped a guy recently who had the problem of DCS only grabbing one core, this was on one of the new CPU's too. He now also uses process lasso to make DCS use all his cores.

 

 

Here is a screenshot of me forcing DCS in process lasso to use only the main 4 Cores of my CPU. It shows 25%, in reality it's 50% of 4 main cores utilization, one main core working up to 90 %. This is at max in game settings, I haven't tested this on PG. The big thing here tho is My CPU is able to MAX out the 1080ti shown in the graph below, that's what I was testing. ED is working on getting this more balanced between the CPU and GPU.

 

 

attachment.php?attachmentid=184970&d=1526971866


Edited by David OC

i7-7700K OC @ 5Ghz | ASUS IX Hero MB | ASUS GTX 1080 Ti STRIX | 32GB Corsair 3000Mhz | Corsair H100i V2 Radiator | Samsung 960 EVO M.2 NVMe 500G SSD | Samsung 850 EVO 500G SSD | Corsair HX850i Platinum 850W | Oculus Rift | ASUS PG278Q 27-inch, 2560 x 1440, G-SYNC, 144Hz, 1ms | VKB Gunfighter Pro

Chuck's DCS Tutorial Library

Download PDF Tutorial guides to help get up to speed with aircraft quickly and also great for taking a good look at the aircraft available for DCS before purchasing. Link

Link to comment
Share on other sites

I think DCS still only really uses 2 threads for it's processing - one for the game, the other for audio. Additional threading is probably down to directx and/or your graphics driver parting up the work so that may benefit from spreading out but I'm not sure how much of an impact that has. The remaining threads appear to be DRM related. All of these can be spread out over your cores but the single primary game thread is still present and can't be divided up into multiple cores (unless 2.5.x has improved things!).

i7-4790K@4.7GHz : EVGA 1070 SC : 16GB Corsair Vengence Pro : 2xEVO 840 SSD : EVGA 850W PSU : CORSAIR H100i Cooler : ASUS Z97-AR MB : CORSAIR OBSIDIAN 750D FULL TOWER

Link to comment
Share on other sites

Sounds like I should give this process lasso thing a try just out of curiosity. I honestly don't care what the cpu/gpu usage stats show as long as I'm getting good FPS with no hitching.

 

And my FPS is solid now since getting rid of that Intel utility that was screwing my system over.

 

I ran a mission last night and the FPS never dropped below 60 and was generally hovering around 100. That is a far cry from the annoying hitching and low 20 some FPS I was getting before, so I'm a very happy simmer now!

 

I haven't tried the F18 in the Oculus yet, as I wanted to get more familiar with all the systems before jumping into VR. But I'm hopeful that my VR performance has improved dramatically as well, thanks to figuring this out!

Link to comment
Share on other sites

I think DCS still only really uses 2 threads for it's processing - one for the game, the other for audio. Additional threading is probably down to directx and/or your graphics driver parting up the work so that may benefit from spreading out but I'm not sure how much of an impact that has. The remaining threads appear to be DRM related. All of these can be spread out over your cores but the single primary game thread is still present and can't be divided up into multiple cores (unless 2.5.x has improved things!).

 

 

 

Confirmed:

 

 

DCS is using 2 cores. period. :D

New system:I9-9900KS, Kingston 128 GB DDR4 3200Mhz, MSI RTX 4090, Corsair H150 Pro RGB, 2xSamsung 970 EVO 2Tb, 2xsamsung 970 EVO 1 TB, Scandisk m2 500 MB, 2 x Crucial 1 Tb, T16000M HOTAS, HP Reverb Professional 2, Corsair 750 Watt.

 

Old system:I7-4770K(OC 4.5Ghz), Kingston 24 GB DDR3 1600 Mhz,MSI RTX 2080(OC 2070 Mhz), 2 * 500 GB SSD, 3,5 TB HDD, 55' Samsung 3d tv, Trackir 5, Logitech HD Cam, T16000M HOTAS. All DCS modules, maps and campaigns:pilotfly:

Link to comment
Share on other sites

Confirmed:

 

 

DCS is using 2 cores. period. :D

 

The devs don't say so anymore, they outline that threading has been adopted wherever they can

and more in the future.

 

When I fly online, my CPU is often beyond 60%, not permanent, but often and long enough to make me believe that more cores have a justification already.

 

The more time goes by the more DCS will adopt threading where they can and once Vulkan arrives

their is even more need for multiple cores.

 

Yeah, the main work is done by 1 core, but that's not the whole picture.

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Asus 1080ti EK-waterblock - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus PG278Q 27" QHD Gsync 144Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Link to comment
Share on other sites

  • 2 months later...

Finally!!! changing the affinity to "all" completely eliminated all my horrible stutters!! Will experiment with lasso

 

i9-7900X 3.3-4.3Ghz 16GB Win10 Pro 64 GTX 1080Ti Acer XB321HK TM Warthog MFG TIR5 GT Omega Pro/ButtKickerx1/WheelStandPro Playseat/ButtKickerx2


Edited by bighead

TM Warthog MFG TIR5 GT Omega Pro/ButKickerx1/WheelStandPro Playseat/ButKickerx2

Link to comment
Share on other sites

  • 3 months later...

Intel® Turbo Boost Max Technology 3.0 causes one core affinity

 

I can confirm, that Intel® Turbo Boost Max Technology 3.0 causes DCS.exe affinity to one core only.

Disabling Intel Turbo solves the problem.

This strange behavior occured after last WIN10 1809 upgrade

 

MB: MSI with X299 chipset; CPU: i7-7820x

i7-7820X@4.5Ghz; GPU 3080Ti, 64GB RAM, HP Reverb G2; VKB Ultimate stick; VIRPIL Throttle; Slaw Pedals; custom AX&BTN BOX

 

Link to comment
Share on other sites

  • 2 weeks later...
I can confirm, that Intel® Turbo Boost Max Technology 3.0 causes DCS.exe affinity to one core only.

Disabling Intel Turbo solves the problem.

This strange behavior occured after last WIN10 1809 upgrade

 

MB: MSI with X299 chipset; CPU: i7-7820x

 

Interesting thread gents. I will have to give this a try and see if it works for me as well.

Link to comment
Share on other sites

Well I tried it and wow! It did work and solved all my issues I had with DCS. Who would have thought. Everything is now smooth as silk, lowest FPS I'm getting is 60 which includes flying down in the weeds in the big cities. I'm running everything on high, visibility on Ultra at resolution of 2560X1440.

 

Thank you for this thread and this find. I can now enjoy DCS on this new rig.

Link to comment
Share on other sites

  • 4 weeks later...
All,

 

So I was having some seriously frustrating issues in the latest 2.5 beta with F-18 and the Persian Gulf map. I'd load a simple MP mission up and the ground textures wouldn't load. Cockpit textures would be all solid black.

 

Sometimes textures would load but if I went to the F10 map, and then back to the cockpit, the ground textures would disappear...

 

Long story short - after alot of messing about with settings (None of which made a difference), I discovered that DCS.exe was defaulting to use only one core of my 6 core/12 thread CPU.

 

Manually going into taskman and setting it to all cores, fixes all my issues. I can now run DCS with high settings and zero stutter or strange texture behaviour.

 

But... I have to do this every single time I launch DCS. I can't figure out why it continues to default to CPU0, but at least this work-around is easy.

 

Anybody else notice or experience similar behaviour?

 

Cheers,

Mack

 

I have to confirm it, this thing took me quite some time to discover.

However, I can finally run DCS in VR with acceptable fps.

-=3DArtistExtreme=-

Modeling/UV mapping/Lighting/Shading/Texturing

3D Portfolio http://www.oleg-kovalev.com

FlyingIron Simulations

Link to comment
Share on other sites

Some of my buds had same prob. As Wrl11 mentioned above, Process Lasso works well to manage CPU and stop recurrent defaulting to CPU0

A Co, 229th AHB, 1st Cav Div

ASUS Prime Z370-A MB, Intel Core i7 8700K 5.0GHz OC'd, RTX 3090, 32GB DDR4, 1TB SSD, Win 10

Samsung 65" 4K Curved Display (Oculus Rift occaisionally), Track IR5, VoiceAttack, Baur's BRD-N Cyclic base/Virpil T-50CM Grip, UH-1h Collective by Microhelis & OE-XAM Pedals. JetSeat & SimShaker for Aviators.

JUST CHOPPERS

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...