Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.1.0a2
2019.3
2019.3.7f1
2020.1
2020.2
Issue ID
1239923
Regression
Yes
HLSLcc compute shader for loop condition is generated incorrectly in shader
How to reproduce:
1. Open attached project "TestComputeShader.zip"
2. In Project window, double click on "test" to open the compute shader
3. In Inspector window, click on "Show compiled code"
4. Compare "test.compute" for loop condiftion with "Compiled-test-.shader" loop condition
Expected result: the loop condition is the same
Actual result: the loop condition is different
Reproducible with: 2019.1.0a2, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Not reproducible with: 2018.4.23f1
Could not test with: 2019.1.0a1 (sometimes the issue reproduces, sometimes it does not)
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note (fix version 2020.2):
Verified in:
Version: 2020.2.0a14
Resolution Note (fix version 2020.1):
Verified in:
Version: 2020.1.0b14
Resolution Note (fix version 2019.4):
Verified in:
Version 2019.4.3f1