Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4
2018.4
2019.4
2020.1
2020.2
2021.1
2021.1.0a10
2021.2
Issue ID
1299802
Regression
No
InvalidOperationException errors thrown in console when multi selecting mesh renderer objects with an array size >64
How to reproduce:
1. Create a new project and open it
2. Create 2 Cubes in the Hierarchy and select them both
3. In the Inspector edit the MeshRenderer component to have a material array size of >64 (For example 65)
4. Observe the console
Expected result: When multi select inspecting objects with a mesh renderer component with an array size >64, the array is not displayed and no errors are thrown
Actual result: When multi select inspecting objects with a mesh renderer component with an array size >64, the array is correctly not displayed but "InvalidOperationException" errors are also spammed in the console
Reproduced in: 2021.2.0a1, 2021.1.a10, 2020.2.0f1, 2020.1.17f1, 2019.4.16f1, 2018.4.30f1, 2017.4.40f1
-
Resolution Note:
Original case fixed in: 2021.2.0a5
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
This is a duplicate of issue #1279753