Search Issue Tracker
Won't Fix
Votes
3
Found in [Package]
1.2.3
Issue ID
VSC-19
Regression
Yes
Visual Studio Code throws an error when double-clicking on Unity Console window debug messages
Reproduction steps:
1. Set Visual Studio Code as the External Script Editor: Unity > Preferences > External Tools > External Script Editor
2. Open the attached project "ConsoleBug.zip"
3. Click Play
4. In the Console window, double-click on the Debug.Log message:
"Testing the console in Unity 2019.4.23f1
UnityEngine.Debug: Log (object)"
Expected result: Visual Studio Code opens the script, that called the Debug.Log method
Actual result: Visual Studio Code throws an error "Path does not exist"
Reproducible with: 1.2.3 (2019.4.21f1, 2019.4.24f1)
Not reproducible with: 1.2.3 (2019.4.20f1, 2020.1.0a1, 2020.3.4f1, 2021.1.3f1, 2021.2.0a13)
Can't test with: 2018.4.34f1 (No VS Code package)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
There are no fixes planned for this Bug