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
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
Add comment