Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b8
Issue ID
1006866
Regression
No
VSCode can't start debugger when Unity Hub is running
When starting a debug session in VSCode it will try to attach itself to the Unity process. It does this by looking for a process named "Unity Editor". However, when simultaneously running the Unity Hub application it will find multiple such processes and won't start.
Output from VSCode:
UnityDebug: Searching for Unity process 'Unity Editor'
UnityDebug: Multiple targets with name 'Unity Editor' running. Unable to connect
UnityDebug: Found Unity process 'Unity Editor (Unity)' (9033)
UnityDebug: Found Unity process 'Unity Editor (Unity Hub Helper)' (9014)
UnityDebug: Found Unity process 'Unity Editor (Unity Hub Helper)' (8994)
UnityDebug: Found Unity process 'Unity Editor (Unity Hub)' (8993)
Fixed by Unity Debugger extension update.
Version 1.3.0 of the Unity Debugger for VSCode has now been published which fixes this issue:
https://marketplace.visualstudio.com/items?itemName=Unity.unity-debug
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