Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
7.2.0
Issue ID
1218646
Regression
Yes
Crash on D3D12Fence::Wait when opening HDRP default "SampleScene" scene with HDRP + DXR
How to reproduce:
1. Create a new HDRP project on Unity 2019.3.0f6 or 2019.3.1f1
2. Update HDRP to 7.2.0 or 7.2.1
3. Go to Window->Render Pipeline->HD Render Pipeline Wizard
4. Click on "HDRP + DXR" and press "Fix All"
5. Wait for Unity to restart
Reproducible with: 7.2.0 (2019.3.0f6, 2019.3.1f1), 7.2.1 (2019.3.0f6, 2019.3.1f1)
Not reproducible with: 7.1.8 (2019.3.0f6, 2019.3.1f1, 2020.1.0a23), 7.2.0 (2020.1.0a23), 7.2.1 (2020.1.0a23), 2017.4.37f1, 2018.4.17f1 (Package version not available)
Full stack trace:
0x00007FF72DD59E8C (Unity) D3D12Fence::Wait
0x00007FF72DD80E7C (Unity) AsyncReadbackDataD3D12::Update
0x00007FF72DDCA995 (Unity) GfxDeviceWorker::RunCommand
0x00007FF72DDD1E0B (Unity) GfxDeviceWorker::RunExt
0x00007FF72DDD21C8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF72EC60173 (Unity) Thread::RunThreadWrapper
0x00007FFD95837974 (KERNEL32) BaseThreadInitThunk
0x00007FFD9803A271 (ntdll) RtlUserThreadStart
Note: After enabling HDRP + DXR opening the scene crashes the project every time
Comments (1)
-
IcyWalker
Sep 14, 2020 19:21
Happens to me also. I thought I broke something but it was this exact bug ,looks like it's way to experimental for anyone's use just yet
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1216890