[Help]: VDD Using Default HDR Luminance Metadata

[machetemike]

Which OS?

Win11 Pro

Which release?

24H2

Driver Version

11.30.4.434

Device Specifications

CPU: 9950X3D
GPU: 5090
RAM: 96GB DDR5 6000
MOBO: Asrock X870-E Nova Wifi
Monitor: LG 45GX950A-B

Running linux (using 9950x3d iGPU). Win 11 VM via virt-manager using gpu passthrough that is taking the display produced by VDD and piping it through Looking-Glass (https://github.com/mikigal/linux-nvidia-prime-vfio-passthrough)

What issue are you experiencing or what do you need help with?

I am attempting to get HDR properly calibrated and seem to be running into an issue.

When running through the Display Calibration the Minimum Luminance number comes to 0.26 while Maximum Luminance as well as Max Full Frame Luminance are both 360.

Enabling logging shows me [DEBUG] Setting default HDR metadata for monitor object for both displays it draws.

I have tried defining the metadata using the hdr_advanced block, defining it in monitor_profile.xml, and through importing my monitors edid w/ user_edid.bin

Here is my current vdd_settings.xml:

<?xml version="1.0" encoding="utf-8"?>
<vdd_settings>
  <monitors>
    <count>1</count>
  </monitors>
  <gpu>
    <friendlyname>default</friendlyname>
  </gpu>
  <global>
    <g_refresh_rate>165</g_refresh_rate>
  </global>
  <resolutions>
    <resolution>
      <width>5120</width>
      <height>2160</height>
      <refresh_rate>165</refresh_rate>
    </resolution>
  </resolutions>
  <options>
    <CustomEdid>true</CustomEdid>
    <PreventSpoof>false</PreventSpoof>
    <EdidCeaOverride>false</EdidCeaOverride>
    <HardwareCursor>true</HardwareCursor>
    <SDR10bit>true</SDR10bit>
    <HDRPlus>true</HDRPlus>
    <logging>true</logging>
    <debuglogging>true</debuglogging>
  </options>
  <colour>
    <ColourFormat>RGB</ColourFormat>
  </colour>
  <edid_integration>
    <enabled>true</enabled>
    <auto_configure_from_edid>true</auto_configure_from_edid>
    <source_priority>file</source_priority>
    <edid_profile_path>EDID/monitor_profile.xml</edid_profile_path>
    <override_manual_settings>false</override_manual_settings>
    <fallback_on_error>true</fallback_on_error>
  </edid_integration>
</vdd_settings>

My current monitor_profile.xml located in C:\VirtualDisplayDriver\EDID:

<?xml version="1.0" encoding="utf-8"?>
<IddCxMonitorConfig>
  <MonitorModes>
    <MonitorMode>
      <Width>5120</Width>
      <Height>2160</Height>
      <RefreshRate>165.000</RefreshRate>
      <RefreshRateMultiplier>1000</RefreshRateMultiplier>
      <NominalRefreshRate>165</NominalRefreshRate>
    </MonitorMode>
  </MonitorModes>
  <HDRCapabilities>
    <HDR10Supported>true</HDR10Supported>
    <DolbyVisionSupported>false</DolbyVisionSupported>
    <HDR10PlusSupported>false</HDR10PlusSupported>
    <MaxLuminance>1300.0</MaxLuminance>
    <MinLuminance>0.0001</MinLuminance>
    <MaxFullFrameLuminance>400.0</MaxFullFrameLuminance>
  </HDRCapabilities>
  <PreferredMode>
    <Width>5120</Width>
    <Height>2160</Height>
    <RefreshRate>165.000</RefreshRate>
  </PreferredMode>
</IddCxMonitorConfig>

Here is the most recent driver restart log entry:

[2026-05-02 14:58:08] [PIPE] Client Connected
[2026-05-02 14:58:08] [PIPE] Client Handling Enabled
[2026-05-02 14:58:08] [PIPE] PING

[2026-05-02 14:58:08] [PIPE] Heartbeat Ping
[2026-05-02 14:58:08] [PIPE] Client Connected
[2026-05-02 14:58:08] [PIPE] Client Handling Enabled
[2026-05-02 14:58:08] [PIPE] RELOAD_DRIVER

[2026-05-02 14:58:08] [COMPANION] Reloading the driver
[2026-05-02 14:58:08] [DEBUG] Unassigning swap chain for monitor object: FFFFFD9447A0D108
[2026-05-02 14:58:08] [DEBUG] Unassigning swap chain for monitor object: FFFFFD94479BB978
[2026-05-02 14:58:08] [INFO] Unasigning Swapchain. Processing will be stopped.
[2026-05-02 14:58:08] [INFO] Unasigning Swapchain. Processing will be stopped.
[2026-05-02 14:58:08] [ERROR] Failed to acquire buffer. Exiting loop. The swap-chain was likely abandoned (e.g. DXGI_ERROR_ACCESS_LOST) - HRESULT: -2005270490
[2026-05-02 14:58:08] [DEBUG] Terminate event signaled successfully.
[2026-05-02 14:58:08] [DEBUG] Core processing function RunCore() completed.
[2026-05-02 14:58:08] [DEBUG] Swap-chain object deleted.
[2026-05-02 14:58:08] [DEBUG] Multimedia thread characteristics reverted successfully.
[2026-05-02 14:58:08] [DEBUG] Multimedia thread characteristics reverted successfully.
[2026-05-02 14:58:08] [DEBUG] Thread terminated successfully.
[2026-05-02 14:58:08] [DEBUG] Thread terminated successfully.
[2026-05-02 14:58:08] [DEBUG] Swap chain unassigned successfully.
[2026-05-02 14:58:08] [DEBUG] Assigning swap chain:
  hSwapChain: FFFFFD944693F2A8
  RenderAdapterLuid: 35338-0
  hNextSurfaceAvailable: 00000000000009AC
[2026-05-02 14:58:08] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:08] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:08] [INFO] Adapter found: 000000B37BDFC050 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:08] [DEBUG] Swap chain unassigned successfully.
[2026-05-02 14:58:08] [DEBUG] Assigning swap chain:
  hSwapChain: FFFFFD9446941108
  RenderAdapterLuid: 35338-0
  hNextSurfaceAvailable: 0000000000000E38
