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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
Won't fix because we do not actively support surface shader.