Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.4.0f1
Issue ID
1018644
Regression
No
[DirectX12] Crash when selecting DirectX12 if Post-Processing effects are used (PRISM plugin)
How to reproduce:
1. Open the "DX12 Crash.zip" project
2. Open the "scene" scene
3. Edit > Project Settings > Player
4. Select DirectX12 as main graphics API
Actual result: Unity crashes.
Reproducible with: 2018.2.0a5, 2018.1.0b13, 2017.4.1f1, 2017.3.2f1.
Not reproducible with: 2018.2.0a6, 2018.2.0a7.
Workaround:
Select DirectX12 in another scene, then open the scene with Post-Processing effects.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment