Jump to content

How would you interpret those performance stats?


Recommended Posts

Posted (edited)

Hi guys,

 

how would you interpret the following performance stats?

The problem ist, cpu is at 49% and gpu is at 59%, but still frames are capped at 45fps and the latency is at ~13ms.

 

Vive Pro

Msi 2080ti Ventus

7700k @5ghz (hyper threading disabled)

32gb 3200 with XMP enabled

samsung SSD

 

supersampling is at 1.0.

 

nvideo control panel at performance mode.

steam vr beta with motion smoothing disabled. (enabled is better though)

 

Isnt that a little bit strange?

 

Here is a screenshot. At the left is the steam vr app, right next to it the taskmanager, and the vive pro mirror.

 

https://imgur.com/a/XNF6Olw

 

thx and have a safe landing...

 

Do you think if i would get it below 11ms latency, then it will push the 90fps and have the cpu and gpu under full load?

 

I think i will try to get the reprojection thing turned off and see what happens.

Edited by OG84

Favorite module: F16C 💥
Currently learning F15E 👨‍🏫
13900k - RTX 4090 - 64GB DDR5 - Varjo Aero - TM Warthog Hotas - Pedals

Posted (edited)

I would hazard the guess that the CPU@49% is a statistic reporting the combined cores/threads on the chip. Being that DCS is very reliant on a single thread to carry most of the workloadand and under utilises the rest of the cores on a modern CPU.

 

I’d wager that if you were to monitor the individual cores while running these tests, you would find that only one core is being routinely topped out and thus causing a CPU bottleneck which is unable to feed your GPU with what it needs to perform.

 

It’s a pretty widely known and accepted fact that this is the case with DCS in its current form - I’d imagine a large reason why the devs are on the long and arduous journey of coding in support for the Vulcan API, and we as the players (especially VR) are hotly anticipating its arrival. Alas, I feel that it may be later rather than sooner...but it will come I’m sure. I just hope the advancements and improvements will be worth the wait, and the monumental amount of work it’ll take for the ED devs.

Edited by Fubarbrickdust

9700k@5.2Ghz | GTX 1080ti | 32gb Ram@3200Mhz | 512gb M.2 NVME SSD

Oculus Rift S | VKB GF Pro Mk.II+MCG Pro (rotary wing) | BRD DS-Raven (fixed wing) | MFG Crosswind V2 | Jetseat+SSA/SSM | SimLab GT1 80/20 Rig | NLR Motion Platform V3 | Quad Bass Shaker Setup

DIY Control Panels: 'White Rhino' Throttle | UFC | MFBB Left | MFBB Right | MFBB Centre | WEP-TECH ACP | HYD-MECH LDG | SYS-ELEC | AN/ARC Radio

Posted (edited)

hi thx, yeah maybe.

 

I added a performance counter for all 46 DCS threads, and as it seems there are basically only 2 with a somewhat utilisation (render, sound?). But still around 50% the max.

I increased the graphics a bit and I'm now quite happy for the moment. The 2080ti delivers more stable 45fps and less stuttering and jagginess than the 1080ti though.

 

Here another screenshot: https://imgur.com/a/CzJLsmN

 

But you could be right, i found this thread which seems to have a legit explanation to this behavior :) https://forums.eagle.ru/showthread.php?t=198669

 

:pilotfly:

Edited by OG84

Favorite module: F16C 💥
Currently learning F15E 👨‍🏫
13900k - RTX 4090 - 64GB DDR5 - Varjo Aero - TM Warthog Hotas - Pedals

Posted

I'm seeing this 45fps cap too. I think it's something new happening in Steam VR? I just checked back in version 1.58 and 2.5 (Deferred shading off) and both also show a similar cap with occasional increases up to 90fps whereas they would happily run up at that fps constantly before.

 

Still cant believe how much better the image quality/ resolution was is in VR in those versions, but won't go there! :-(

Intel Core i3 8350K 4GHz, MSI RTX 2080 Super, AS Rock Z370 Pro4 Motherboard, Samsung SSD, 32G DDR4 RAM, Windows 10 PRO 64 Bit

 

Rift-S, Tripple Samsung 27" C27F Display, Hotas Warthog, Saitek Pro Flight rudder pedals, EDtracker, Track IR.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...