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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1279753