Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.2f2
Issue ID
1066315
Regression
No
Workspace settings are not saved when using Visual Studio Code in Unity
1. Create a new project
2. Go to Edit -> Preferences -> External Tools and change "External Script Editor" to "Visual Studio Code"
3. Create two new scripts
4. Open them both with VSCode editor in Unity (they should remain on the tabs of VSCode editor)
5. Close VSCode Editor and reopen one of the scripts
Expected result: when closing VScode editor in Unity, the opened scripts remains on the tabs of VSCode editor
Actual result: closing VSCode editor and attempting to open a script via the Unity project folder will open a new workspace.
Reproducible with: 2017.4.14f1, 2018.1.9f2, 2018.2.14f1, 2018.3.0b8, 2019.1.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Add comment