VR space warp: render at half rate when needed and reproject every other frame (depth + motion vectors), auto-engaged, can be disabled #1594

Open
opened 2026-11-17 13:06:21 +00:00 by sky_line · 0 comments
Owner

At half rate, SteamVR on Linux only reprojects for rotation: no motion smoothing, so the eyes disagree on head roll and translation, which is uncomfortable. DLSS-G and FSR frame generation interpolate (holding a real frame back adds latency) and are not stereo-aware, so they are wrong for VR.

Proposal: app-side space warp (extrapolation)

  • When the GPU can't hold the headset rate, render real frames at half rate and synthesise every other frame ourselves:
    • reproject the newest real frame to the newest predicted head pose (positional, using depth), per eye;
    • carry moving content forward with our motion vectors;
    • fill disocclusions (edge-stretch, or the previous frame's history).
  • Submit at the full rate (120 Hz on an Index) with the real per-frame pose, so the runtime adds only its own late rotation correction.
  • Engagement is automatic (owner decision): on when the frame time would miss the headset rate, with hysteresis (no flapping), off when there's headroom. A setting turns it off entirely.
  • No preset locking: users pick their own settings (GI, shadows); space warp absorbs the cost.
  • UI, wall and hands: draw them at the full rate, or warp them correctly, so the laser and UI never judder.
  • No cost outside VR or when it is off.

Done when

  • With heavy settings at a real ~60 Hz, the headset shows a stable 120 Hz.
  • Head translation and roll stay comfortable (both eyes consistent).
  • Moving avatars carry forward without tearing.
  • Toggling it off returns today's behaviour.

Owner rule for heavy settings: 60 real is acceptable for now; 120 real stays the long-term goal.

Part of #1072.

At half rate, SteamVR on Linux only reprojects for rotation: no motion smoothing, so the eyes disagree on head roll and translation, which is uncomfortable. DLSS-G and FSR frame generation interpolate (holding a real frame back adds latency) and are not stereo-aware, so they are wrong for VR. ## Proposal: app-side space warp (extrapolation) - When the GPU can't hold the headset rate, render real frames at half rate and synthesise every other frame ourselves: - reproject the newest real frame to the newest predicted head pose (positional, using depth), per eye; - carry moving content forward with our motion vectors; - fill disocclusions (edge-stretch, or the previous frame's history). - Submit at the full rate (120 Hz on an Index) with the real per-frame pose, so the runtime adds only its own late rotation correction. - **Engagement is automatic** (owner decision): on when the frame time would miss the headset rate, with hysteresis (no flapping), off when there's headroom. A setting turns it off entirely. - No preset locking: users pick their own settings (GI, shadows); space warp absorbs the cost. - UI, wall and hands: draw them at the full rate, or warp them correctly, so the laser and UI never judder. - No cost outside VR or when it is off. ## Done when - With heavy settings at a real ~60 Hz, the headset shows a stable 120 Hz. - Head translation and roll stay comfortable (both eyes consistent). - Moving avatars carry forward without tearing. - Toggling it off returns today's behaviour. Owner rule for heavy settings: 60 real is acceptable for now; 120 real stays the long-term goal. Part of #1072.
sky_line added this to the Slipstream project 2026-11-17 13:06:21 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#1594
No description provided.