Search Issue Tracker
Active
Under Consideration for 2.0.X
Votes
0
Found in [Package]
2.0.11
Issue ID
VS-78
Regression
No
Intellisense is not detecting Unity-specific suggestions when a script is part of an Assembly
How to reproduce:
1. Open the user-attached “TestAssemblySwitch.zip” Project
2. Open the “PlayerController.cs” Script found in the Assets/Scripts/InputSystem folder
3. Attempt to write awake/start/update functions in the Script
4. Wait for the Intellisense suggestions to appear
Expected result: Intellisense Unity suggestions window appears
Actual result: Intellisense suggestions appear but without Unity-specific suggestions
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a7
Reproduced on: macOS Ventura 13.5 (Intel), Windows 11 (User reported)
Not reproduced on: No other environment tested
Notes:
- Issue might be highly inconsistent to reproduce, first-time testing was not reproducible
- Couldn’t reproduce on a new project
- Reproducible with Visual Studio 2022
- Not reproducible with Visual Studio Code
- Couldn’t find under what condition the issue starts reproducing
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Compiled Shader code has self-assignments and redundant code in the Shaders that use "enable_d3d11_debug_symbols"
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
Add comment