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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment