15 FPS in main menu

[Tygaris]

  Hi,

5900X, 32 GB, RX 6800, Reverb G2 here. I always had issues with the MT & OpenXR version, but it worked okay'ish when I set SteamVR as the OpenXR runtime. It's not headset related because other VR games run as expected.

Since the 2.9 update it got worse. The main menu launches with around 20fps and then drops down to 15fps. Even worse in game where it drops to single digits. I set the graphics to Low, but the frame rate remains the same. Removed all DCS files (installation and save games) and reinstalled it. Just the base game without any additional modules, still the same problem.

I changed the OpenXR runtime to SteamVR and the main menu is at 40fps. But that's still bad compared to previous versions, even before MT support.

One thing I noticed is that the first core is at 100% while the GPU is taking a day off. With SteamVR the workload on the cores is much more distributed and the GPU is maxed out. Before anyone asks: yes, I'm launching the EXE from the bin-mt folder. But the huge fps difference between OpenXR and SteamVR happens with the single-threaded one, too. Looking forward to a fix or a hint.

Help? (making Puss-in-Boots face)

M.

dcs.log DxDiag.txt

[Flappie]

You have all the symptoms of this issue:

 

[Tygaris]

23 hours ago, Flappie said:

You have all the symptoms of this issue:

 

Thanks for the hint.

I tried changing the cpu affinity but sadly the problem still exists. It just moved to the next core and so on and so on. Disabled the first 4 cores but: nope

I have this issue only in VR. If I disable it, the main menu is at around 100fps and no core is at 100%, and it's GPU bound.

Edited October 22, 2023 by Tygaris

[Flappie]

There's a new workaround in town and it seems to work for many.

Try disabling core parking:

 

Edited October 22, 2023 by Flappie

[QuiGon]

On 10/21/2023 at 7:06 PM, Flappie said:

You have all the symptoms of this issue:

 

It doesn't look like the same issue to me tbh. To me this seems to be quite a different issue. @Tygaris has no freezes in the main menu, but rather poor performance as he uses VR, where 3D imagery is being rendered in the main menu. To me this seems to be an issue with the VR renderer, especially as there is such a big difference between OpenXR and SteamVR. I don't really see a relation to the issue that you linked there @Flappie, so I'm not surprised to see that the affinity workaround didn't work for @Tygaris.

Edited October 23, 2023 by QuiGon

[Flappie]

@QuiGon I saw CPU0 at 100%. Isn't it the main symptom?

[jeepster]

in 2.8 i saw 90fps in main menu and f10-map, after updating to 2.9 there are 25 frames left. while playing missions frames are ok.

using an options preset without any new settings.

G2, RTX3090, 64GB RAM

Any ideas what’s going wrong?

 

Edited October 23, 2023 by jeepster

[QuiGon]

On 10/23/2023 at 7:21 PM, Flappie said:

@QuiGon I saw CPU0 at 100%. Isn't it the main symptom?

No, 100% core utilization isn't an issue. I have that all the time when I run DCS, even if DCS works absolutely smooth and flawless.
Quite on the contrary: I would be annoyed if the DCS main thread wouldn't utilize all the available power of the core its running on

Edited October 24, 2023 by QuiGon

[Flappie]

I meant only one CPU at 100%.

Edited October 28, 2023 by Flappie

[Tygaris]

Managed to get decent frame rates again, after I set SteamVR as the default OpenXR runtime and not Windows Mixed Reality.
90Hz in main menu and 35-60 on Sinai with nearly everything on "High". Works for me now again.

[Tygaris]

For the record:

My problem hasn't been solved! It's still there, but I'm able to jump through some hoops to make it disappear.
There is still an issue with DCS MT + OpenXR (WMR).

[Rapierarch]

On 10/22/2023 at 7:00 PM, Flappie said:

There's a new workaround in town and it seems to work for many.

Try disabling core parking:

 

 

Hey @Flappie,

I don't believe disabling core parking is a wise decision on ryzen processors. Their boost algorithm somehow depends on that. 

If you don't use core parking scheduler will move threads from one core to the next instead of keeping them closer in the same CCD or CCX which will itself show stutters and put heavy load on memory bus only.

I believe whatever that Dx11 thing is doing to run vulkan shaders masked behind is doing this and I guess ED developers can tell vulkan api not to do that and can tell how to utilize each cpu but they cannot do it in DX11.