Please leave a comment on this community post if it is impacting you, to let Valve know this is an important issue.

  • javasux@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    20
    ·
    4 months ago

    VR has much more stringent latency requirements than normal gaming, because moving your head needs to be in perfect sync with the world “staying still”. The manual calibration needed for this is around 8ms, which is compensating for the render/presentation time of a single frame at 120fps.

    It sounds like a nitpick, but I can tell you from experience that it makes a very significant difference.

    • Lojcs@lemm.ee
      link
      fedilink
      arrow-up
      1
      arrow-down
      5
      ·
      edit-2
      4 months ago

      If you can just add a 7ms delay without noticing it as the solution suggests, latency doesn’t sound that stringent. What the problem sounds to me like is that the headset doesn’t support vrr so frames have to wait a whole frame time if they miss their window, and the system doesn’t realise that’s happening. Which wouldn’t be a problem if this was managed by the driver instead