Search Issue Tracker
Fixed
Votes
1
Found in
5.3.4f1
Issue ID
791476
Regression
No
[HLSLcc] GLES3 compiler produces incorrect code when comparing a boolean vector
Steps to reproduce:
1. Open attached "Case 791476 repro" project
2. Select "test.shader" shader and click "Compile and show code"
3. In compiled shader on line 410 notice that instead of comparing with tb4.y, it compares with tb4.x again.
Work arounds:
a. In "test.shader" change line 53 to "float2 thresholded = (inp < 0.2) ? 0.0f : 0.5f;".
b. In "test.shader" on line 65 set the 1st argument of PixelFilteringMean to col.rg instead of "i.uv".
Reproduced with: Unity 5.4.0b15; 5.3.4p4; 5.3.4f1; 5.1.4f1;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment