Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.0f1
2019.3
2020.1
Issue ID
1186752
Regression
No
Additional integer operation is added to a Shader causing performance drop on older devices when Compiling with Gles3 or Gles2
Steps to reproduce:
1. Open attached project "Case_1186752"
2. Navigate to Project -> Assets and select "Cutout Hlsl" shader
3. In the Inspector window Press "Compile and show code"
4. In the open text editor scroll down to the line 107
5. Notice the additional integer operation is added if(((int(u_xlatb1) * int(0xffffffffu)))!=0){discard;}
Expected results: No additional Integer operation is added making the build smooth on older devices
Actual results: Additional Integer operation is added making a performance slowdown on older devices
Reproducible with: 2017.4.0f1, 2017.4.33f1, 2018.4.12f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a9
Shader compiles clip/discard incorrectly on GLES devices, causing noticeable slowdowns
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment