Search Issue Tracker
Won't Fix
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
- [Linux] "Trying to load color backbuffer into a complex RenderPass setup" error is thrown after entering Play mode in AR Mobile template project
- [Android] Neither of the callbacks are called when several videos with VideoPlayer are spawned on the target on the Google Pixel devices
- Texture2D memory allocation size is significantly increased when running on iOS device
- No data received in Profiler when connecting to WebGL Player without "Autoconnect Profiler" option enabled
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
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.