Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.3.0a1
2018.4
2019.2
2019.3
2019.3.0b1
Issue ID
1187094
Regression
Yes
Shaders compile as Shader Model 4+ even though the Graphics API is set to OpenGLES2 and Shaders are set to target Shader Model 2
To reproduce:
1. Open the user's attached project
2. Select the "SahderBug" shader in the Assets folder
3. Set the Compiled code only on OpenGLES20
4. Compile and show
5. Scroll to line 67, the exact line might differ from version to version
Expected: Compiling the shader does not produce any operators that are not compatible with devices that don't support Shader Model 4
Actual: Compiling a certain bit of shader code results in bitwise operator
Reproduced with: 2018.3.0a1, 2018.4.11f1, 2019.2.9f1, 2019.3.0b6,
Not reproduced with: 2017.4.33f1, 2018.2.13f1
2020.1.0a8 output differs from all the others so it's hard to say if it reproduces the issue or not
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