In alpha 9
Are you sure it’s not locked?
I can confirm this. Not sure how to reproduce, but saw it multiple times during recompile-reload cycles. In my case, selecting objects in the project browser did not change the inspector. I had to select something in the hierarchy first, then the inspectors would react to selection in the project browser again.
Did not see it yet in a11.
1 Like
Yeah that’s it. I’ll keep an eye out for it in a11, not seen it yet though.
I haven’t used Alpha 9 a lot and never noticed this behaviour but Alpha 9 is no longer in the works since Alpha 11 has just been released. I worked with it some time today and didn’t noticed this behaviour either.
It also randomly happened in the previous version (or maybe 2 versions ago?) of 2018.4 LTS and Windows, haven’t seen it in the latest version though.
Me neither and I’ve been using it for several hours this morning.
Just got it in a11, so I guess it’s still there somehow.
I got it right after opening the editor.
The editor was fully open? What did you try to select? Did you try selecting it in the Hierarchy view or in the scene view?
Similar to what I mentioned before.
After opening, trying to select anything in the project browser didn’t update the inspector (it was blank).
Only after selecting a hierarchy object the inspector was normal again.
I’ve tried this, the only objects that do not update the inspector are the main folders in Assets and Packages. For example, if I select the Scene folders in Assets nothing happens in the Inspector, if I select the sub-folders in Scene or a scene, the Inspector updates.
Incidentally, and completely unrelated, I just noticed that I am missing the Package Manager UI in Packages…
Yeah, I can’t reproduce it either. It just happens sometimes. I didn’t get it yet in compile-reload cycles in a11, but it was very infrequent with a9 too, so I’m not sure anything changed.
Me too. Since when is it no longer a package? I think it’s been a while since I last noticed it there.
I guess since 2019.3:
1 Like
Okay, I stopped following the beta testings…
The inspector has been a bit crazy since the first 2020 alpha. I was about to post a rant here but I’m glad someone else saw it
I still have to experience this… I’ve been using 2020.1 for hours lately without noticing this problem.
I’ve been having the same issue (first in 2019.3.3, now also in 2019.3.9). I can’t identify the cause, but once it starts, my inspector doesn’t update on ANY new selection in any window, unless I set the Inspector to Debug view (or vice versa). But then I have to do that for EVERY new object selection. So I generally just have to restart Unity, which is a good 4-5 minutes…
1 Like
I have this exact same problem in 2019.3.15f1. Very frustrating…
I have this problem, occasionally, with 2020.2…
1 Like
If you manage to find a way to reproduce the behaviour somewhat consistently, a bug report would be much appreciated.