[2026-05-02 14:58:08] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:08] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:08] [INFO] Adapter found: 000000B37C27C5F0 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:08] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:08] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:08] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:08] [INFO] Adapter found: 000000B37BDFC050 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:08] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:08] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:08] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:08] [INFO] Adapter found: 000000B37C27C5F0 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:09] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:09] [DEBUG] Creating a new swap-chain processing thread.
[2026-05-02 14:58:09] [DEBUG] Constructing SwapChainProcessor:
  SwapChain Handle: FFFFFD9446941108
  Device Pointer: 0000026BFFB97D30
  NewFrameEvent Handle: 0000000000000E38
[2026-05-02 14:58:09] [DEBUG] Terminate event created successfully.
[2026-05-02 14:58:09] [DEBUG] Swap-chain processing thread created and started successfully.
[2026-05-02 14:58:09] [DEBUG] RunThread started. Argument: 0000026BFFC02760
[2026-05-02 14:58:09] [DEBUG] Hardware cursor setup completed successfully.
[2026-05-02 14:58:09] [DEBUG] Run method started.
[2026-05-02 14:58:09] [DEBUG] Swap chain assigned successfully.
[2026-05-02 14:58:09] [DEBUG] Multimedia thread characteristics set successfully. AvTask: 13
[2026-05-02 14:58:09] [INFO] HDRPlus is enabled.
[2026-05-02 14:58:09] [INFO] SDR10bit is enabled.
[2026-05-02 14:58:09] [INFO] CustomEdid is enabled.
[2026-05-02 14:58:09] [INFO] HardwareCursor is enabled.
[2026-05-02 14:58:09] [INFO] PreventSpoof is disabled.
[2026-05-02 14:58:09] [INFO] EdidCeaOverride is disabled.
[2026-05-02 14:58:09] [INFO] Driver Starting
[2026-05-02 14:58:09] [INFO] VDD Path: C:\VirtualDisplayDriver
[2026-05-02 14:58:09] [INFO] IDDCX Version: 0x1b00
[2026-05-02 14:58:09] [DEBUG] Testing Debug Log
[2026-05-02 14:58:09] [PIPE] Starting Pipe
[2026-05-02 14:58:09] [PIPE] Pipe created
[2026-05-02 14:58:09] [DEBUG] Starting pipe with parameters: D:(A;;GA;;;WD)
[2026-05-02 14:58:09] [DEBUG] Initializing device:
  DeviceInit Pointer: 000000EDFE0FE870
