MoonlightVibe 6.3.2
Upstream reworked how Moonlight decides to decode and render on separate D3D11 devices. This
matters most if you have an AMD card.
The change
Separate devices are faster, but that path is prone to driver bugs. It used to be on by default and
switched off for known-bad cases — which left several broken configurations still taking it,
because they passed the feature-level test it relied on.
It is now an explicit allow-list: Intel, NVIDIA on WDDM 3.0+ drivers, NVIDIA on Windows-on-ARM, and
AMD Vega and later.
AMD
- Polaris (RX 400/500) and older — you should stop seeing corrupt output. Upstream tracks it as
moonlight-qt#2003, and the old
Radeon HD 5570 deadlocked on this path outright. These cards were still taking it before this
release. - Vega and newer — detected properly now. The detection reads a driver capability bitfield, and
an early version of this code compared it with==, which would have excluded any card reporting
more than one precision level. Fixed upstream before this release shipped.
NVIDIA
The gate is now the driver version, not the GPU generation — WDDM 3.0 or newer, roughly driver
471.11+. Older drivers rendered all-zero or green frames on this path. On a current driver, nothing
changes for you.
Diagnostics
The D3D11VA renderer now logs your GPU driver version — the first thing worth having if any of the
above goes wrong on your hardware.
Everything else
The rest of this range does not reach the Windows or macOS builds: a Linux VAAPI fallback change,
the CI move to tag-triggered releases, and merges.
Upgrading from 6.3.1 is a straight replacement. Nothing to reconfigure.
Rebased onto moonlight-stream/moonlight-qt upstream.
Built from 845e155507cedbab2c65428e9bb85c67da8a0fb3 (845e15).
Windows and macOS assets are attached to this same release.
Includes all MoonlightVibe patches: mic passthrough, per-seat stream settings, latency tuning, and configurable gamepad quit combo.