Search Issue Tracker
Fixed
Votes
5
Found in [Package]
1.1.4
1.2.1
Issue ID
VSC-14
Regression
Yes
IntelliSense doesn't provide its features when editing a Script with Visual Studio Code
How to reproduce:
1. Create a new project
2. Set Visual Studio Code as the Unity Script Editor (Edit -> Preferences -> External tools -> External Script Editor)
3. In the Project window create a new C# Script
4. Open the newly created Script
5. Above the Start method start writing (do not copy-paste) this line of code: 'public GameObject '
Expected result: Visual Studio Code suggests a code completion for the GameObject class name
Actual result: no code completion is suggested
Reproducible with: 1.1.4 (2019.4.0f1), 1.2.1 (2019.4.0f1, 2020.1.0b11, 2020.2.0a14)
Not reproducible with: 1.1.3 (2019.4.0f1)
Workarounds:
1. Regenerating the project files (Edit -> Preferences -> External tools -> Regenerate Project Files)
2. Creating a project with Rider or Visual Studio as the Unity Script Editor and then switching to Visual Studio Code
Notes:
The issue doesn't occur with Rider or Visual Studio
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
Add comment