Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131806
Regression
No
The Inspector does not shown SkinnedMeshRenderer Bounds when they are overriden by script
Reproduction steps:
1. Open the attached “IN-126846” project
2. Open the SampleScene
3. Enter Playmode
4. In the Hierarchy window, select the "unitychan_dynamic no_mesh" GameObject
5. Scroll down in the inspector window to the SkinnedMeshRenderer Component at the bottom
6. Observe the Inspector and the Game view
Actual results: In the Inspector, the bounds fields remain 0'd, while in the Game view the bounding box drawn and overriden on the SkinnedMeshRenderer, by the VMeshAnimator.cs script is clearly changing each frame
Expected results: The Inspector shows the size of the SkinnedMeshRenderer bounds even if they are overriden by script
Reproducible with: 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Couldn’t test with: 2023.1.0a3 (After version downgrade the test project does not work)
Reproducible on: Windows 11 (by reporter), macOS 26.2
Not reproducible on: No other environments tested
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
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.