Search Issue Tracker
Fixed in 2.0.2
Votes
1
Found in [Package]
2020.1.0b8
2020.1.0b10
2020.2.0a8
Issue ID
1249626
Regression
Yes
[Scripting] Intellisense does not work when External script Editor is changed and set back to Visual Studio 2019
When the Default "External script Editor" in the Preferences is changed and set to Visual Studio for mac then Intellisense does not work
Steps to Reproduce:
1. Create a new project.
2. Unity > Prefrances >External Tool > External script Editor > Open by file extention
3. Unity > Prefrances >External Tool > External script Editor > Visual Studio for mac
4. Create C# scripts.
5. Open Script in Visual Studio 2019
6. In Start() start typing UnityEngine specific or type/variable/function (e.g. "Coll...", "game...", "Des...", )
Actual Result:
Intellisense(Auto-completion ) does not work
Expected Result:
Auto-completion should predict the rest of a type/variable/function
Reproducible on:
2020.2.0a12, 2020.2.0a8, 2020.1.0b10, 2020.1.0b8
Working fine on:
2020.2.0a7, 2020.1.0b7 2019.3.15f1
Environment:
Windows 10 and macOS 10.15
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment