scommander2

Please show photos once the setup is completed

I am wondering if we can disable launcher at startup. Not sure the following thread can off the load of some mods at startup:

nice!!

Hi @YoYo, thanks. A quick question the following options: bkg_load_all_plugins = false with: bkg_load_signed_plugins = false What are differences? Thanks.

Thanks. Then, I guess the 0-core with the 100% load must run the DCS main thread for graphic.

Hi @Special K, according to @Schlomo1933 CPU usage: with his dcs.log: common cores: {8, 9, 10, 11, 12, 13, 14, 15} render cores: {0, 1, 2, 3, 4, 5, 6, 7} IO cores: {16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31} unavailable cores: {} It seems that his system uses E-Cores in the most time rather than P-Cores (hope the CPU usage was taken when he was in the flight). However, he set affinity by Task Manager fordcs.exe with all P-Cores 0-15 (with hyper-threading which matched to dcs.log common/render cores), then:

I guess the ship is on the different group and I could not update it back to the group "CSG-1". The group is maxed out.

Hi @Special K, thanks for mentioning and it is a hint... I would like to try out while NV overlay disabled. Again, thanks a lots!!

Thanks... it should be benefit for a campaign. But, is there a tool that able to analyze the captured data to feed the conditions of triggers for the next mission in ME so that the next mission becomes more dynamic? I guess that I ask too much of ahead with the day dreaming

Just wondering what we are going to do for data that captured by TARPs in DCS? Thanks.

Hope that we can be enlighten by @Special K, @Flappie or ED developers. In general, if a process that is the long-time life cycle or bounded by the CPU id in the code then that CPU id is very busy than others, and OS may not swap the process id out to another CPU id less frequently for the scheduling purpose. I am not sure that how DCS is coded. Yes, we are kind pushing all DCS tasks over all P-cores and they are running the high frequency rate, and that is cons.

The 2nd graph seems nice to me since 13900k P-cores is from 0-15 (with hyper-threading). How is the performance for this configuration then?

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?!