Download Latest Version VectorXR-0.20.2-windows-x64-setup.exe (17.2 MB)
Home / v0.20.1
Name Modified Size InfoDownloads / Week
Parent folder
VectorXR-0.20.1-windows-x64-setup.exe 2026-11-10 5.2 MB
VectorXR-0.20.1-windows-x64-setup.exe.sha256 2026-11-10 105 Bytes
README.md 2026-11-10 4.1 kB
VectorXR v0.20.1 source code.tar.gz 2026-11-10 6.5 MB
VectorXR v0.20.1 source code.zip 2026-11-10 6.9 MB
Totals: 5 Items   18.6 MB 0

VectorXR 0.20.1 - Depth for Direct3D 11 Games, PimaxXR Fixes, and Duplicate Pivot Profiles

A fix release for 0.20.0. Frame Generation can now use depth from Direct3D 11 games, including UEVR titles. Frame Generation no longer stalls games on PimaxXR. Turbo's Auto mode gives async pacing a fairer trial, and eye-tracked foveation is placed better on Pimax. VectorXR works beside OpenXR Toolkit and Quad-Views-Foveated in more setups, and custom Pivot profiles can now be duplicated.

Frame Generation

  • Depth for Direct3D 11 games. Frame Generation can now use the depth that Direct3D 11 games provide, including UEVR titles, for steadier generated frames.
  • Use game depth option. If a game stutters, hangs or shows depth artifacts with Frame Generation, turn off Use game depth in the profile's advanced settings and restart the game. Frame Generation then works without depth.
  • No more stalls on PimaxXR. With Frame Generation engaged, PimaxXR could hold up the game's own rendering, and the game's frame rate dropped sharply. Frame Generation now works around it.
  • Smoother output on PimaxXR 0.4.4 and earlier, which could skip a refresh when no new frame was ready.
  • Frame Generation stays off when OpenXR Toolkit is below VectorXR, because Toolkit can't handle the extra frames there. The OSD and the OpenXR Layers page now say when this applies; move OpenXR Toolkit above VectorXR there to use both.
  • OpenXR Toolkit's prediction dampening is respected instead of being undone by Frame Generation.
  • No rejected frames from misplaced depth. Some games, such as UEVR titles, can describe depth that doesn't fit its image, and PimaxXR and Virtual Desktop then reject the whole frame. VectorXR now leaves that depth out.

Turbo

  • Auto gives async pacing a fair trial. A stutter right as a game left its loading screen could make Auto settle on sequenced pacing for good. Auto now rides out early stutters. It also tries async again after a quick failure, a VectorXR or runtime update, or 30 days.
  • More accurate frame timing with sequenced pacing in games that prepare frames ahead, such as DCS.
  • Turbo stands aside when OpenXR Toolkit's Turbo runs above VectorXR, instead of both pacing frames.

Quadviews and eye tracking

  • Better-placed focus areas on Pimax. On headsets with angled displays, VectorXR's emulated quad views placed each eye's sharp area off to the side. Both eyes now line up on where you're looking.
  • A frozen eye tracker no longer pins the focus area. If the tracker stops updating, the focus area follows your head until the tracker recovers.
  • Eye-tracked foveation is no longer switched off in PimaxXR's native quad views.
  • DCS's focus views stay aligned on PimaxXR's native quad views.

Pivot

  • Duplicate custom profiles. A new Duplicate button next to Remove copies a profile with all its settings and bindings, places the copy just below the original, and scrolls to it. Change the copy's applications or bindings so the two profiles don't overlap.
  • Pivot stays centred after a recenter on Pimax. Recentering in Pimax Play during a session could leave Pivot turning around your old head position.
  • A restarted VR session starts Pivot fresh, instead of picking up the previous session's origin.

Compatibility

  • Games start with OpenXR Toolkit or Quad-Views-Foveated on VIVE runtimes.
  • Stability fixes for PimaxXR around starting VR again in the same game, and around head tracking.

Known issues

  • In helicopters, Interpolate can show artifacts around the rotors and in the sky behind them.
  • On Varjo headsets with Quadviews, focus sharpening is off in DCS while Frame Generation runs.
  • On Varjo headsets with Quadviews, overlays such as OpenKneeboard are drawn at the Peripheral resolution outside the focus area, and can look jagged there at low Peripheral settings. Raise Peripheral (1.0 matches Varjo's default) if overlays matter more than the performance gain.
  • Turbo prevents runtime reprojection such as SteamVR Motion Smoothing from working. Use one or the other.
Source: README.md, updated 2026-11-10