Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2019.2.10f1
2020.2
Issue ID
1213365
Regression
No
[Shaders] finalgbuffer:ShadingModelFinalGBuff and clip() affect UV coordinates
Reproduction steps:
1. Open project in "ShaderIssue.zip"
2. Notice how the "ForestFoliage" GameObject looks in the Scene
3. Open "Tree_Foliage_Inner" Shader in Project window
4. Comment line 37 and de-comment line 14 (look at the note below)
5. Inspect "ForestFoliage" Object in the Scene
Expected result: UV coordinates remain the same
Actual result: UV coordinates are changed and the Texture becomes blank
Reproducible with: 2017.4.37f1, 2018.4.19f1, 2019.3.4f1, 2020.1.0b1, 2020.2.0a2
Note: The issue can be fixed by either removing finalgbuffer:ShadingModelFinalGBuffer or enabling clip(c.a - 0.0) (or both)
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 because we do not actively support surface shader.