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
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
Add comment