Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.5.0f3
Issue ID
862725
Regression
No
[Standard] Setting metallic map throws NullReferenceErrors and breaks usage of Material in inspector after upgrading
To reproduce:
1) Open attached project
2) Create a new material in it
3) In inspector, click the button to add a Metallic map to that material
4) Try adding something as Metallic Map (tested with "Abstract - ..." textures)
Expected: Material is still editable after changing map
Actual: Inspector breaks with only Albedo and Metallic Map visible when inspecting Material, a lot of NullReferenceErrors are thrown in Console
Reproduced in, 5.4.0f3, 5.5.0f3, 5.5.0p3, 5.6.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment