Search Issue Tracker

Won't Fix

Votes

0

Found in

2023.2.9f1

Issue ID

UUM-70491

Regression

No

D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present

--

-

Reproduction Steps:
1. Open the attached “repro-project“
2. Open the “Assets/OutdoorsScene.unity“ scene
3. In the Lightning window select "Generate lighting"

Expected Result: Lighting bakes successfully without causing a crash
Actual Result: Unity crashes with a “Fatal Error!“ pop-up

Reproducible with: Unity 2023.2.9f1 (by reporter)

Notes:
1. CQA could not reproduce the issue
2. According to users a “Fatal Error!“ pop-up appears stating: “Failed to present D3D11 swapchain due to device reset/removed. This error can happen if you draw or dispatch very expensive workloads to the GPU, which can cause Windows to detect a GPU Timeout and reset the device. (see [https://docs.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery).|https://docs.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery).If] if you believe this error is due to built-in Unity functionality, please submit a bug. This is an unrecoverable error and the editor will shut down.“
3. Reproducible with both DirectX11 and DirectX12 Graphics APIs

Workaround:
1. Setting the Search Distance Multiplier parameter to zero (Lightning window → Probe Volumes tab)
2. Using Vulkan Graphics API

First few lines of the stack trace:
0x00007FFEDE84EEE1 (Unity) D3D12Fence::Wait
0x00007FFEDE836BD3 (Unity) GfxDeviceD3D12::FlushCommandList
0x00007FFEDE838083 (Unity) GfxDeviceD3D12::GetComputeBufferData
0x00007FFEDFF5C522 (Unity) GfxDeviceWorker::RunCommand
0x00007FFEDFF640FF (Unity) GfxDeviceWorker::RunExt

  1. Resolution Note:

    There are no fixes planned for this Bug

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.