scommander2

Hi @JohnRedcorn, let me share what I know about it (I may not say 100% correct since I am an UNIX person not a Windows guy. In UNIX world, there is no CPU park rather than CPU idle/bound). The Power service profile with 100% (High performance) with the sub-item processor power management is where I can set the minimum and maximum CPU unitization percentages. And, I do make both min/max 100% to use them possible. About the CPU parking disable, I guess/think that an entry in the registry to be zero from 100 to make Windows not to park a CPU possible. I think that both are important for me to ensure the CPU performance/availability when dcs.exe needs the CPU resource. Well, will these options work for everyone, it is hard to tell

Process Lasso Testing Initial Setup Launch DCS first Select dcs.exe and set CPU affinity for all P-Cores: select dcs.exe and set CPU priority "Above Normal": verify the above settings for: 1. CPU affinity with all P-Cores and CPU priority "Above Normal": check task manager for the CPU metrics as well as Game bar: Exit DCS Relaunch DCS and verify task manager (details) for: CPU affinity - no longer to set again CPU priority - no longer to adjust again Reboot my system Launch DCS and verify with task manager (details) for: CPU affinity - all P-Cores are assign for dcs.exe CPU priority - running as "Above Normal" Conclusion Process Lasso and ParkControl are very good software to handle: 1. CPU parking disable/enable (ParkControl only) 2. Core scheduling 3. CPU affinity with the specified core(s) 4. CPU priority for the specified process 5. more features, but the above features are good for DCS so far. However, these two software are running in the background when Windows starts up. CPU Unpark is one time setup with the minimum features but the app terminated when the user closes it. My powershell script is for adjusting CPU affinity and CPU priority, but it is required to be executed after the new DCS launched for every time.

A real user tested with 285K (not DCS) in general from YouTube: With the recent DCS release, I think that the 285K P-cores should work the same way as 14900K P-cores with the better TDP.

CPU8 Affinity on/off Testing For one minute testing Before turning off the CPU8 affinity, I took the the resource screenshot: nullAfter turning off the CPU8 affinity, I took the the resource screenshot again: For ten minutes+ testing For "Before turning off the CPU8 affinity", I found that FPS went up and down very often sometimes. For " nullAfter turning off the CPU8 affinity", it seemed that FPS was more stable in the most of time. It is very interesting finding. Is it the implementation issue in DCS? Hi @jackd, "Support" is the ED tech support? Thanks.

Wow... thanks because of the bitwise issue due to the most significant bit? I will give a try tonight. Right. I think that bitsum Process Lasso can make the CPU affinity adjustment in real time when dcs.exe is launched according to SP's video, but I have not tried it yet.

Thank you so much....

Yes, I concur, and it is an excellent observation. My test case "Test1" for F-14 take off from Afgh airfield is very heavy load of the AI objects (alive or static) on the ground, and air (higher) is the best FPS I can have. When CPU BOUND is kicked in the FPS gets drop because of E-cores is part of it and I do not want my cockpit is running with CPU BOUND with E-cores. Therefore, P-cores have to dominate the entire dcx.exe execution time because I have no idea when DCS will make GPU BOUND or CPU BOUND based on the dcs algorithm. Ideally, the first view (what I see currently) should be GPU BOUND (foreground with the best view and FPS) and whatever objects (background) behinds my view should be CPU BOUND so that the entire system will be balanced and not waste any resources rather than context switching between GPU/CPU (speaking from the UNIX multitasking standpoint).

Hi @JohnRedcorn, thanks... I have the CPU affinity for dcs.exe with all of P-Cores to ensure that all of threads (included the DCS main process) are running the best loads as possible.

I find "bitsum high performance profile" if I enable it from Settings->Experimental.

That's right, people maybe hold on the upgrade if they have 13th/14th gen due to performance beside lower TDP (if it is not a big concern) according to few reviews. For people owning 12th gen, it is an option to consider 15th gen according to the reviews also.

@jackd, oh.. sorry not to mention it. I have created my own power plan for the screen saver if I am away for a while, But the rest of settings should be identical to "high performance", especially processor min/max management. About the bitsum power plan, I have no ideal. Is it because of mime is the paid version?! Not sure...

