Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0f3
Issue ID
821291
Regression
Yes
Edge length based tessellation causes AMD drivers to crash
Reproduction steps:
1. Open the project.
2. Open the "crash" scene
3. Play the scene
4. Wait for drivers to crash.
Unity should now freeze and a message should appear in the corner of the screen that display drivers have crashed.
Note: Calling UnityEdgeLengthBasedTess causes drivers to crash. It happens only in DX11 and DX12 modes with AMD graphics cards.
Reproduced on: 5.5.0a5, 5.4.0f3, 5.3.6p2
No reproduction on: 5.3.5f1, 5.2.5f1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #813805