Just wondering when/if whoever “officially” owns the vscode-unity-debug package was going to correct the dependency… :). It seems they tried and failed… based on the comment above from @Incode ?
Is there an ETA when this is truly going to be fixed?
Perhaps a relevant aside: I’ve found VS code has become extremely slow at updating my references, since this package has been broken. It now takes about 20 mins after first launch of VS until I can things like “Find All References”.
@Domas_L Could you look into the Unity Debugger for VS Code being broken? Is my work around still needed in this case, or do we need to fully clean out the .csproj and .sln files after updating the extension or something?
Edit: I’m a dirty liar and everything is broken and sad still. For some reason this worked with an older project but creating a new project caused autocomplete to no longer work.
I updated to the latest unity extension (2.7.3) and it seems to be working for me, I have the debugger working as well as autocomplete and suggestions. Remember to update your C# plugin as well, I’m on 1.21.14. For a while I was on 1.21.12 and I had to manually uninstall that.
Also vs code 1.43.0
What package version do you have installed in the package manager?
hmm, after visual studio code updated itself to 1.43.0, i also can no longer work with my unity project correctly. i tried both 1.21.12 and 12.21.14 and still visual studio code can no longer understand unity classes, or autocomplete, or go to definitions.
this message is in the c# output window of visual studio code when it opens:
Failed to spawn ‘dotnet --info’
yay, visual studio code fucked itself when it updated itself to 1.43.0. i will try reinstalling an older version- and disable auto updates if it does work.
a combination of rolling back visual studio code to 1.42.1 and c# to 1.21.12 got my autocomplete and go to definition functionality working again. autoupdates are now disabled for everything. fuck that shit, it just causes headaches.
Edit: I’m a dirty liar and everything is broken and sad still. For some reason this worked with an older project but creating a new project caused autocomplete to no longer work.
Sorry I missed this, I assume you mean the visual studio code package manager?
Not sure what I’m doing differently but I have autocomplete working.
Oh… I am on Visual Studio Code Editor 1.13 in unity because 1.1.4 had problems described here: https://discussions.unity.com/t/771880
Yeah, i thought maybe it had something to do with the VS Code Editor and that you had 1.20 installed, I tried updating to that, but still no luck. Not sure what the problem is.
This has been driving me crazy. So glad for this PSA. It seems that most IDE’s right now aren’t jiving with my project nowadays. It’s super weird. Over a year and a half in production and all the sudden. Hope this fixes it!
I couldn’t find any active cases about this issue - could you please fill a bug report with repro steps and a minimal repro project and send it to us?
I’m having the exact same issue. I can hear my laptop’s fan spinning up like crazy for at least 20 mins until I have (very slow) access to intelli sense/go to definition etc. Has rolling back to the V1.21.12 C# extension improved your situation?
@SoxwareInteractive I’m on 1.21.12 … references, go to, etc… all extremely slow to populate. Once populated it seems to work fine. Overall very frustrating that our tools are not working.
Thanks for jumping in here, are you saying the reference issue doesn’t break everyone? How is that possible?
I started a new project and started running in to the same issues again. Rolling back to C# version 1.21.12 and Unity debugger 2.7.2 of course fixed it. I’m going to go back to edit my posts to say that it’s still broken, not sure why it worked with my previous project though… I’m guessing there’s something cached that’s allowing it to work.
A bunch of coworkers are reporting that the latest C# extension completely locks up vs code when attempting to auto complete text. What fun!
There are instructions on how to fix the issue:
It seems that the fix has been already merged, and the issue should be fixed soon:
Was this supposed to be a complete fix? I’ve regained Omnisharp/autocomplete, but still can’t debug. Unity freezes up as soon as the debugger is attached (OSX)
The fix has been merged but doesn’t seem to fix the issue. Most folks in this thread have used the instructions in your first link to get to a working state.
After the fix it works for a while and then it stops working… Not sure what is causing this but I see that the plugin “Debugger for Unity” requires the latest version of the plugin and loads it. I end up with two versions installed.
So it’s not a fix :|.
@Domas_L Can you help us out here? TIA!
Others are reporting that this may be fixed with the latest VS Code extensions Unity Debugger (2.7.5) and C# (1.21.15 which is currently pre-release). I’ll update my original post once the extension is officially released and I can confirm that it’s fixed.
If you want the pre-release .VSIX you can get it here: Release v1.21.15 · dotnet/vscode-csharp · GitHub