Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2018.4
2019.4
2020.2
2020.2.2f1
2021.1
2021.2
Issue ID
1310791
Regression
No
[DX12] Editor crashes when creating a RenderTexture with RenderTexture.antiAliasing value higher than supported by hardware
How to reproduce:
1. Open the attached "1310791 repro" project
2. Click the "Crash Unity" menu item from "Bug repro" > "Crash Unity"
Expected results: the Editor throws a warning that the anti-aliasing was changed to a supported value and doesn't crash
Actual results: the Editor crashes
Reproducible with: 2018.4.31f1,2 2019.4.20f1, 2020.2.5f1, 2021.1.0b6, 2021.2.0a4
Notes:
-This issue reproduces with DirectX12 and doesn't reproduce with DirectX11, Vulkan, OpenGLCore, OpenGLES2, and OpenGLES3 graphics APIs
-The RenderTextureFormat parameter doesn't seem to matter whether the Editor will crash or not
-The anti-aliasing value that causes the crash seems to be hardware dependent
-On 2018.4.31f the Editor doesn't crash but freezes with infinite "d3d12: swapchain present failed (887a0005)" messages being logged
-When using DirectX11 instead of crashing a warning message is thrown stating:
"RenderTexture's anti-aliasing changed from 6 to 4 due hardware limitations."
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
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a12