Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
9
Found in
2019.1.0b10
Issue ID
1174950
Regression
Yes
[Linux] 3D With Extras projects will throw constant OpenGL Error: Invalid texture unit! errors
This issue has no description.
-
DavidCoen
Aug 21, 2021 10:11
I am hitting this with a GLES3 shader on windows desktop (unity 2020.3.16f1, windows 10, NVIDIA GeForce GTX 670)
for me at least it seems related to the instruction count in the shader -
BHGAhuerta
Dec 20, 2019 19:18
It looks like our issue was fixed by rebuilding our asset bundle. Sounds similar to (1195750)
-
BHGAhuerta
Dec 20, 2019 16:34
I am also seeing this issue with some Android devices. This is happening on a Galaxy S9+ but not on a Samsung SM-T350
12-20 11:33:24.077: E/Unity(28700): (Filename: ./Runtime/GfxDevice/opengles/DeviceStateGLES.cpp Line: 72)
12-20 11:33:24.078: E/Unity(28700): OpenGL Error: Invalid texture unit! -
tictocblake
Nov 22, 2019 01:14
I also see this error on Android
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
- FP32 is used for a temporary when compiling a shader for GLES or Vulkan
- The highlight that was created with Highlighter.Highlight does not disappear when the window is closed with the element
- [URP] CommandBuffer warnings thrown while debugging Depth Overlays with Post-processing enabled in Rendering Debugger
- hlslcc: float image atomics don’t work
- [Apple silicon][M1] Game view FPS is very low when the view is moved to an external display
Resolution Note (fix version 2020.1):
We lack the original hardware where we encountered this issue for verification. As it's low-hanging issue and we have seen lots of iteration here, we are assuming this issue has been resolved. Please file a new issue or re-open if you encounter this.
Resolution Note (fix version 2019.3):
We lack the original hardware where we encountered this issue for verification. As a fix has been committed, it's low-hanging issue and we have seen lots of iteration here, we are assuming this issue has been resolved. Please file a new issue or re-open if you encounter this.