Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.11
Issue ID
1163314
Regression
Yes
Clickable Stack Trace Links in the Console window do not open Visual Studio Editor
How to reproduce:
1. Open the attached project named Case_1163314
2. Play the Scene
3. Click "Start..." message in the console
4. Click "Assets/Scenes/Test1.cs:10" text
Expected result: Visual Studio editor opens and highlights the line of code
Actual result: Visual Studio editor does not open
Reproducible with: 2019.3.0a1, 2019.3.0a6
Not reproducible with: 2017.4.29f1, 2018.4.2f1, 2019.1.7f1, 2019.2.0b6
Reproducible with package versions: 1.0.2, 1.0.5, 1.0.9, 1.0.10, 1.0.11
Notes:
While testing 2019.3.0a1 and package version 1.0.9 two errors were thrown after clicking on the stack trace
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note:
The issue is no longer reproducible with the following Unity versions - 2020.1.0a1, 2019.3.0b1 and 2019.2.3f1