[2026-05-02 14:58:09] [DEBUG] Configuring IDD_CX client:
  EvtIddCxAdapterInitFinished: Not Set
  EvtIddCxMonitorGetDefaultDescriptionModes: Not Set
  EvtIddCxMonitorAssignSwapChain: Not Set
  EvtIddCxMonitorUnassignSwapChain: Not Set
[2026-05-02 14:58:09] [DEBUG] Added: 5120x2160 @ 165/1Hz
[2026-05-02 14:58:09] [INFO] Using vdd_settings.xml
[2026-05-02 14:58:09] [INFO] Attempting to Load GPU from adapter.txt
[2026-05-02 14:58:09] [INFO] ASSIGNED GPU: NVIDIA GeForce RTX 5090 (LUID: 35338-0)
[2026-05-02 14:58:09] [DEBUG] Creating device with WdfDeviceCreate:
[2026-05-02 14:58:09] [DEBUG] Device context initialized and attached to WDF device.
[2026-05-02 14:58:09] [DEBUG] Entering D0 power state:
  Device Handle: FFFFFE0D16648168
  Previous State: 5
[2026-05-02 14:58:09] [DEBUG] Initializing adapter...
[2026-05-02 14:58:09] [INFO] Attempting to use user Edid
[2026-05-02 14:58:09] [INFO] Using custom edid
[2026-05-02 14:58:09] [DEBUG] Initializing adapter...
[2026-05-02 14:58:09] [DEBUG] FP16 processing capability detected.Adapter Caps Initialized:
  Max Monitors Supported: 1
  Gamma Support: 1
  Transmission Type: 3
  Friendly Name: 00007FFDE7FFDF30
  Manufacturer Name: 00007FFDE7FFDF68
  Model Name: 00007FFDE7FFDF80
  Firmware Version: 1
  Hardware Version: 1
[2026-05-02 14:58:09] [DEBUG] Adapter Initialization Status: 0
[2026-05-02 14:58:09] [DEBUG] Adapter handle stored successfully.
[2026-05-02 14:58:09] [DEBUG] InitAdapter called successfully.
[2026-05-02 14:58:09] [DEBUG] Initializing device:
  DeviceInit Pointer: 000000EDFE0FE870
[2026-05-02 14:58:09] [INFO] Applied Adapter configs.
[2026-05-02 14:58:09] [DEBUG] Added: 5120x2160 @ 165/1Hz
[2026-05-02 14:58:09] [DEBUG] Created container ID
[2026-05-02 14:58:09] [DEBUG] Monitor created successfully.
[2026-05-02 14:58:09] [DEBUG] Querying target info for adapter object: FFFFFE0D16657A88
[2026-05-02 14:58:09] [DEBUG] Target capabilities set to: 3
Dithering support set to: 8
[2026-05-02 14:58:09] [DEBUG] Parsing monitor description:
  MonitorModeBufferInputCount: 0
  pMonitorModes: Null
[2026-05-02 14:58:09] [INFO] Attempting to Load GPU from adapter.txt
[2026-05-02 14:58:09] [DEBUG] Monitor Modes:
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
[2026-05-02 14:58:09] [DEBUG] Creating device with WdfDeviceCreate:
[2026-05-02 14:58:09] [DEBUG] Monitor Modes:
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
[2026-05-02 14:58:09] [DEBUG] Device context initialized and attached to WDF device.
[2026-05-02 14:58:09] [DEBUG] Querying target modes:
  MonitorObject Handle: FFFFFE0D16641178
  TargetModeBufferInputCount: 0
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] IDDCX_TARGET_MODE2 configured with Size: 80 and BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Entering D0 power state:
  Device Handle: FFFFFE0D1663DF58
  Previous State: 5
