Qt Design Studio / Qt Quick 3D: “Device loss detected in Present()” when using lightProbe Texture (HDR/JPG/ktx2) on AMD GPU
-
Hi everyone,
I’m experiencing a reproducible rendering crash in Qt Design Studio 4.8.1 (runtime based on Qt 6.9.2 MSVC 2022) when trying to use lightProbe inside an ExtendedSceneEnvironment in Qt Quick 3D.
The scene works perfectly as long as lightProbe is not set.
However, once I assign any texture – HDR, JPG or even KTX2 – the QML Puppet crashes with:
D3D11: Removing Device.
Warning: Device loss detected in Present()
Warning: Graphics device lost, cleaning up scenegraph and releasing RHIEven simple JPEGs immediately trigger device loss.
KTX2 textures fail with:
Warning: Failed to load image: <path_to_ktx2>
System information
Product: Qt Design Studio 4.8.1
Based on: Qt 6.9.2 (MSVC 2022, x86_64)
Built on: Nov 21 2025 15:48:14
From revision: 9129b18a0a
GPU: AMD Radeon (WDDM 3.1, D3D Feature Level 12_1)
Direct3D 11 acceleration works fine in all applications and games
No GPU driver issues (dxdiag reports no problems)
What I found so far:
The crash happens only when lightProbe is enabled.
Removing the lightProbe completely makes the scene stable.
The same project works correctly on a different PC with a stronger GPU (NVIDIA).
Reduced version of Qt Design Studio seems to use its own runtime, so external Qt installations (MinGW/MSVC) don’t affect the puppet.
Even small textures (1–2K JPG or HDR) cause the same device loss on this AMD system.
According to Qt documentation, lightProbe requires runtime filtering / mipmap generation when raw images are used, which may be heavy on some GPUs.My questions:
Is this a known issue with Qt Quick 3D + D3D11 backend + AMD GPUs?
Is the DS reduced runtime missing some image format plugins such as proper HDR/KTX support?
Should lightProbe textures be prefiltered using qt6_add_lightprobe_images() before runtime?
Is there a recommended workflow to make lightProbe stable on lower-end AMD hardware?
Any suggestions on how to diagnose or force Qt to fallback safely (e.g., WARP/software rendering for the puppet)?The project works correctly without lightProbe and only fails during IBL processing.
Other 3D features (materials, models, skybox, post-processing) work fine.
This looks like a DXGI/D3D11 device removal triggered specifically by the IBL pipeline.
Any insights or similar experiences would be highly appreciated.
Thank you! -
Is this "Warning: Failed to load image: <path_to_ktx2>" the actual output or have you redacted the path?