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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
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.