[2026-05-02 14:58:09] [DEBUG] IDDCX_TARGET_MODE2 configured with Size: 80 and BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [INFO] Attempting to use user Edid
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [INFO] Using custom edid
[2026-05-02 14:58:09] [DEBUG] Initializing adapter...
[2026-05-02 14:58:09] [WARNING] Input buffer is too small for target modes.
[2026-05-02 14:58:09] [DEBUG] Querying target modes:
  MonitorObject Handle: FFFFFE0D16641178
  TargetModeBufferInputCount: 2
[2026-05-02 14:58:09] [DEBUG] Adapter Initialization Status: 0
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Adapter handle stored successfully.
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] IDDCX_TARGET_MODE2 configured with Size: 80 and BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [DEBUG] Creating target modes:
  TargetModeIndex: 0
    Width: 5120
    Height: 2160
    RefreshRate: 165
  TargetModeIndex: 1
    Width: 5120
    Height: 2160
    RefreshRate: 165
[2026-05-02 14:58:09] [DEBUG] Output target modes count: 2
[2026-05-02 14:58:09] [DEBUG] Target modes copied to output buffer:
  TargetModeIndex: 0
    Size: 80
    BitsPerComponent.Rgb: 12
  TargetModeIndex: 1
    Size: 80
    BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Setting default HDR metadata for monitor object: FFFFFE0D16641178
[2026-05-02 14:58:09] [DEBUG] Default HDR metadata set successfully.
[2026-05-02 14:58:09] [INFO] Applied Adapter configs.
[2026-05-02 14:58:09] [INFO] Creating Monitor: 1
[2026-05-02 14:58:09] [DEBUG] Adapter initialization finished successfully.
[2026-05-02 14:58:09] [DEBUG] Created container ID
[2026-05-02 14:58:09] [DEBUG] Monitor created successfully.
[2026-05-02 14:58:09] [DEBUG] Querying target info for adapter object: FFFFFE0D1663C1E8
[2026-05-02 14:58:09] [DEBUG] Target capabilities set to: 3
Dithering support set to: 8
[2026-05-02 14:58:09] [DEBUG] Parsing monitor description:
  MonitorModeBufferInputCount: 0
  pMonitorModes: Null
[2026-05-02 14:58:09] [DEBUG] Monitor Modes:
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
[2026-05-02 14:58:09] [DEBUG] Parsing monitor description:
  MonitorModeBufferInputCount: 2
  pMonitorModes: Valid
[2026-05-02 14:58:09] [DEBUG] Monitor Modes:
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
  Mode - Width: 5120, Height: 2160, RefreshRate: 165
[2026-05-02 14:58:09] [DEBUG] Writing monitor modes to output buffer:
  ModeIndex: 0
    Size: 72
    Origin: 1
    BitsPerComponent.Rgb: 12
  ModeIndex: 1
    Size: 72
    Origin: 1
    BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Querying target modes:
  MonitorObject Handle: FFFFFE0D1665A8B8
  TargetModeBufferInputCount: 0
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] IDDCX_TARGET_MODE2 configured with Size: 80 and BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] IDDCX_TARGET_MODE2 configured with Size: 80 and BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [DEBUG] Creating target modes:
  TargetModeIndex: 0
    Width: 5120
    Height: 2160
    RefreshRate: 165
  TargetModeIndex: 1
    Width: 5120
    Height: 2160
    RefreshRate: 165
