AdrianL

Try creating a new power plan, using high performance as its base

The problem with the video is that it says to search once. The setting needs to be applied to your active power plan, which might not be the first one found in the registry. Download CPU Unpark (Does not need to be installed) and see what the parking index is. You want it to be 100 for the active power plan. You might need to reboot. See

See if you have parked cores. If so, the disable CPU parking. You might need to reboot

Default most likely would been 4, for later Intel CPUs. Just move the slider to the left until you see 4 and press apply. Or just reset the entire power plan. Edit Power Plan, set another power plan active, select the the power plan you want to reset and then 'Restore plan defaults'. Then set that power plan active again Did it help with your stuttering / freezing issue?

Yes. It just gives more options so make sure you know what they do

Going to recommend people use CPU Unpark https://coderbag.com/programming-c/disable-cpu-core-parking-utility Much easier than messing with registry or command lines. Download and run. Nothing to install. Make sure the slider is on 100% for the selected power plan. Press apply and you done. No need to use the app again. Note it does need .NET Framework 4.6.1 installed but most PCs will have that by now

The maxed out core will be the main rendering thread. Usage of your other threads will be based on what is happening in the mission at any point in time. Threads will never be evenly used

2nd cmd is different to the first. Ending in 83 is power core. Ending in 84 is e-core. PCore: powercfg -attributes 54533251-82be-4824-96c1-47b60b740d00 0cc5b647-c1df-4637-891a-dec35c318583 -ATTRIB_HIDE ECore: powercfg -attributes 54533251-82be-4824-96c1-47b60b740d00 0cc5b647-c1df-4637-891a-dec35c318584 -ATTRIB_HIDE Also the setting seems unintuitive to me. 100% means no parking. Zero means allow parking for all cores. Reading the setting I expected it to be the other way around Scary how many settings are hidden. But they also generally hidden as you can have issues with some of them if the setting is not fully understood.

powercfg -attributes 54533251-82be-4824-96c1-47b60b740d00 0cc5b647-c1df-4637-891a-dec35c318584 -ATTRIB_HIDE will show the E-Core setting in the power plan. But my understanding is this should be left alone i.e. will be zero. Mine is set to zero. The issue with CPU8/CPU0 affinity on startup is related to power cores. None of your power cores should be parked. In your DCS log it will log out what it considers P or E-cores. Would check if that matches your CPU

So, by default, the Windows 'High Performance' plan has parking disabled. All other plans will generally have CPU parking enabled. I posted here as to how to check if your power plan has parking disabled

If you do not see the "Processor performance core parking min cores" option under "Processor power management" when viewing a power plan, then you can run the following command from an admin command prompt powercfg -attributes 54533251-82be-4824-96c1-47b60b740d00 0cc5b647-c1df-4637-891a-dec35c318583 -ATTRIB_HIDE If you want to hide it again then change the -ATTRIB_HIDE to +ATTRIB_HIDE 100% means no core parking. This should be the default for the 'High Performance' power plan, as shown in the image in the post above.

It is. Setting is just hidden by default.

The setting needs to be set for your active power plan. So you need to repeat the search on the registry for all items until the power settings key Might be easier to use tool like https://coderbag.com/programming-c/disable-cpu-core-parking-utility Note: By default the High Performance power plan should have parking disabled.

@Flappie So unparking the cores resolved my issue as well. I used CPU Unpark (https://coderbag.com/programming-c/disable-cpu-core-parking-utility), which gives some control over this i.e. you can change it per power plan, no messing with the registry, etc I found that my default parking index was 4% i.e. 96% of my core's were allowed to be parked. By trial and error, setting this to 80% has meant my stutter issue is gone and I no longer need to disable CPU8. And I still get some energy savings when not gaming.

This discord invite still works for me https://discord.gg/7c22BHNSCS

I put this in the target box of the icon shortcut C:\Windows\System32\cmd.exe /C START "" /AFFINITY 0xFFFFFFFFFFFFFEFF "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" Change the path, obviously. You can add any DCS params at the end. The affinity mask will be based on your actual CPU but for the i9-13900 it is the one listed above (See https://bitsum.com/tools/cpu-affinity-calculator/). Also, if you read thru this whole thread, for some it is CPU0, etc. Whatever CPU is maxed when you just start DCS. So the affinity mask needs to change accordingly. If you look at the top of your DCS log you will see it switched off if done correctly, This worked to fix the stuttering issues for me, at least

Yes. Switched to MT when it came out and never had have any freezing / stuttering issues. I followed this thread with interest, wondering why I was not having this issue. Running v2.9 it was a slide show while trying out all the new graphic options. Saw CPU8 maxed, removed affinity and everything was back to normal. I now start DCS from the cmd line with CPU 8 affinity off, using the cmd line method at the bottom of https://bitsum.com/tools/cpu-affinity-calculator/ . Performance has been excellent since

I am always up to date with windows, bios, drivers, etc. I had no issue with v2.8 on Win 11, i9-13900 with HT on. In v2.9 I now need to set CPU affinity to remove CPU8 (Might be different per system)

This is listed as a known issue in the change log.

This is noted in the change log as a known issue. See

See this post. For me it was CPU 8 but see if you have a maxed out CPU. If so, try to remove affinity from that CPU

Definitely was running MT. Separate shortcut pointing to MT folder

So I have been watching this thread with interest. I run Win 11, i9-13900, RTX 3090, Non-VR, 1440p and did not have any of the issues reported here. Game ran very smoothly at 90+ FPS, max settings. But as of v2.9 I now have massive stuttering and need to remove affinity from CPU8 to fix. Removing CPU8 affinity and then adding it back after after DCS starts fixes the issue

See this for detail on the radar changes. https://www.reddit.com/r/hoggit/comments/17bmpph/dcs_29046801_aircraft_radar_ranges_chart_fa18c/

Likely to be 'Screen Space Shadows'. Basically adds shadows using objects visible on the screen for additional fidelity, as it can add shadows to places that shadow maps cannot.