Terrain textures high DESTROYS framerates

[Nedum]

On 7/24/2023 at 1:03 PM, Nealius said:

With the 2.8 updates of the last couple of months, my system has been increasingly unable to deal with high terrain textures.

In attached mission, sitting in an F-15E at Nellis, with terrain textures low and textures medium, I get a solid 40fps looking towards Las Vegas. For some reason I get a dip in the 30s and some stutters when looking north/northeast, but still playable. 

However, change the terrain textures to high and I get 26fps looking towards Las Vegas, and down in the teens when looking at Sunrise Mountain.

I don't really understand what's going on.

Specs: i5-9600k at 4.7Ghz, RTX3060 12GB, 32GB DDR4, SSDs, 32GB pagefile, Quest 2 at 72hz 1.2x resolution. DCS settings when issue is experienced

Is it a hardware issue, something with DCS, or something with NTTR/Nellis?  

02-Nellis Ranges Sunset.miz 69.55 kB · 4 downloads DxDiag.txt 97.09 kB · 8 downloads

 

What about all of your VR settings?

Link cable or not? Is ASW active? Do you use tools? If yes, what tools, release version and what settings?

Sometimes a tool-setting, never interact with DCS settings before, does suddenly stuff (because now it interacts with DCS) it never did before.

And, as always, do you use mods and did you a slow repair?

[Raven (Elysian Angel)]

12 minutes ago, Nedum said:

It looks like, you are CPU bound. I can't see an issue with the VRAM.

Did you all the stuff with the slow repair, no mods and so on?

Yes the game says “cpu bound” in those instances because it’s constantly swapping textures in and out. I know the VRAM is full because other utilities told me so, and it’s pretty obvious in-game.

It doesn’t actually mean “CPU-bound” but it  means “something else than graphics card-bound”.

 

And no I never use mods and of course I have a pure client.

4 hours ago, Nealius said:

Runnng a 12GB card, as per opening post.

My comment wasn’t aimed at you. 12GB will be perfectly fine depending on the map and resolution of the headset, like I said in other posts

[Nealius]

15 minutes ago, Nedum said:

What about all of your VR settings?

Link cable or not? Is ASW active? Do you use tools? If yes, what tools, release version and what settings?

Sometimes a tool-setting, never interact with DCS settings before, does suddenly stuff (because now it interacts with DCS) it never did before.

And, as always, do you use mods and did you a slow repair?

All VR settings are in the first post.

Link cable. ASW off. Using OpenXR Toolkit, only the foveated rendering and anti-shake features. Done slow repair numerous times. No changes when removing mods.

One other thing of note is that when checking framerates in MT, prior to the Sinai release update it was telling me that I was CPU bound. Now it's telling me I'm GPU bound on the same settings. 

[Nedum]

11 minutes ago, Nealius said:

All VR settings are in the first post.

Link cable. ASW off. Using OpenXR Toolkit, only the foveated rendering and anti-shake features. Done slow repair numerous times. No changes when removing mods.

One other thing of note is that when checking framerates in MT, prior to the Sinai release update it was telling me that I was CPU bound. Now it's telling me I'm GPU bound on the same settings. 

Couldn't read more about your VR-Setting as Quest 2 at 72hz 1.2x resolution, so I asked about the other stuff.

You are running the Stable or the Open Beta? The reason why I am asking, your system suddenly going from CPU- to GPU-bound and is losing performance, which sounds really strange. It should be the opposite, you should gain performance. That was a problem for some people getting the first DCS-MT build. Some people found out there was an issue with HT (intel)/SMT (AMD). They had to disable it. And for some people it shows up later, after a few updates, even so they were running the DCS-MT build from the start.

Perhaps that could be the "problem"?

 

[Raven (Elysian Angel)]

34 minutes ago, Nealius said:

Now it's telling me I'm GPU bound on the same settings. 

Good, that’s what you’d want, and what MT is all about in the end: alleviating cpu bottlenecks

[Nealius]

31 minutes ago, Nedum said:

You are running the Stable or the Open Beta? The reason why I am asking, your system suddenly going from CPU- to GPU-bound and is losing performance, which sounds really strange. It should be the opposite, you should gain performance. That was a problem for some people getting the first DCS-MT build. Some people found out there was an issue with HT (intel)/SMT (AMD). They had to disable it. And for some people it shows up later, after a few updates, even so they were running the DCS-MT build from the start.

Open Beta, running MT exclusively. In the first builds of MT performance was great. After Sinai release was when it went sour for me. I'm on 9th gen Intel so I don't think my chip even has HT on it. 

[Lange_666]

My 4th gen Intel had already HT so yours should do to.

[Nealius]

5 hours ago, Lange_666 said:

My 4th gen Intel had already HT so yours should do to

The i5-9600k is listed as not supporting HT.

[Davee]

On 7/24/2023 at 4:03 AM, Nealius said:

With the 2.8 updates of the last couple of months, my system has been increasingly unable to deal with high terrain textures.

In attached mission, sitting in an F-15E at Nellis, with terrain textures low and textures medium, I get a solid 40fps looking towards Las Vegas. For some reason I get a dip in the 30s and some stutters when looking north/northeast, but still playable. 

I can confirm the framerate drop when looking northeast. Always been there for me over the last year. Look elsewhere, framerate goes back up.

 

 

 

[PLUTON]

On the other hand, the terrain textures on high do not lower my fps, but it is the textures
that I have to put on medium otherwise I get no more than 15 fps on high. only on SINAI? On SYRIA I get 45/50 fps.
Do you understand something about it?
Me no