Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2019.3.4f1
2020.2
Issue ID
1230927
Regression
No
GL culling state is reset after a call to GL.IssuePluginEvent
Steps to reproduce:
1. Open the attached project "GL_invertCulling.zip"
2. Build it on Android
3. Notice the LogCat
Expected results: GL culling state is not reset after a call to GL.IssuePluginEvent
Actual results: GL culling state is reset after a call to GL.IssuePluginEvent
Reproducible with: 2017.4.39f1, 2018.4.21f1, 2019.3.10f1, 2020.1.0b6, 2020.2.0a5
VLNQA00220, Samsung Galaxy Note9 (SM-N960F), Android 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android R, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Note: Does not reproduce with Standalone. This feature only specific to OpenGles
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] The Player freezes when disabling Bluetooth while connected to the headphones
- Addressable bundles are not retrieved from the cache when a WebGL Player is refreshed
- Sprites are incorrectly occluded by Sprite Physics Shape culling when behind in sorting order
- CPU usage is increased when the Editor is idle with the ProBuilder Package installed
- Unstable lighting when additional light sources are added in Shader Graph nodes
Resolution Note (2020.2.X):
By design: GL state is reset after plugin call to avoid side effects. Plugins are expected to set all of GL state that they need for rendering in their callback, including culling mode. As the plugin callback can be deffered to gfx thread which might happen after scripting has finished.