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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment