Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2018.2.X



Found in


Issue ID




"using static" directive causes Unity to not find the class in the script



The issue happens wit .NET 4.6 only

To reproduce:

1. Open the project, attached by the tester (
2. Add Fred.cs script to any game object
3. (Optional) Examine the code in Fred.cs

Expected: using "using static" directive in the script doesn't prevent Unity from finding the class in the script

Reproduced in 2017.1.0a6, 2017.1.2p2, 2017.2.0f3, 2017.3.0b6, 2018.1.0a1

Comments (3)

  1. Vapid-Linus

    Jul 15, 2018 10:56

    Still a problem in 2018.2.2f1 when using a statically imported class from a class inside a namespace.

  2. dog_funtom

    May 19, 2018 19:22

    Followup: actually, it is found for a moment, just after compilation (or maybe during). Can be attached to GO and displayed in inspector as usual. Then it changes to invalid and stays like this for a moment. And only then it disappears and can't be added.

    But during/just after a next compilation, it appears back, then follows the described cycle again.

    In other words, it is found successfully, but then somehow "unfound" by some kind of process that runs after errorless compilation.

  3. dog_funtom

    May 19, 2018 19:13

    2018.1.0f2 still can't find such script.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.