Search Issue Tracker

Fixed in 2021.1.X

Fixed in 2019.4.X

Votes

29

Found in

2019.4.13f1

2021.1.0a2

Issue ID

1287702

Regression

Yes

Double-clicking a script in the Inspector window does not open the External Script Editor

Inspector Framework

-

How to reproduce:
1. Create a new Unity project
2. Create a new script and attach it to any GameObject
3. In the Inspector window double-click the Script field

Expected result: the external script editor is opened
Actual result: nothing happens

Reproducible with: 2019.4.13f1, 2021.1.0a2
Not reproducible with: 2018.4.28f1, 2019.4.12f1, 2020.1.0a1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a1

  1. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.0a5

  2. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.14f1

Comments (22)

  1. unity_XisIZrof4t6N2g

    Nov 05, 2020 10:23

    Sorry for the last post. But i have solved this issue atleast on my and my students computers.

    It had too do with letters like Å Ä Ö if you have these letters on a folder or on a script visualstudio wont open your scripts. Removing these letters and visualstudio and Unity works fine. This is however a very annoying little bug plz fix!

  2. unity_XisIZrof4t6N2g

    Nov 05, 2020 10:20

    test

  3. unity_XisIZrof4t6N2g

    Nov 05, 2020 09:23

    As a teacher this is so anoying each other student get this issue aswell. Creating a new project on desktop sometimes fixes the issue. And fiddeling around in prferences. But i agree with all above statements. This little bugg makes me not wanna work with Unity as is!

  4. amesa_unity

    Nov 03, 2020 09:51

    We have had to downgrade to 2019.4.12, not a big deal, but we have a team of game designers whose tools depend on this functionality . I hope this will be fixed in the next LTS release.

  5. Jadesa

    Nov 03, 2020 00:22

    However, good practice for mapping hierarchy of your project right into your brain!

    @OMX-JONSON
    Or simply rightclick on a header of the component, not so bad

  6. omx-jonson

    Nov 02, 2020 09:24

    As a workaround (which is painful, but still better than nothing) :
    In inspector, where the script component is, there's 3 small dots. Click them and from the dropdown select "Edit script". It opens Visual Studio.

  7. omx-jonson

    Nov 02, 2020 09:20

    Seriously, lads. How can something like this go into the LTS?
    You add new LTS version, and it has such a HUGE error.
    Nothing seems to work.
    Please fix this ASAP.
    What's next? Hide mouse cursor in editor? :)

  8. CGCowboy

    Nov 01, 2020 15:54

    This simple little bug is a workflow crusher when you have lots of scripts.

  9. AaronVictoria

    Nov 01, 2020 09:35

    Any one seeing this, a short-term workaround is to switch your inspector to debug mode.

  10. jcbadboy

    Oct 30, 2020 16:38

    This issue decreases usability and productivity. Very important to fix it.

Add comment

Log in to post comment