[2026-05-02 14:58:09] [DEBUG] Output target modes count: 2
[2026-05-02 14:58:09] [WARNING] Input buffer is too small for target modes.
[2026-05-02 14:58:09] [DEBUG] Querying target modes:
  MonitorObject Handle: FFFFFE0D1665A8B8
  TargetModeBufferInputCount: 2
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] IDDCX_TARGET_MODE2 configured with Size: 80 and BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [DEBUG] Creating IDDCX_TARGET_MODE2 with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] IDDCX_TARGET_MODE2 configured with Size: 80 and BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Creating target mode with Width: 5120, Height: 2160, VSyncNum: 165, VSyncDen: 1
[2026-05-02 14:58:09] [DEBUG] Target mode configured with:
  Total Size: (5120, 2160)
  Active Size: (5120, 2160)
  vSync Frequency: 165/1
  hSync Frequency: 356400/1
  Pixel Rate: 1824768000
  Scan Line Ordering: 1
[2026-05-02 14:58:09] [DEBUG] Creating target modes:
  TargetModeIndex: 0
    Width: 5120
    Height: 2160
    RefreshRate: 165
  TargetModeIndex: 1
    Width: 5120
    Height: 2160
    RefreshRate: 165
[2026-05-02 14:58:09] [DEBUG] Output target modes count: 2
[2026-05-02 14:58:09] [DEBUG] Target modes copied to output buffer:
  TargetModeIndex: 0
    Size: 80
    BitsPerComponent.Rgb: 12
  TargetModeIndex: 1
    Size: 80
    BitsPerComponent.Rgb: 12
[2026-05-02 14:58:09] [DEBUG] Setting default HDR metadata for monitor object: FFFFFE0D1665A8B8
[2026-05-02 14:58:09] [DEBUG] Default HDR metadata set successfully.
[2026-05-02 14:58:09] [DEBUG] Monitor arrival successfully reported.
[2026-05-02 14:58:09] [DEBUG] Adapter initialization finished successfully.
[2026-05-02 14:58:09] [INFO] Finished Setting up adapter.
[2026-05-02 14:58:10] [DEBUG] Assigning swap chain:
  hSwapChain: FFFFFE0D166366B8
  RenderAdapterLuid: 35338-0
  hNextSurfaceAvailable: 0000000000000590
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFDFFC590 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [DEBUG] Assigning swap chain:
  hSwapChain: FFFFFE0D16631DB8
  RenderAdapterLuid: 35338-0
  hNextSurfaceAvailable: 00000000000005FC
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFE4FC170 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFDFFC590 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFE4FC170 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [PIPE] Client Connected
[2026-05-02 14:58:10] [PIPE] Client Handling Enabled
[2026-05-02 14:58:10] [PIPE] PING

[2026-05-02 14:58:10] [PIPE] Heartbeat Ping
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Creating a new swap-chain processing thread.
[2026-05-02 14:58:10] [DEBUG] Constructing SwapChainProcessor:
  SwapChain Handle: FFFFFE0D16631DB8
  Device Pointer: 000001F2E99DD5E0
  NewFrameEvent Handle: 00000000000005FC
[2026-05-02 14:58:10] [DEBUG] Terminate event created successfully.
[2026-05-02 14:58:10] [DEBUG] Swap-chain processing thread created and started successfully.
[2026-05-02 14:58:10] [DEBUG] Hardware cursor setup completed successfully.
[2026-05-02 14:58:10] [DEBUG] Multimedia thread characteristics set successfully. AvTask: 16
[2026-05-02 14:58:10] [DEBUG] Swap chain assigned successfully.
[2026-05-02 14:58:10] [ERROR] Failed to set device to swap chain. HRESULT: -2005270490
[2026-05-02 14:58:10] [DEBUG] Unassigning swap chain for monitor object: FFFFFE0D1665A8B8
[2026-05-02 14:58:10] [DEBUG] Core processing function RunCore() completed.
[2026-05-02 14:58:10] [INFO] Unasigning Swapchain. Processing will be stopped.
[2026-05-02 14:58:10] [DEBUG] Swap-chain object deleted.
[2026-05-02 14:58:10] [DEBUG] Destructing SwapChainProcessor:
[2026-05-02 14:58:10] [DEBUG] Multimedia thread characteristics reverted successfully.
[2026-05-02 14:58:10] [DEBUG] Terminate event signaled successfully.
[2026-05-02 14:58:10] [DEBUG] Thread terminated successfully.
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Creating a new swap-chain processing thread.
[2026-05-02 14:58:10] [DEBUG] Constructing SwapChainProcessor:
  SwapChain Handle: FFFFFE0D166366B8
  Device Pointer: 000001F2E99561A0
  NewFrameEvent Handle: 0000000000000590
