I’m no longer able to highlight the Script asset in Project tab by clicking the “Script” field of MonoBehaviour.
Double click doesn’t work either.
Bug Report: http://fogbugz.unity3d.com/default.asp?1287337_e1clu5m2npbsfcpg
2 Likes
Whoa, that’s annoying. I haven’t backed up your claim, but try perhaps reimport-all, and of course close/open Unity.
When you click on it do you see any internal console spew from Unity editor?
Nope, nothing in console.
And I’ve verified this on a newly created project.
me too. Same issue. A terrible upgrade
try 2019.4.12
1 Like
What about clicking on other linked assets? I mean such as if you have a Renderer that references a Material asset, and you click on that Material in the Renderer inspector, does it light up the asset?
They work fine. I think because they are not grayed out like the “Script” field.
1 Like
One more question: you say Doubleclick doesn’t work… testing here in 2019.4.8, doubleclick actually fires up the editor directly with that script… You’re saying that also fails?
If so, it would sound like perhaps all events are disconnected from that field. I hope that gets fixed ASAP!! It’s a bummer to get a massive showstopper in LTS like this.
Yep, double click stopped working either.
We had a particle system bug in 2019.4.8 which seems to be fixed in 2019.4.13. But now I’ve rolled back to 2019.4.12 and it seems to be a sweet middle - particles are working and no “Script” field bug.
1 Like
This is TERRIBLE. Please fix this immediately.
Same here, all disabled object fields are not interactable anymore.
Another thread confirming the same issue:
https://forum.unity.com/threads/2019-4-13-inspector-doesnt-navigate-script.992351
Using the editor in debug mode seems to work as normal.
You can still open the script by right clicking the component name and selecting “Edit Script”. But there is no way to highlight the script asset in the Project browser.
1 Like
I came here looking for a solution for this exact problem.
On 2019.4.13f1, Double clicking on the “Script” in the UI doesn’t open it. You can still open it by double clicking in the Project window or by selecting ‘Edit Script’ from the dropdown. But my habit is to double-click it, and that’s not working.
Same here, just noticed this. It’s an LTS no?
It’s an LTS Unity-style 
1 Like
Unity has confirmed the issue and a pending fix.
grrrr… reverted back to 2019.4.12f1 for the time being …
lucky me this didn’t re-trigger a SpriteAtlase rebake, which would take ~3h ( because of ASTC compression used for the atlas )
1 Like
Yea I’ve sent a report on this. An artist on my team reported this to me, as he uses that for navigating to scripts that he uses to manipulate shaders that he develops. As a coder, I spend most of my time with inspector in debug mode, so I didn’t notice it until he pointed this out. So for those of you that want a workaround, you can linger in debug mode until the next patch is out.
Guys, relax, “clicking things” is a feature and as such it isn’t something the LTS will get, since LTS only gets bug fixes.