Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2017.4.15f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1113055
Regression
No
[OpenGL] Generated shader code uses gl_TessLevelOuter[3] instead of gl_TessLevelInner[0] when compiling with GLSL generator
Steps to reproduce:
1. Open the attached Project "OpenGL_SV_InsideTessFactor"
2. Open "Test" Scene
3. Enter the Play Mode to trigger Update
4. Move the View Camera around in the Scene Window
Expected result: Tessellation Triangles remain visible regardless of the view angle of position
Actual result: Tessellation Triangles are flickering when changing view angle or position or calling the Update
Reproducible with: 2017.4.18f1, 2018.3.2f1, 2019.1.0a14, 2019.2.0a1
Note:
Only reproducible on Win GLCore & Mac GLCore(Intel HD only)
Mac Radeon Metal - Shader not supported - correct as Metal doesn’t support geometry shader
Mac Radeon GLCore - works with NO glitching
Mac IntelHD Metal - Shader not supported - correct as Metal doesn’t support geometry shader
Mac IntelHD GLCore - works with glitching <———————
Win GTX980m DX11 - works with NO glitching
Win GTX980m GLCore - works with glitching <———————
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
- 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
Resolution Note:
Won't fix as Mac OpenGL is depreciating and only on Intel HD card.