Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X
Votes
5
Found in
2021.3.38f1
2022.3.28f1
6000.0.1f1
7000.0.0a1
Issue ID
UUM-71454
Regression
No
Entering "Configure Avatar" inside the Inspector locks it
Reproduction steps:
1. Open the attached “Repro“ project
2. Expand and select the Avatar of the “Assets/VillagerHuman.fbx“ Model
3. Select “Configure Avatar” in the Inspector
4. Observe the Inspector
5. Select any GameObject in the Hierarchy window
6. Observe the Inspector
Expected result: The Inspector is unlocked and switches to the GameObject’s components view
Actual result: The Inspector is locked and remains on the Avatar Inspector view
Reproducible with: 2021.3.38f1, 2022.3.28f1, 6000.0.1f1
Reproducible on: M1 MacOS 14.4.1
Not reproducible on: No other environment 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
- SpeedTree does not move when using WindZone
- "Undeclared identifier 'LinearToSRGB'" error is thrown when creating a color variable with HDR color mode and assigning a Custom Render Texture target in Shader Graph
- Input System package is missing when creating a new HDRP project
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
Stevegustus
Jun 28, 2024 02:20
I just had this happen to me with 2022.3.34f1 using MacOS 14.5. The Inspector is "locked" (padlock icon in closed position) and it can not be easily unlocked.
An earlier workaround I saw didn't work for me. And that was to click on the "Done" button in Muscles & Settings. I did this and no change. I tried variations of this by clicking on different things in Scene and Project without success.
The solution for me was to click on the padlock icon for Inspector and then cycle between other tabs within the same frame (for example Lighting). When I returned to Inspector it was unlocked and worked normally. At least that's what I think cleared it up.
minsumandoo
May 08, 2024 18:02
It happens to me too.
Windows 11
2022.3.26f1, 2022.3.28f1