Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.20f1
2023.2.16f1
6000.0.0b13
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-67559
Regression
No
Components are flattened in the Inspector when using a custom initializer
How to reproduce:
1. Open the “InspectorOverlappingIssue“ project
2. Open the “Assets/BugReport/BugReportScene.unity” scene
3. In the Hierarchy window select the “PlayerNameDisplayers” GameObject
4. In the Inspector window locate the “Player Name Displayer” script Component
5. Expand the “Init” section
6. Make sure the Inspector window is left open
7. From the Project window drag the “Assets/BugReport/PlayerNameDisplayer.cs” script on the “PlayerNameDisplayers” GameObject
8. Observe the Inspector window
Expected result: All the Components are spaced out evenly
Actual result: All the Components are flattened together
Reproduced with: 2022.1.0a15, 2022.3.20f1, 2023.2.16f1, 6000.0.0b13
Not reproduced with: 2021.3.36f1, 2022.1.0a14
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproduced on: No other environment tested
Note: Reselecting the GameObject in the Hierarchy window resolves the issue
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.