Jump to content

VR Flight Guy in PJ Pants

Members
  • Posts

    2695
  • Joined

  • Last visited

Posts posted by VR Flight Guy in PJ Pants

  1. 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

    • Like 1
    • Thanks 1
  2. Echoing above, this is mine.

    Make a "baseline" for comparison. I make a track, run it through.

    For testing, change one setting/version at a time, run like an A/B test.

    Example:

     

×
×
  • Create New...