AJaromir

O.k. Now I am like 90% sure it is caused by Nvidia App https://www.nvidia.com/en-us/software/nvidia-app/ I'm not sure if I should start a new thread on this topic.

Please try to uninstall Nvidia App if you have it.

@silverdevil Do you have GeForce Experience or Nvidia app? Looks like once I uninstalled the Nvidia App, it stopped freezing. I have to try it about 50 more times to be sure.

Yes. I tried to run slow repair. My personal opinion is the Issue is most probably in the "aircraft select" window. Because every time I reset the filter or switch to another plane, the game freezes every time. But every time it comes back on within a few seconds. It just always depends on the first selection. If that one doesn't freeze, then everything works relatively normally.

This is how the crash looks like: When I clicked by mouse on A-10CII, the game had frozen with not-responding message. Waiting solves nothing. Tried to wait like 10 minutes. Here is the full debug log: dcs.log This is where the freeze happens:

As if on purpose, when I try to take a video of the game crashing (by Nvidia App), the game never crashes.

O.k. TrackIR nor any controller have no effect on the issue. I tried to select aircraft in MP session with all devices unplugged, but crash still occurs.

I've noticed that TrackIR5 often crashes when the game crashes. Could this be related?

Yes. Check my other posts. It looks like this is how DCS load MP missions.

It seems to help prevent freezing after setting the filter in the aircraft selection to wait 10-20 seconds before clicking on the machine.

New attemp. Before starting the game the "tracks" and "logs" folder deleted Tried different server than before. dcs.log

For the next test I deleted the whole tracks folder and logs folder. Now the game definitely crashed. Here is the log: dcs.log

What about it? As I have written. It happens when I click on the aircraft in the aircraft select menu. Game stops responding. I can wait 10 minutes but nothing happens. I am loading MULTIPLAYER mission from the multiplayer list of servers.

For unknown reason this crash does not happen every time. It is like 1 out of 5 attemps result in no crash. No matter which aircraft I choose.

For first time game freezes - Not responding. I tried to wait few minutes, but no joy. This happens since the last two updates. OS Windows 11 24H2 MB: ASUS ROG STRIX Z790H Gaming WIFI CPU: Core I9 - 13900KF RAM: 64GB G.Skill DDR5 Ripjaws S5 5600MHz CL28 Dual Channel Kit 2x 32GB GPU: MSI GeForce RTX 4090 VENTUS 3X E 24G OC SSD: Samsung 990 PRO 2TB No mods used Whole DCS folder is set in antivirus exception list (defender) dcs.log

From manual, page 33: When the fuel selector (fuel cock) [11] is set to "Auf", both fuel lines from the forward and rear tanks are allowed to feed fuel to the booster pump. The booster pump draws more fuel than actually needed from both tanks and the surplus is routed back into the forward tank, thereby closing the valve for the forward tank. With this mechanism fuel effectively is drawn only from the rear tank as long as the engine gets enough fuel from it. When the engine pump starts to starve, the forward tank is "opened".

From the manual - page 33: When the fuel selector (fuel cock) [11] is set to "Auf", both fuel lines from the forward and rear tanks are allowed to feed fuel to the booster pump. The booster pump draws more fuel than actually needed from both tanks and the surplus is routed back into the forward tank, thereby closing the valve for the forward tank. With this mechanism fuel effectively is drawn only from the rear tank as long as the engine gets enough fuel from it. When the engine pump starts to starve, the forward tank is "opened". If I understand correctly, an excess should cause the highlighted non-return valve to close. I deliberately had the front fuel pump off and the rear fuel pump on, and tried flying 1km above the ground in the most economical mode, but even then the behaviour described in the manual did not happen. Fuel continued to be drawn evenly from both tanks. The only way to stop fuel being drawn from the front tank was to manually close the fuel valve. Considering that the behavior of the system does not match the description in the manual, I consider it a bug.

This is the P-51D Normandy cold start instant action. Check the shadows at 3D objects

You think it is possible to overflow 24GB VRAM and 64GB RAM in main menu?

No. I have set "leave the decision to the 3d application" for everything. Today i turned the game again and the issue is back. Seems like it happens randomly. Something is parking. But I don't know what because all cores are unparked.

After like 10 game restarts it finally works without stutters. I really don't understand what happened.

As you can see in the video. Once I set FPS limit to 150, everything is instantly fine. Bellow that the suttering occurs. Core parking is forcibly disabled in the windows registries. ASUS ROG STRIX Z790H GAMING WIFI Core I9 13900KF Arctic Liquid freezer III 360 G.skill Ripjaws S5 DDR5-5600 CL28-34-34-89 1.35V 64GB (2x32GB) Intel XMP Samsung 990 PRO NVMe SSD 2TB MSI RTX 4090 VENTUS 3X OC 24G Nvidia driver version 566.14 Windows 11 home 23H2 22631.4460 144 Hz Display with Gsync enabled, resolution 2560*1440

Thank You. Will do that. But as other features added like "diable hot plug" Which had been possible only by commands like this one, it would also be implemented into GUI.

Tracks takes relatively a lot of space on drive when those are not deleted time to time. I would like to have ability do disable tracks. This will also lower some SSD wear by reducing TBW.

There is almost no info about laser range finder and need to cool it down to prevent burnout and making it unusable. Many times I edned with remaining missiles which I was not able to shoot because the laser burnouted. All info about need to cool down laser in manual. Page 316, captcher 8-8 Page 323, captcher 8-15 The problem with the information written in picture bellow is that it only applies to one "special" mode. Not to the laser rangefinder in general. Page 443, captcher 11-27