[2026-05-02 14:58:10] [DEBUG] Terminate event created successfully.
[2026-05-02 14:58:10] [DEBUG] Swap-chain processing thread created and started successfully.
[2026-05-02 14:58:10] [DEBUG] Hardware cursor setup completed successfully.
[2026-05-02 14:58:10] [DEBUG] Swap chain assigned successfully.
[2026-05-02 14:58:10] [DEBUG] RunThread started. Argument: 000001F2F10B9830
[2026-05-02 14:58:10] [DEBUG] Unassigning swap chain for monitor object: FFFFFE0D16641178
[2026-05-02 14:58:10] [INFO] Unasigning Swapchain. Processing will be stopped.
[2026-05-02 14:58:10] [DEBUG] Destructing SwapChainProcessor:
[2026-05-02 14:58:10] [ERROR] Failed to set device to swap chain. HRESULT: -2005270490
[2026-05-02 14:58:10] [DEBUG] Terminate event signaled successfully.
[2026-05-02 14:58:10] [DEBUG] Swap-chain object deleted.
[2026-05-02 14:58:10] [DEBUG] Multimedia thread characteristics reverted successfully.
[2026-05-02 14:58:10] [DEBUG] Thread terminated successfully.
[2026-05-02 14:58:10] [DEBUG] Swap chain unassigned successfully.
[2026-05-02 14:58:10] [DEBUG] Assigning swap chain:
  hSwapChain: FFFFFE0D158ED548
  RenderAdapterLuid: 35338-0
  hNextSurfaceAvailable: 0000000000000768
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFE4FC170 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [DEBUG] Swap chain unassigned successfully.
[2026-05-02 14:58:10] [DEBUG] Assigning swap chain:
  hSwapChain: FFFFFE0D158EC468
  RenderAdapterLuid: 35338-0
  hNextSurfaceAvailable: 0000000000000920
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFDFFC590 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFE4FC170 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Initializing Direct3DDevice...
[2026-05-02 14:58:10] [DEBUG] DXGI factory created successfully.
[2026-05-02 14:58:10] [INFO] Adapter found: 000000EDFDFFC590 (Vendor ID: 4318, Device ID: 11141)
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Creating a new swap-chain processing thread.
[2026-05-02 14:58:10] [DEBUG] Constructing SwapChainProcessor:
  SwapChain Handle: FFFFFE0D158ED548
  Device Pointer: 000001F2EAAA34E0
  NewFrameEvent Handle: 0000000000000768
[2026-05-02 14:58:10] [DEBUG] Terminate event created successfully.
[2026-05-02 14:58:10] [DEBUG] Swap-chain processing thread created and started successfully.
[2026-05-02 14:58:10] [DEBUG] RunThread started. Argument: 000001F2F0EF18D0
[2026-05-02 14:58:10] [DEBUG] Hardware cursor setup completed successfully.
[2026-05-02 14:58:10] [DEBUG] Run method started.
[2026-05-02 14:58:10] [DEBUG] Multimedia thread characteristics set successfully. AvTask: 18
[2026-05-02 14:58:10] [INFO] Direct3D device created successfully. Feature Level: 45312
[2026-05-02 14:58:10] [DEBUG] Creating a new swap-chain processing thread.
[2026-05-02 14:58:10] [DEBUG] Constructing SwapChainProcessor:
  SwapChain Handle: FFFFFE0D158EC468
  Device Pointer: 000001F2EAAA36E0
  NewFrameEvent Handle: 0000000000000920
[2026-05-02 14:58:10] [DEBUG] Terminate event created successfully.
[2026-05-02 14:58:10] [DEBUG] Swap-chain processing thread created and started successfully.
[2026-05-02 14:58:10] [DEBUG] RunThread started. Argument: 000001F2F0FDAB10
[2026-05-02 14:58:10] [DEBUG] Hardware cursor setup completed successfully.
[2026-05-02 14:58:10] [DEBUG] Run method started.
[2026-05-02 14:58:10] [DEBUG] Multimedia thread characteristics set successfully. AvTask: 19

