scommander2

May I suggest that can we setup the processor affinity to all P-cores only through Task Manager manually for testing? Based on the last graph, E-cores had lots of activities...

It seems that we are back to the ST version.

A quick question: one core was at 100% when landed on the main dashboard or in the flight? I am also a steam user, and I am not sure that there is lots of differences between standalone and steam. I do see one core slightly higher CPU usage than other cores while I am at the main dashboard. All P-cores are kind almost same loads while I am in the flight.

It is very generosity.

I could not.

TL;DR I think that RIO wheel has the different selections to select the loadout from 2 to 7. Once the selection is made, and I can press ACM to make the jettison but not rails and racks.

No, it is correct. DCS uses vCPU instead and it is same as Task manager processor affinity due to hyper-threading for all P-Cores. And, PL looks the physical cores on another hand. So, sorry that it is the interoperation issue. Yes, I agree that we want the DCS render/common cores are on all P-Cores not E-Cores. About the 8th core, it should go by DCS counts or PL counts and it is very questionable since the different CPUs have different P-Core counts. Go back to the topic: I disabled the 8th core according to DCS counts and it did not make different in my environment.

Not for my case. According to my doc.log: common cores: {8, 9, 10, 11} render cores: {4, 5, 6, 7, 0, 1, 2, 3} IO cores: {12, 13, 14, 15, 16, 17, 18, 19} unavailable cores: {} My P-cores are from 0 to 11 for i9-13900 CPU. The 8th core is my P-core. I will test for unclicking the 8th CPU from the process affinity.

Someone did make off for the 8th core in affinity for the related issue and there was a thread about it. I have checked ED tech support for the benefit of offing 8th core from the process affinity, and the tech support could not provide an explanation about this setting. However, tech support said that if it works for users and why not.

UFO?

It's kid different: DLSS is primarily focused on improving performance by upscaling from a lower resolution, while DLAA focuses on enhancing visual quality at native resolution.

For me, there is no selection for it. So, I have to enter it. The option might not show for you (I guess), so please enter it from keyboard.

5090 is a powerful GPU. However, the CPU/GPU bound context switching is more frequently in the recent patches and It does not help for the powerful GPU owners. I guess?!

Thanks for entering the request and a good catch Right, I can't rollback DCS version through the openbeta option, and the dcs update is for the standalone only

Can I assume that Windows has been configured to the resolution for "the monitor" as 3840x2160? In DCS:

Thanks @mazex for the post, I do experience the flickering issue with the preset K.

Thanks, @Ramsay, Indeed...

I have asked the question. For the recent few patches, it is hard to keep GPU bound only rather than GPU/CPU bounding around. There are few threads about the performance issues here and there, and no answer why. Now, we have another new issue of the CPU gets higher temperature.

@rob10, thanks for the comment. So, it is more for the backward support...

A quick question: The recent release has shipped the latest DLSS, why the "DLSS_Preset" option is required in autoexec.cfg? Thanks.

Thanks for informing me. The following entry has been moved to the "closed" section: - refueling light gain: https://forum.dcs.world/topic/245592-refuelling-probe-light/?do=findComment&comment=4428642 {https://discordapp.com/channels/1071433028045377637/1076903951791816807} I need to find time to try it out

It is a good question. Hope HB has enough information for AN/APG-71, then F-14D may be possible

No problem, thanks!

About the full syntax of autoexec.cfg likes below? dx11backend = { DLSS_Preset = 'K', } Thanks.

oh, okay and thanks. I was asking that DCS does not have the option in the game self.