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
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
Add comment