Testing With ParkControl and other adjustments Thanks for @jackd suggestions, and I have tried different settings with my new objectives: To obtain 60 FPS (pre-set in Nvidia Control Panel and DCS options) and not over kill my system To utilize P-Cores as many as possible. To leave E-Cores for other tasks or helpers for P-Cores if too busy to handle. Re-test the test case "Test1" for CPU/GPU metrics v.s. FPS ParkControl Installed Bitsum ParkControl and adjusted options according to my objectives to have the long-life tasks to be assigned to P-Cores possible, other tasks (included all background prcoesses) will be handled by E-Cores: Affinity/Priority Re-adjusted my P-Cores affinity with dcs.exe possible, and made dcs.exe priority ("Above normal") a little bit higher most of all processes: : set CPU affinity to the process : : Binary to Decimal at https://www.rapidtables.com/convert/number/hex-to-decimal.html : For example for 20 CPUs (P-Cores) : Binary = 11111111111111111111 : Decimal = 1048575 : "1" - select : "0" - not select : powershell.exe "$process = Get-Process dcs; $process.ProcessorAffinity = 4095" : : sets process with the specified priority : : Priorities are: : Realtime -> 256 : High -> 128 : Above normal -> 32768 : Normal -> 32 : Below normal -> 16384 : Low -> 64 : powershell.exe "gwmi win32_process -f 'name=\"dcs.exe\"' | foreach-object { $_.setPriority( 32768 ) }" CPU/GPU metrics With the test case "Test1", it was about 50-55 FPS at the airfield and 60 FPS in air with the following metrics: Conclusion Overall, the 60 FPS is possible in the most cases (instant action and multiplayer), and GPU / CPU BOUNDs are based on the views (F2, F3 ..., F10). I will perform more tests for more findings.

Assume T.A.R.G.T. GUI is able to detect the throttle. Does the throttle show on OPTIONS->CONTROLS on the top column of the listed devices? If yes, go bottom for "Axis Assign" to adjust the bindings... If not, "Rescan Device" for scaning all devices again.

Thanks, it is a good quote, and people are mentioning about

Since Arrow Lake is no longer supplied hyperthreading so the heavy lift CPUs are equals to the actual count of P-cores. However, some people do disable the hyperthreading feature from BIOS due to the FPS issue since the MT release, therefore, I think that it does not make lots of differences while running with the Arrow Lake. Is the Arrow Lake a gaming CPU? People are still taking about...

I guess that Steam users have to wait again :-{

Thanks!!

- [ADDED] RIO cannot transmit (or rather get response) through his radio anymore {https://forum.dcs.world/topic/359096-new-to-realistic-radio-no-working-both-setting-and-rio-can-only-talk-on-one-radio/#comment-5536878} Tracked it now.

Thanks for checking. My CPU is the "H" model, and there is no overclock option on my system.

I am not sure that "Scale GUI" will cause FPS drops since I have the 4K 3840x2160 monitor and I set it for 1.25.

HB said that there is insufficient information for AN/APG-71 so the answer is no

Priority / Affinity for dcs.exe I have discovered that "Selected Launch Option" has the limited options and it can't take "-high" for the priority setting. The following cmd script will make changes for affinity and priority: : set CPU affinity to the process : : Binary to Decimal at https://www.rapidtables.com/convert/number/hex-to-decimal.html : For example for 20 CPUs (P-Cores) : Binary = 11111111111111111111 : Decimal = 1048575 : "1" - select : "0" - not select : powershell.exe "$process = Get-Process dcs; $process.ProcessorAffinity = 1048575" : : sets process with the specified priority : : Priorities are: : Realtime -> 256 : High -> 128 : Above normal -> 32768 : Normal -> 32 : Below normal -> 16384 : Low -> 64 : powershell.exe "gwmi win32_process -f 'name=\"dcs.exe\"' | foreach-object { $_.setPriority( 32768 ) }" save the contents into a file with ".cmd" and make sure the permissions to execute the cmd file. To execute the cmd file after dcs.exe is up and running.

Yes, I did... It's okay now... Thanks!!

Thanks.... I just clicked the button instead...

The following is my testing regarding the CPU affinity with dcs.exe. My CPU is i9-13900H, and P-cores and total CPUs can be set according to the Intel web site: ** NOTE: my Nvidia Control Panel has limited 60 FPS as well as DCS Max FPS ** (Do not want to overkill my system) Enable Window Game bar for the following tests: With the affinity of 20 CPUs: With the affinity of 10 CPUs: As soon as I do "Task Manager"->"Details"->"dcs.exe"->"Set Affinity"->"All Processors"->"OK", my FPS is back 53 and stable. My finding When I did all core unparking, and it made all P-cores available to the most of processes regardless priorities. The video that I posted in the previous post was set the affinity to dcs.exe with all P-cores, and not other window processes. There is my dcs.exe found in the task manager with all core unparking: The priority of dcs.exe is normal and my AV priority even higher than doc.exe. I think that I can set dcs.exe priority to high (mentioned in the video also) by doing "Task Manager"->"Details"->"Set Priority" (with selected dcs.exe shown above)->"High" so that dcs.exe can be scheduled into all P-cores in the most runtime possible. When I set "High", the FPS does not increase and I hope that dcs.exe should better and smooth. I need to test more to find out. Thanks.