Troubleshooting steps taken

No response

Expected outcome

Proper Luminance range during HDR configuration

Additional information

No response

Contact Details

No response

[machetemike]

Following #80 it appears my luminance information is being properly written at driver level

However its still not going under 0.26 or over 360 before going completely blank (black, or white) in the HDR calibration steps.

Using AI to assist and it wants me to ask "Does EVT_IDD_CX_ADAPTER_QUERY_TARGET_INFO in VDD's driver code return hardcoded luminance values, and does hdr_advanced actually configure those values or is it unimplemented?"

It wants me to ask this because of https://learn.microsoft.com/en-us/windows-hardware/drivers/display/iddcx1.10-updates :

This is very revealing. From the Microsoft IddCx 1.10 docs:
"When the driver provides a monitor descriptor containing HDR metadata, the OS calls EVT_IDD_CX_MONITOR_SET_DEFAULT_HDR_METADATA to give the default HDR metadata to the driver."
This is critical. EVT_IDD_CX_MONITOR_SET_DEFAULT_HDR_METADATA is an OS callback TO the driver — meaning the OS is telling the driver what HDR metadata to use based on what it has parsed from the EDID. The driver then stores this and uses it when sending HDR info frames.
So the flow is:

Driver provides EDID to OS via IDDCX_MONITOR_DESCRIPTION
OS parses EDID, determines HDR metadata
OS calls EVT_IDD_CX_MONITOR_SET_DEFAULT_HDR_METADATA to send that parsed metadata BACK to the driver
Driver stores and uses it for per-frame HDR metadata

The log line Setting default HDR metadata for monitor object is the driver's log of THIS callback being called — the OS calling the driver with metadata derived from the EDID or other sources.
This means:

The Setting default HDR metadata log line is actually the OS GIVING metadata to the driver — not the driver applying a hardcoded default
The metadata values being set come from what the OS determined from the EDID
If the OS is giving 360 nits, it's because that's what the OS determined — not a driver hardcode

But wait — the log just says "Setting default HDR metadata set successfully" without printing the values. So we don't know if the OS is providing 1317 nits or 360 nits.
Also critically: "HDR metadata isn't made available to remote drivers because any HDR10 metadata should come from the display subsystem on the client."
This is the key insight. VDD in a VFIO/Looking Glass context — is it being treated as a REMOTE driver? If Windows is treating VDD as a remote IddCx driver, HDR metadata wouldn't be provided at all, and the driver would use whatever default it has hardcoded.
The IddCx version in the log is 0x1b00. Let me check what version this is. …


Found something critical in the Microsoft IddCx 1.10 docs that reframes everything we've been looking at.
EVT_IDD_CX_MONITOR_SET_DEFAULT_HDR_METADATA — which is exactly what the log line Setting default HDR metadata corresponds to — is an OS callback to the driver. Meaning the OS is telling the driver what HDR metadata to use, not the driver applying its own hardcoded default. The values the OS sends come from what it determined from the EDID and from a separate DDI called EVT_IDD_CX_ADAPTER_QUERY_TARGET_INFO.
That second DDI is the key quote:

"If a driver wishes to enable HDR for an adapter, it must provide additional information about each target connector via its EVT_IDD_CX_ADAPTER_QUERY_TARGET_INFO function."

This is where the driver reports HDR target capabilities — including luminance — separately from the EDID. If VDD's implementation of this callback has hardcoded 360 nit values, the OS will use those over the EDID when calling SetDefaultHDRMetadata, regardless of what the EDID says.
This is almost certainly the root cause. The hdr_advanced XML block was presumably designed to configure these QUERY_TARGET_INFO values, but isn't being parsed and applied yet.
This is now a very precise question for your GitHub issue: does EVT_IDD_CX_ADAPTER_QUERY_TARGET_INFO in VDD's driver code return hardcoded luminance values, and does hdr_advanced actually configure those values or is it unimplemented?