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
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
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