Search Issue Tracker
Fixed
Fixed in 6000.0.51f1, 6000.1.7f1, 6000.2.0b5, 6000.3.0a1
Votes
0
Found in
6000.0.0b13
6000.0.45f1
6000.2.0a8
6000.3.0a1
Issue ID
UUM-102023
Regression
No
“Property (_AdditionalShadowParams) exceeds previous array size (41 vs 32)…” warning is spammed when exceeding the light limit set in URP Config package
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene” Scene
3. In the Build Profiles (File > Build Profile), make sure iOS or Android platform is selected
4. In the Hierarchy window, select “Point Light (With shadow)” GameObject
5. In the Inspector, disable the GameObject
6. In the Hierarchy window, open the context menu of “PointLight x8 (without shadow) (2)" and select Duplicate
7. Open the context menu of “PointLight x8 (without shadow) (3)" and select Duplicate
8. Observe the Console
Expected result: The logged warning clearly shows that it occurred due to exceeding the maximum number of lights set in the universal-config package
Actual result: “Property (_AdditionalShadowParams) exceeds previous array size (41 vs 32)…” warning is spammed
Reproducible with: 6000.0.45f1, 6000.0.0b13, 6000.2.0a8
Couldn't test with: 2022.3.60f1 (no warning are thrown)
Reproducible on: macOS Sequoia 15.3.2 (M1 Max)
Not reproducible on: No other environments
Note: If the issue does not reproduce, try saving changes then closing and reopening the project after step 5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quality Hackweek] Activated Terrain Inspector is active only until the terrain GameObject is deselected when two or more Inspectors are open
- Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
- Errors are thrown and Inspector's UI element is not drawing when a GameObject with script component using a List<T> attached is selected
- ConfigurableJoint's parameters are not saved in the Prefab after Runtime Prefab baking
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
Add comment