Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
Votes
0
Found in [Package]
2.0.5
Issue ID
VS-28
Regression
Yes
Can't attach Unity debugger to Visual Studio on a Virtual Machine
How to reproduce:
1. Create a Virtual Machine
2. Open Unity and add any script to any GameObject
3. Open that script with Visual Studio
4. Select "Attach Unity Debugger"
Expected results: Unity Debugger is attached
Actual results: No Unity Client is found
Reproducible with: 2020.2.0b14, 2021.1.0a9
Not reproducible with: 2018.4.30f1, 2019.4.16f1, 2020.1.17f1
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
- Empty scrollable space appears and scrollbar shrinks when scrolling down in the Tile Palette Brush Picks overlay window and List View selected with many saved brushes
- PhysicsCore2D Renderer should ensure it only renders to a base camera in URP.
- Player GameObject can’t be selected in the Hierarchy window during Step 4 of the "Get Started" tutorial in 2D Platformer Microgame because Hierarchy window is masked
- Gradient marker colors are removed when undoing marker movement in the Inspector Gradient field
- Crash on RendererScene::NotifyInvisible when GameObjects are deleted from the Hierarchy in a specific Scene
Resolution Note:
Sorry for the late response to this issue. The issue shows that the Visual Studio Tools for Unity is not correctly installed in Visual Studio (e.g project incompatible when loading). Microsoft has tested this without being able to reproduce it so we are closing as unable to reproduce. We recommend to report the issue directly to Microsoft if you still have the issue. Thank you.
Resolution Note (2.0.X):
Sorry for the late response to this issue. The issue shows that the Visual Studio Tools for Unity is not correctly installed in Visual Studio (e.g project incompatible when loading). Microsoft has tested this without being able to reproduce it so we are closing as unable to reproduce. We recommend to report the issue directly to Microsoft if you still have the issue. Thank you.