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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment