Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0b7
Issue ID
1046074
Regression
Yes
Intellisense stops working on new scripts
Windows 10
Unity 2018.2.0b7
Visual Studio 2017
Steps to repro:
1) Open an existing project (that has scripts) in 2018.2.0b7 (on a windows 10 machine)
2) Create a new script and open it in Visual Studio
3) Observe that Intellisense stops working
4) Note that Intellisense is fine when opening existing scripts
Intellisense only starts working after restarting Unity and Visual Studio
Also reported here: https://developercommunity.visualstudio.com/content/problem/130597/unity-intellisense-not-working-after-creating-new-1.html
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment