Search Issue Tracker
Fixed in 2022.3.5f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a22
Votes
2
Found in
2022.2.7f1
2023.1.0b4
2023.2.0a2
Issue ID
UUM-27260
Regression
No
List.Capacity is used instead of count in ”SetSharedMaterials”
How to reproduce:
- Open the attached project "SetMaterialsBug.zip"
- Enter Play Mode
Expected results: No errors are thrown
Actual results: "Unexpected number of materials!" is thrown in the Console window
Reproducible with: 2022.2.7f1, 2023.1.0b4, 2023.2.0a2
Could not test with: 2020.3.45f1, 2021.3.18f1 ('Renderer' does not contain a definition for 'SetMaterials')
Reproducible on: Windows 10
Comments (1)
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
- 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
peturdarri
Feb 15, 2023 11:26
To clarify the description, this happens when trying to set fewer materials on a renderer than there currently are on it. It applies to both SetMaterials and SetSharedMaterials.