BJ55

@Miro you have parked cores.

I was referring at the ME trigger.

Thank you @TOViper , I wasn't aware of that setting. (chiedo anche scusa per la piccola parentesi in inglese.)

@Skyracer : what's your RAM clock? After the recent updates I've noticed a big drop in performance due to RAM usage, in high density areas it goes from a stutterfest with 2400MHz to a barely usable simulator with XMP1 3000MHz. Since they introduced the new fog and volumetric lights there's also more system load, so it's better to reduce preload radius to 50000-60000, visib range to high, disable shadows blur and heat blur... With the hope that they fix the rendering core stuck at 100% https://forum.dcs.world/topic/368620-one-or-more-cores-reaching-100/ Lots of "ANTIFREEZE ENABLED" even in your log. There's no virus, only false positives due to how current malware detection works.

You have to edit the images inside the .miz contained in DCS World\Mods\aircraft\F-4E\Missions\Training\ folder (open with 7zip, go to KNEEBOARD\IMAGES\ , extract and resize images with an editor, overwrite the images in the .miz with the new ones). It's better to ask these questions in the Heatblur section, so they're aware of a potential readability issue.

Since last update SAU/Autopilot stabilization is flooding dcs.log with "Flightmodel (Main): filter stick" entries. Best regards. dcs stab on.log dcs stab off.log

Yup, but I see it in a different way: the smart AV developers and programmers must fix the false positive issues of their products.

Btw: I was able to riproduce the issue with a simple RAM downclock (XMP1 3600 -> 2400), removing dust in ME made no difference (in a custom mission the new fog was causing heavy stutters), only removing static objects made some difference. Both Kandahar and Baghdad areas are a nightmare for my rig, but I suspect that there are other bugs that are contributing to the performance issues. Edit: https://forum.dcs.world/topic/355693-huge-sp-performance-degradation-with-29758923-and-29658056-compared-to-dcs-29555918/page/3/#findComment-5506276 dcs log F14B_IA_Afghanistan_Cold Start no dust.log

A dcs.log could be useful... I have no such issues with that mission, but I use less demanding settings. Try with res. cockpit 1024, SSAO off, heat blur off, grass 800, preload 50000-60000 (use bigger values only if you have slow disks), max FPS 90. 7680x1080 are a lot of pixels to render!

Use any search engine and you'll find thousands of articles and user reports about the issue. Have yet to test the latest screwdriver, maybe next week, but since 560 series I've only observed performance degradation and problems. Some users don't agree... https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/559105/geforce-grd-57270-feedback-thread-released-3525/

Had the same results (109mil), that's because at that altitude and with that speed bombs are released when you depress the button (target range=release range), it's like a Direct bombing profile. When you have some spare time, try with different altitudes (500, 1000, 1500).

From the resmon graphs it seems to me that any program tested is using perf2 cores for rendering, perf1 cores for rendering/common and perf0 for IO, the only one with a stuck core while idle is DCS. (be aware that my W10pro installations are highly customized/debloated for performance and with updates disabled after last stable) I'm so lucky that the HW required for my CAD-CAM is not compatible with W11, so for at least 2y I will keep W10 on all WS/PC, EOS doesn't mean that it will stop working the day after, it takes a total rewrite of DCS core engine to cause potential issues. (hate W11 UI, instability and new spyware) As I said MSI AB is used only for fan control (with 50-54°C, without 65-70°C), I always use only NVCP for change settings, if needed. Avoid ASUS sw like the plague, in particular Armoury Crate or any other phoning home "feature" installed in the BIOS. Totally agree, my next machines will be all AMD.

I'm curious about this, overall I have a good performance in SP, except in high density areas or with a huge number of units. I only use MSI AB for fan control, custom balanced energy plan and GPU at prefer max. perf. Do you think I need PL? The cores stuck at 100% is a regression that will be fixed with the next patch? dcs.log DxDiag.txt

Not a shader issue, there are too many objects to render, if you add all the computations for systems and units you reach the point where the hardware can't handle anymore, AH-64 @ Baghdad is even worse (512, med textures, no shadows, LOD at 0.8, 2x MSAA or DLSS, with VID feed = 40-50 FPS). This is a general issue and I don't expect both eye-candy, full-fidelty systems and performance at the same time... Maybe some more code optimization and add an option to reduce scenery objects? (quantity, not LOD)

Something's missing in your power options: You can also download the freeware Bitsum ParkControl and turn off parking for both P E cores. In Settings disable "start at login", once configured there's no need to run the program in background.

I know that (sadly) it's bugged and unmaintained, but at least the PCM meaning is explained in the manual.

The rudder is inverted.

I had problems at Kandahar too, after some tests I've found that performance issues are mission related, below the comparison with landing at Bagram from a TTI mission and from a ME custom mission with only 2+2 units: Later today I will test a complex ME mission. Edit: confirmed, on my PC multiple units can cause massive stuttering above Kabul.

Plenty of similar reports here: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/557655/geforce-grd-57247-feedback-thread-released-22025/ , install previous drivers, don't install NV app. 552.44 is OK, not perfect like 314.22 but...

@Aero4000 : have you tried with no axis deadzones in controls settings? I had the same sensations until I've set deadzone to 0 and curvature to 15, firmware deadzones are enough, now it's smooth and predictable. Deadzones caused near center lack of precision with other aircrafts too.

Here's the mission/track/screenshots. Starting point-IP 10nm, IP-TGT 2.5nm, put in active pause to fill the bombing calculator and set the weapons system, hit shift-F10 once to hide labels, turn off active pause, stabilize the aircraft for the run. F-4_ag_train_cauc_82SE.zip