Search Issue Tracker
Fixed in 7.1.7
Votes
0
Found in [Package]
7.1.5
Issue ID
1202902
Regression
Yes
[HDRP] Crash on GfxDeviceD3D12::BuildTopLevelAccelerationStructure when changing Forced Screen Percentage
Steps to reproduce:
1. Create a new HDRP project or open the one attached by the user
2. Open the DXR + HDRP section of the HDRP Wizard (Window -> Render Pipeline -> HD Render Pipeline Wizard -> HDRP + DXR)
3. Make sure the project is HDRP + DXR ready (if not, press the "Fix all" button)
4. Select the HDRenderPipelineAsset in the Project Hierarchy
5. In Inspector find Dynamic Resolution
6. Check "Enable" and then "Force Screen Percentage"
7. Change the Forced Screen Percentage value
Reproducible with: HDRP 7.1.5 (2020.1.0a17), 7.1.6 (2019.3.0f4, 2020.1.0a17), 7.1.7 (2020.1.0a18)
Not reproducible with: HDRP 7.0.1 (2019.3.0b4), 7.1.1 (2019.3.0b4, 2019.3.0b12), 7.1.2 (2019.3.0b4, 2019.3.0b12)
Couldn't test HDRP 7.1.5 on 2019.3.0b4, 2019.3.0b12 due to UnauthorizedAccessException when trying to fix the HDRP + DXR issues in HDRP Wizard
Stacktraces:
0x00007FF62AF4E244 (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FF62AF4D9BF (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FF62AFA6E3B (Unity) GfxDeviceWorker::RunCommand
0x00007FF7D5DC537A (Unity) GfxDeviceD3D12::BuildTopLevelAccelerationStructure
0x00007FF7D5DC4C3C (Unity) GfxDeviceD3D12Base::BuildRayTracingAccelerationStructures
0x00007FF7D5DFCC87 (Unity) GfxDeviceWorker::RunCommand
Notes:
- Stacktraces seem to appear interchangeably
- After the crash, as long as the editor doesn't quit, it leaks memory
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
- Building "ManagedStripping" fails when a script uses a custom package
- [Quest] Visual artifacts are present when rendering Spot lights with Forward+ Rendering Path in XR
- [ColorCheckerTool] DropDown menu appears in the wrong location
- [ColorCheckerTool] Documentation icon leads to a broken documentation page
- [RayTracing] Impossible to identify individual instances added using RTAS.AddInstances in a compute shader when using ray queries.
Resolution Note (fix version 7.1.7):
Fixed in 2020.1.0a21
Resolution Note:
Fixed in 2019.3.0f6 (27ab2135bccf)