Skip to content

v1.6.0 — Frame reconnect and tuned HEVC

Choose a tag to compare

View all tags
@elliotttate elliotttate released this 14 Oct 14:16
v1.6.0
c1e173e

SteamFrame Advanced Options v1.6.0 adds reconnect recovery and our current tuned HEVC preset.

  • Reconnect Frame: one SteamVR restart, restoration of prior HEVC tuning requests, and verification of fresh encoded video. Recovery reports when the headset has not returned instead of repeatedly restarting.
  • Updated help: unplug/replug guidance for a stalled dedicated dongle, including use of the same USB port or hub; clearer explanations of helper-version mismatches and encoder policies waiting for reconnect.
  • All four built-in presets: Tuned HEVC, Smooth HEVC, High quality HEVC, and Full-resolution HEVC — Experimental. Every preset remains editable.
  • Tuned HEVC: 400 Mbps target, 90 Hz, 10-bit, 1664-pixel width, quarter-resolution multipass, synchronous sending, and center/outside-gaze offsets of -20/-12.
  • Encoder and diagnostics fixes: maximum-QP changes require encoder reinitialization; accepted rate-control status is clearer; compositor handoff and recovery-trace timing labels are more accurate.
  • Source tools: latest-build launcher and a matching-helper diagnostic build workflow to keep historical research helpers out of normal recovery.

Download and extract the complete SteamFrame-Advanced-Options-win-x64.zip, then run SteamLinkVRSettings.exe. The ZIP includes the .NET and Windows App SDK runtimes, codec companion, presets, and updated guides. Personal settings are kept separately.

If SteamVR has an older helper loaded, use Reconnect Frame or Restart SteamVR and resume once. This briefly disconnects the headset and may close the running game.

Bitrate values are targets, not guaranteed output. Sustained smooth 400 Mbps gameplay is not established. The full-resolution multipass preset remains experimental.

Validation: 113 managed tests, six native test executables, 25 compositor-timing assertions, ten launcher checks, and the managed probe harness passed. The optional original-driver patcher fixture was not configured and that test was skipped. Reconnect was exercised on the paired Frame; the helper notice stayed cleared across two app reopenings.

Assets 4
Loading