Search Issue Tracker
By Design
Votes
0
Found in [Package]
10.2.0
Issue ID
1297323
Regression
No
[ShaderGraph] Lightmap texels are improperly invalidated when using custom Shader Graph materials
Steps to reproduce:
1. Download and open the attached project
2. Open GITest scene
3. Navigate to the Lighting window and click on Generate Lighting
4. Notice, how black shadows are bleeding underneath the blocks using custom ShaderGraph materials
Notes:
- Affects both CPU and GPU PLM
- URP lit shader is not affected
- Use the Texel Validity view to verify the issue
Doc ticket: https://unity3d.atlassian.net/browse/DOC-2828
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Nothing happens when entering a converter ID to target property in the Add Binding window when a converter ID was already added and removed
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
Resolution Note:
The difference in lightmap baking in this case is due to the Shader Graph having alpha clipping enabled, but the standard Lit material having it disabled. Starting in Unity 2021.2 there is an "allow material override" option on the Shader Graph to make it easier to switch this from the Material inspector rather than the Graph inspector. Prior versions would need to have it switched on the Shader Graph directly.