Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.6f1
6000.4.0b6
6000.5.0a5
Issue ID
UUM-133214
Regression
No
Material “TerrainLit” is missing space in Shader Graph's Graph Inspector
Steps to reproduce:
1. Create new Unity project
2. In Project window create Shader Graph Asset (Lit Shader Graph for example)
3. Open Shader Graph
4. In Graph Inspector > Graph Settings > Material observe “TerrainLit” naming
Actual results: “TerrainLit” material is missing space
Expected results: “Terrain Lit” material is not missing space
Reproducible with versions: 6000.3.6f1, 6000.4.0b6, 6000.5.0a5
Can’t test with versions: 6000.0.66f2 (no “Terrain Lit” material available is Graph Inspector)
Tested on (OS): Ubuntu 24.04, macOS Silicon Tahoe 26.2 (M1)
Notes:
- "Sprite Lit", "Six-way Smoke Lit", "Sprite Custom Lit" presented with spaced
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.