After resolving the DCS freezing issue by adjusting the CPU priority, several new problems have emerged

[EX_AI]

Since a DCS update two months ago, the main menu has been freezing. Sometimes it freezes permanently, requiring a computer restart. After nearly half a month of debugging, I found that setting the highest CPU priority for DCS significantly reduces freezing. However, new issues have emerged:

 

1. Slow or crashed startup:
   • Longer loading times when opening the launcher, entering the game from the launcher, and loading into the main menu.
   • Frequent crashes or freezes during the black screen after launching the game or at 0% progress on the initial loading screen.
2. Severe FPS drops when moving the mouse in-game:
   • Occurs less frequently in windowed mode but happens 100% of the time in fullscreen mode after the latest update.
   • Adjusting CPU priority seems to affect the frequency of this issue.

 

I'm unsure if these problems are related and would appreciate solutions for each.

This is the dcs.log file generated when the game crashes after getting stuck at 0% on the loading screen with the highest CPU priority enabled:

dcs.log

[EX_AI]

There seems to be a fundamental difference in CPU allocation when the highest CPU priority is enabled or disabled.

 

The first image shows the situation when the CPU priority is set to the highest, with the game successfully entering the main menu and functioning properly.

 

The second and third images respectively show the scenario when the CPU priority is set to default, where the game gets stuck at the black screen loading step during startup or freezes after entering the main menu.

 

 

 

 

 

 

 

[EX_AI]

The problems I want to solve are as follows:

 

1. Solve the problem that the game starts extremely slowly after setting the CPU to the highest - priority.
2. Solve the problem that the game occasionally gets stuck on a black screen and the process shows no response during startup.
3. Solve the problem that the frame rate drops sharply when moving the mouse, which occurs irregularly.

[ARM505]

Good luck. This has been an ongoing, no solution problem problem for me.

 

The 'randomly unable to complete loading' with an individual CPU (normally number 8 ) stuck at 100% can be worked around sometimes, or kind of solved by Process Lasso or something similar, but that hasn't proved to be a full solution for me (it doesn't always work). I'm using VR as well, and when using VR, I get significant 'pauses' or stutters after a while, similar to what you describe when using the mouse - somehow, ALT-tabbing out of DCS (it continues to run and respond in VR, but has the 'window is out of focus' message) instantly restores frame rates to a silky smooth 72 fps (my default with my Oculus Rift 3). After a while, the stutters will restart, and again ALT-tabbing stops them for a while. So the PC is able to output silky smooth stutter free play, but for some reason DCS just doesn't want to do that.

 

I've kind of given up. I'm hoping they find some magical fix, but it's just terrible. No amount of reinstalling, updates, tweaks etc have helped. There was a time it was working, but one of the updates just borked it and it's never gotten fixed for me.

[ARM505]

Oh, and regarding the mouse issue, ED apparently fixed the 'high mouse polling rate' problem, but now I'm reading it may not have been solved. Try lowering your mouse polling rate? It's a quick and easy to do test.

 

 

Edited 12 hours ago by ARM505

[EX_AI]

2小时前，ARM505说：

哦，关于鼠标问题，ED 显然修复了“高鼠标轮询率”问题，但现在我正在阅读它可能还没有得到解决。尝试降低鼠标轮询率？这是一个快速而容易进行的测试。

 

 

In fact, just as I described in the third point, the frame rate issue caused by mouse movement is quite strange. Sometimes it doesn't occur when I launch the game, and sometimes it does, and I can't find a pattern to it. I tried lowering the polling rate to 500, but the problem didn't go away and still maintained the aforementioned odd characteristics.

 

However, there's one thing I think is worth noting: when this issue occurs, the CPU performance graph is similar to the second and third graphs on the second floor. What's more, when I move the mouse quickly, I can see the occupancy rate of one of the cores shoot up to 100% in no time. When the issue doesn't occur, the CPU performance is close to what's shown in the first graph, and there's no obvious or sharp change in the CPU performance graph when I move the mouse quickly.

[Pikey]

This appears to be the polling rate issue for the OP. It had all but been solved for most hardware some months back. If you have another mouse lying around, try it out and see. There might be some old communications about it. There's more information out there I'm sure, but you'll need to provide more specific hardware details, its a hardware based problem.

[EX_AI]

56分钟前，Pikey说：

This appears to be the polling rate issue for the OP. It had all but been solved for most hardware some months back. If you have another mouse lying around, try it out and see. There might be some old communications about it. There's more information out there I'm sure, but you'll need to provide more specific hardware details, its a hardware based problem.

What information is needed? My mouse is a Logitech G502, and the polling rate is 1000Hz.

[Steel Jaw]

Monkeying around with cpu priorities has never worked for me.  I gave it up as a waste of time.