Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0f3
Issue ID
932272
Regression
No
Shader fails to compile when 2 equality tests are made and stored back into same float vector with certain Graphics API selected
To reproduce:
1. Download and open attached "VertexIDTest.zip" project.
2. Select the "VertexIDTest" shader from the project view.
3. Press the "Compile and show code" button in the inspector.
Expected result: Shader compiles without any errors.
Actual result: Shader fails to compile. Errors appear in the console.
Reproduced with: 2017.2.0b3, 2017.1.0f3, 5.6.2p4, 5.5.4p1.
Notes: Shader fails to compile when Graphics API is set to either OpenGLES3, OpenGLES2, OpenGLCore, Vulkan. Error appears when the following conditions are met(line 31 in VertexIDTest shader):
- Testing equality between the vertex ID (SV_VertexID) and constant values in a vertex shader.
- There are more than two equality tests, and the test results are going to be stored into the same float vector.
Verified with: 2017.3.0b1
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
Add comment