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
- [Linux] Crash on mono_runtime_invoke when executing a specific script
- Installing the HDRP Water Samples doesn't notify the user to enable the "Water" on HDRP Asset
- Persistent Memory Leak in `ChunkDrawCommandOutput` and `CullingSplits.InitializeSplits`
- 1 KB or more of GC is allocated when Debug logging
- [HDRP][XR][DX12] SSR PBR Accumulation algorithm artifacts are present in one eye when using SPI OpenXR Rendering Mode
Add comment