Unity Inspector stuck on one object,Unity Inspector stuck on one item (Not locked)

E

13

0

The inspector is currently stuck on one object, and I can’t focus on other objects in the scene. And no, the inspector is not locked, I also tried locking and unlocking again just to make sure, and no the problem wasn’t that. What could be the reason for this?,I tried editing a scene in Unity today, and when I clicked on one object, it was focused in inspector. This is normal behavior, but when I clicked any other object on the scene, the inspector left focused on the same object. I tried locking and unlocking the inspector tab, and it sure wasn’t the solution. Any other reason this could be happening?

Elishaelision answered 22/1 at 14:45 Comment(4)

Have you tried to restart Unity? To reset the layout? (top right corner of Unity window)

– Spiel 17/3, 2020 at 11:15

Also have this issue... Been going on for quite a few 2019.3 versions..

– Evers 21/7, 2020 at 21:54

Ok, I've found a solution that works for me. Or rather discovered when this issue occurs. Occasionally when I use "V" snapping it gets stuck in the inspector. Simply use "V" snapping again and then undo + deselect. Let me know if it solves it for you guys!

– Inhalation 29/8, 2020 at 13:18

Thank you! A simple undo (select) works in my case

– Scenery 19/10, 2023 at 14:19

D

0

I have a solution, try to enable and disable debug on inspector, it works for me

Downhearted answered 22/1 at 10:18 Comment(2)

This does work, but it needs to be done again every single time you change your object.

– Meperidine 11/6, 2020 at 0:26

Thank you for this; What version is everyone using? (2019.3.10f1) and has anyone solved it completely?

– Cavalry 23/7, 2020 at 21:22

S

0

going to debug and back makes it refocus on whichever new object you’ve selected, but then it stays focused on that object until you toggle debug again. It’s hard to believe that a game engine would have such a bug.
Edit: Turns out restarting Unity cleared the bug.

Surround answered 22/1 at 10:19 Comment(1)

I know this is very old, but the aside from the possible GetComponent<Transform>() (which I think was optimised in Unity 5) the actual reason why modifying the rotation (or position) of a game object with rigidbody is slow, is that this circumvents the physics system and all the physics of the object needs to be recalculated. I've found a comparison of the performance of setting position different ways, and the result was that if you have a rigidbody, ALWAYS use Rigidbody.MovePosition() and MoveRotation().

– Cheerless 25/6, 2018 at 12:51

I

0

Kinda glad to see I’m not alone having this issue.
The normal < > Debug fix works, but it’s not a solution I can work with…
There’s got to be another fix??

Inhalation answered 3/7, 2020 at 13:1 Comment(0)

E

0

Also have this issue… Been going on for quite a few 2019.3 versions…

Evers answered 21/7, 2020 at 21:54 Comment(0)

M

0

I dont know either i have the same bug. I tried to force refreshing everytime I select a new object but that doesn’t work either.

Melidamelilot answered 1/8, 2020 at 18:31 Comment(0)

I

0

Ok, I’ve found a solution that works for me.
Or rather discovered when this issue occurs.
Occasionally when I use “V” snapping or “shift+move” it gets stuck in the inspector.

Simply use"shift+move" again and then undo + deselect.

Edit: Managed to record me doing the fix:

It happened again today. Grabbed a video of the problem, Shift + drag fixes it!
https://www.jottacloud.com/s/106758ccdcacc0f4188a5adb4b714445928

Inhalation answered 22/1 at 10:19 Comment(2)

This solution did not work for me. Definitely feels related to "V" snapping as I was just using snapping before the issue started occurring. Unity 2019.4.9

– Surly 19/9, 2020 at 2:12

That's actually worked. Thank you!

– Diaphanous 14/5, 2022 at 14:10

S

0

I was able to reproduce this.

Using the “V” to snap vertices - if an accidental selection of multiple objects happens when attempting to move the vertice, and you then press Esc to cancel the operation (not sure if Esc is required to produce the bug), the Inspector will then hit this problem/bug. Restarting the Unity Editor is required to make it fully functional again.

Tested on Unity 2019.4.9

Surly answered 19/9, 2020 at 2:48 Comment(0)

D

0

Hi. Just wanted to say it also happens in 2020.1.4f1

Dodder answered 31/10, 2020 at 22:20 Comment(1)

I still got this issue. Must be some key combo I accidentally press or something, but at least I have a working fix.. As poorly mentioned in an earlier post; find an empty space in editor scene View. Press and hold v and drag said empty space. That unfreezes the locked object every time!

– Inhalation 1/11, 2020 at 17:23

R

0

This problem just cropped up for me, too. 2020.1.12f1 and 11f1

I can select objects in the scene view and in the hierarchy, but the inspector never switches to the new object. Entering playmode causes the selection to suddenly switch.

Has anyone come across a fix for this yet?

I suspect it’s a registry problem, or something. I doubt filing a bug report will help, since Unity will most likely be unable to reproduce the problem on their end, even if you send them your project file.

Rah answered 11/11, 2020 at 16:1 Comment(0)

K

0

This is still an issue for me, I’ve been tracking this for quite sometime. All the above suggestions work, specially the debug which I discovered after a bit of frustration (prior to this thread).

Restarting unity corrects this for a period of time BUT if you have a large project, which I do, this is ULTRA time consuming and unfortunate.

I’ve noticed it occur after hours of working, or within a few seconds so I highly doubt it has anything to do with any specific functionality performed by users because I’ve had it occur under any / all situations and I’m not really using any of the above suggestions during these times.

I submitted a bug report over a year ago, then another, and another…now I’m here.

I’ve tried reinstalling unity, creating a test project, using different versions (current 2019.x+), all seem to have this issue occur eventually. I’ve been a unity user for some time now…this is a new “feature” that’s not super appreciated ;p

…not to drone on, but it takes roughly 8m to open my project currently, by days end I lose no less than 1.5 hours fk’n with this (that’s 11 reboots btw).

Karena answered 22/1 at 10:21 Comment(2)

Hi, been trying to reproduce this issue again to screenrecord my solution which works 100% of the time. I'll try to keep this thread in mind next time it happens. For me, hold "V" or "shift" and drag over an empty area fixes this! Every time. Ps: Anyone know why I can't reply to this thread? I've done it before....

– Inhalation 18/1, 2021 at 17:57

I've been fortunate these last few days, but as soon as this little gem resurfaces I'll be sure to try ur video example I swear I've probably done so with my multiple encounters but at this point I'd try anything

– Karena 20/1, 2021 at 20:17

D

0

Happens for me too. Restarting does not fix it. Happens every 10-20 clicks Now.
Restarting used to fix it.

Decastyle answered 22/5, 2022 at 4:30 Comment(0)

P

0

Set the inspector to debug and then normal again.
Doing that everytime you select an object, so 1000 times in a day is ridiculous. It’s still present in the new version. Unity team, do something instead of laying of 250 devs…

Recommended topics

Hot tags