LuminalVGD v0.1.0-alpha.4 — Build 14
Driver build 14 (DriverVer 0.1.0.14). Changes since v0.1.0-alpha.3 (build 13):
Added
- TDR duck-out. When a frame worker's D3D device reports removal (a
GPU reset), the driver departs every virtual monitor so a failing
Windows TDR recovery can never wait on the indirect display path —
the working hypothesis for the machine-wide display-stack wedges
observed on 2026-05-17, 07-26 and 07-27, where a virtual display was
the exclusive active display each time. Monitor identity and the
frame ring are parked; a recovery poller probes the render adapter
(the specific LUID, never the default adapter) on deadline-bounded
throwaway threads, and on recovery the monitors re-arrive with the
same container GUID and connector so Windows reattaches the
remembered topology and ring sequences continue. Bounded throughout:
one duck in flight, at most 3 cycles per incident (a 10-minute
stability window starts a fresh budget), a 10-minute recovery budget,
and every give-up path cleans up deterministically. - New ETW events for the above:
TdrDeviceRemoved,TdrDuckStart,
TdrDuckDeparted,TdrRecoveryDetected,TdrReplugged,
TdrDuckAbandoned,TdrRecoveryProbeHung,
TdrDuckTornDownMidFlight.
Fixed
- Watchdog contract. The handshake advertised "watchdog 3 s" while
the enforced lease floor was always 10 s (orphaned monitors actually
lived ~11 s). The advertised default is now 10 — advertised and
enforced agree, locked by a regression test. No behavioral change to
lease enforcement.
Pairing
- Works with LuminalShine 26.08.0-beta.2 or later; pairs with
26.08.0-beta.6, which adds the host-side topology lifeboat
(a physical display is activated alongside the virtual one the
moment a GPU hang is detected). Protocol unchanged (proto 0.3,
handshake build 14).