Jump to content

Recommended Posts

Posted (edited)

After some playing around and tests, I have established a baseline so that it can be used for comparisons in the future.

The benchmark baseline is not used to tune settings.

That the baseline serves as the basis when there is one thing changed,  let's say, the next OB version, I can check how the performance differs, if any, when everything else remains the same.

This is a somewhat not-so-scientific A/B test. Because there are a number of factors that are beyond control: Windows changes, NVIDIA drivers changes, VR drivers changes, and equipment getting old, etc.

The scenario or the track file is designed so that there are reasonable amount of actions happening around at the same time, because this is DCS World, not MSFS, not just simply flying. The jet plane used because it is faster and is more demanding in terms of frame rate and frame time (which measures the smoothness) than helicopter. And the graphics settings in DCS attempt to push it towards the limit.

At the end of the day,  I am sick and tired of people using one single screenshot and claims, without any setup details and context, that certain thing(s) give great performance, and if yours does not work like that, the fault is yours.Turns out, performance is something a very dynamic and complicated thing and it is not what some people think.

Hope this clarifies a few things. And the details of the benchmark are in the video.

Mission and track files are enclosed.

 

Benchmark - FA-18C - Flyover Beirut 1.7.miz benchmark - fa18c - flyover beruit 1.7.trk

Edited by VR Flight Guy in PJ Pants
  • Like 1
  • Thanks 1

I Fly, Therefore I Am.

One cannot go around not saying "Thank you" every time these days, can't you?

YouTube: https://www.youtube.com/channel/UCc9BDi-STaqgWsjNiHbW0fA

Posted

Hi,

 

thank you for your work. 🙂

Where do I have to copy the trk-file to? And where do I start it from?

  • Like 1

CPU: AMD Ryzen 9800X3D, System-RAM: 64 GB DDR5, GPU: nVidia 5090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal/Super, OS: Windows 11 Pro, HD: 2*2TB and 1*4 TB (DCS) Samsung M.2 SSD

HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts

HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick

Rudder: WinWing Orion Metal

Posted
20 hours ago, VR Flight Guy in PJ Pants said:

Saved game, your DCS folder and then Tracks. For my setup, it would be E:\Saved Games\DCS.openbeta\Tracks

As usual, your insights and comments are welcome. I am always looking for ways to make it better.

 

Thank you. I will give it a shot. 😉

CPU: AMD Ryzen 9800X3D, System-RAM: 64 GB DDR5, GPU: nVidia 5090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal/Super, OS: Windows 11 Pro, HD: 2*2TB and 1*4 TB (DCS) Samsung M.2 SSD

HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts

HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick

Rudder: WinWing Orion Metal

Posted
1 hour ago, VR Flight Guy in PJ Pants said:

Quickie: how does OpenXR Turbo Mode perform?

I get really bad stuttering when I enable turbo mode. I can control this to a degree by limiting the FPS but if the frame rate drops below the target rate, I get huge latency spikes. 

  • Like 1

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

  • 3 weeks later...
  • 3 months later...
  • 2 months later...
  • 5 weeks later...
  • 4 months later...
  • 2 months later...
Posted (edited)

(VR) Benchmark results for 2.9.8.1107:

Overall back to 2.9.1 level, in terms of average FPS. BUT! After the loading shot up (gone through carpet bombing in the city, roughly between 80 sec and 105 sec of the runtime), the recovery was still rubbish, slightly better than the last one 2.9.7.59263 but still nowhere near the Baseline, both in terms of FPS and frame times. However, it is a delight to see the portion of time between frame times  < 8ms, which I would consider to be "smooth", keeps on growing, all the way up from the Baseline.

For the details of how the Benchmark is conducted, please visit the videos on the above.

N.B. Win11 Home 23H2 build 22635.4225. NVIDIA driver version 561.09

image.png

image.png

image.png

image.png

Edited by VR Flight Guy in PJ Pants
  • Thanks 2

I Fly, Therefore I Am.

One cannot go around not saying "Thank you" every time these days, can't you?

YouTube: https://www.youtube.com/channel/UCc9BDi-STaqgWsjNiHbW0fA

  • 3 months later...
  • Recently Browsing   0 members

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