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
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Add comment