Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.2.14f1
6000.5.0a3
Issue ID
UUM-129109
Regression
No
[RenderingDebugger] ReflectionProbeAtlas overlay does not respect the set size
Steps to reproduce:
- Download attached project and open in Unity.
- Enable Development build.
- Build and Run project.
- Enable Rendering Debugger overlay (ctrl+delete)
- Go to Frequently Used section.
- Go through the Map Overlays till you reach the Reflection Probe Atlas.
Actual results: Reflection Probe Atlas overlay should be the 50(map size).
Expected results: Reflection Probe Atlas overlay is smaller compared to other maps.
Reproducible with versions:
6000.2.14f1, 6000.5.0a3
Tested on (OS):
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS Tahoe: 26.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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.