Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2018.4
2019.4.8f1
2020.2
Issue ID
1275152
Regression
No
[HLSLcc] Wrong atomic min/max parameter types
Reproduction steps:
1. Open attached project "OpenGLCompute.zip"
2. In Project window, open Assets/Repro.compute compiled code
3. In Script editor, observe main() method's line 3
Expected result: atomicMin(int, int)
Actual result: atomicMin(uint, uint)
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b4
Edit: same applies for Metal
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
- 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
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a2
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b9
Resolution Note (fix version 2020.1):
Fixed in 2020.1.10f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.13f1