Skip to content

Build 23 Proto Driver (0.1.0.23)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@NorthernLights NorthernLights released this 03 Aug 21:21
v0.1.0-alpha.7
f45b809
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

LuminalVGD v0.1.0-alpha.7

Driver identity: 0.1.0.23 (Build 23)
Protocol: 0.9
Architecture: Windows x64
Status: Alpha / pre-release

Build 23 is a stability and containment release for LuminalVGD's direct-to-encoder shared-texture transport. It prevents optional capture-transport failures from repeatedly deleting and reassigning the Windows IddCx swapchain or removing the virtual monitor. The display now remains present even when direct transport must be disabled, allowing LuminalShine to recover or select its fallback path without destroying the active topology.

Highlights

Non-destructive transport failure containment

  • A D3D12 timeline-fence ring that cannot create or share its textures or fence now downgrades once, in place, to the legacy keyed-mutex ring.
  • The downgrade does not delete the IddCx swapchain, disconnect the monitor, or force another display modeset.
  • A remaining non-device publication failure opens a drain-only circuit for the current activation. LuminalVGD continues to acquire and finish IddCx frames while direct-ring publication remains disabled.
  • Exhausting the recovery budget now marks direct transport DEAD while keeping every virtual monitor arrived. Recovery may reduce streaming performance, but it no longer removes the active display topology.
  • Actual GPU device-loss results—DXGI_ERROR_DEVICE_REMOVED, DXGI_ERROR_DEVICE_HUNG, and DXGI_ERROR_DEVICE_RESET—remain eligible for reassignment/TDR recovery.

Protocol 0.9 transport reporting

  • RingHeader.reserved0 now reports the transport actually selected by the driver.
  • 0 represents keyed mutex and 1 represents a D3D12 timeline fence.
  • The existing ring layout is unchanged. Older hosts continue to interpret zero as the keyed-mutex transport.
  • LuminalShine can request the preferred transport and safely discover a driver-side downgrade without guessing from requested capabilities.

First-frame capture admission

  • A newly created display is not considered direct-capture-ready merely because Windows assigned a swapchain.
  • Capture admission now waits for the first frame to be copied and published into the shared ring.
  • The ring remains REBUILDING until that first successful publication, avoiding races where a client begins capture against an empty generation.
  • First-frame readiness and selected-transport state are exposed through the host/FFI interfaces for coordinated LuminalShine startup.

Swapchain device-creation recovery

  • D3D device creation and IddCxSwapChainSetDevice failures use bounded retry and recovery paths.
  • Retry classification distinguishes transient setup failures from terminal GPU device loss.
  • Frame acquisition remains non-blocking and every recovery wait has a deadline.
  • Cleanup paths retire unusable transport resources without holding IddCx callbacks or repeatedly operating on a dead swapchain.

Diagnostics

  • Added RingTransportStageFailed ETW events for texture creation, texture sharing, keyed-mutex acquisition, fence creation, and fence sharing.
  • Failure events include HRESULT, texture format, dimensions, ring generation, and session identity.
  • Added explicit first-frame publication and selected-transport telemetry.
  • vgd-probe diagnostics now provide clearer capture-readiness, transport, generation, and recovery information.

Compatibility

  • Requires Windows 10/11 x64 with Indirect Display Driver support.
  • LuminalShine 26.08.0-beta.2 or newer is required for control-device authentication and streaming integration.
  • Protocol 0.9 retains the existing ring layout and keeps the host compatibility floor at protocol 0.3.
  • The package contains the signed UMDF driver DLL, signed catalog, INF, installation and removal scripts, license, installation guide, and third-party notices.

Installation

  1. Download LuminalVGD-v0.1.0-alpha.7-x64.zip and SHA256SUMS.
  2. Verify the archive's SHA-256 digest against SHA256SUMS.
  3. Extract the archive.
  4. Run PowerShell as Administrator and execute install-driver.ps1 from the extracted directory.
  5. Confirm Device Manager lists Luminal Video Graphics Display under Display adapters.

The driver normally exposes no monitor until LuminalShine or another authorized controller creates one.

Signing and integrity

The driver DLL and catalog in this release are signed and RFC 3161 timestamped by NortheBridge Foundation. Signed binaries are distributed only as release assets and are not committed to the source repository.

SHA-256

afe890d0b0b94232b20eb0b6e3aac738e2f1ea73c66572541b9bb1b2e97d5afe  LuminalVGD-v0.1.0-alpha.7-x64.zip

Notes for alpha testers

This remains alpha software. Build 23 substantially limits the blast radius of direct-transport failures, but a system-wide GPU device removal or graphics-stack reset can still interrupt the current stream. Build 23 reports and contains that condition; complete stream reconstruction after device loss also depends on LuminalShine's host-side recovery behavior.

Please attach the LuminalShine runtime log plus LuminalVGD, IddCx, and DDisplay ETLs when reporting a capture or recovery failure.

Assets 4
Loading