Search Issue Tracker
Won't Fix
Votes
1
Found in
6000.0.31f1
6000.1.0b2
Issue ID
UUM-92830
Regression
No
"Property (urp_ReflProbes_BoxMin) exceeds previous array size" warning spams console after switching platforms
Steps to reproduce:
- Make sure you have the latest Unity 6000.1 installed, with the Android module too
- Create a new project with the Universal 3D template
- Add a cube to the scene and save the scene
- Switch to the Android platform
- Switch BACK to Standalone
Actual results: Hundreds of warnings in the console. They can be cleared, but they keep spamming afterwards too.
!image-2025-01-14-15-11-30-270.png|width=1311,height=302!
Property (urp_ReflProbes_BoxMin) exceeds previous array size (64 vs 32). Cap to previous size. Restart Unity to recreate the arrays.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
Property (_AdditionalLightsLayerMasks) exceeds previous array size (256 vs 32). Cap to previous size. Restart Unity to recreate the arrays.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
Expected results: No warning in the console
Reproducible with versions: 6000.1.0a2, 6000.1.0b2, 6000.0.35f1, 6000.0.27f1
Not reproducible with versions: 6000.0.26f1
Tested on (OS): Windows 11
Notes:
- for newer versions, these repro steps would lead to a crash, when closing the editor, but the crash is inconsistent for me.
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
- "State comes from an incompatible keyword space" error when clicking on a shader
- Test Runner's Player test fails when the IL2CPP scripting backend is selected
- Not all of the Profiler Modules can be reordered
- [Accelerator] Texture uploads to the cache server are duplicated when switching between Texture Formats
- CommandBuffer.DrawProcedural fails to render when RenderGraph and Metal Graphics API are enabled
Resolution Note:
Due to the way these arrays are structured, fixing this properly is a difficult task with a large halo effect, and will need a larger undertaking to fix in the future.
Unfortunately, our best workaround at the moment is to restart the editor.
Thank you for bringing this issue to our attention.