Unity Debugger Extension for Visual Studio Code 3.x Preview Release

I've installed this and logpoints are very cool
I've noticed that editing logpoints during one session is ignored and opened an issue on github
Deleting and adding new ones during the session seems to work correctly

 

Hello, just wondering if development on this extension is still active. 3.0.1 has been a good improvement, but the VsCode debugger is still quite unreliable and is would greatly benefit from additional development. At the very least, I think it would be a good idea to release version 3.0.1 on the extension marketplace so that the majority of VsCode users could benefit from the improvements, unless there have been some regressions that others have run into.

 

hi! What about debug when multiple instances of Unity are open?

 

@miniwolf_unity just to confirm, are we supposed to be able to debug using Mac VSCode attaching to an IL2CPP iOS build? The current v2.x and this new v3.0.1 connect and then a few seconds later disconnect. We can attach to the Editor and debug fine.

VSCode output;
UnityDebug: Initializing
UnityDebug: Searching for Unity process 'iOS Player'
UnityDebug: Attached to Unity process 'iPhonePlayer(XXX-iPhone-5S):56000' (130992214)
UnityDebug: Disconnected

https://github.com/Unity-Technologies/vscode-unity-debug/issues/130

I also tried Visual Studio for Mac and got errors similar to issues like:
https://github.com/Unity-Technologies/vscode-unity-debug/issues/103 ("Operation is not valid due to the current state of the object").

We've updated / uninstalled / reinstalled stuff, checked firewalls, disabled cellular connections, etc. as suggested in a few of your posts and github issues.

 

I've never been able to get the debugger to connect to any of the Players. Seems even Visual Studio cannot find the players when using 'attach to process', none of the players are listed. Here's the log, logcat screen shot attached. Using unity debugger 3.0.1:

`
12:21:25.393823: Log
---

12:21:25.433330: UnityDebug
12:21:25.436785: Running session
12:21:25.460713: Constructing UnityDebugSession
12:21:25.473188: Done constructing UnityDebugSession
12:21:25.749315: Command: initialize: {
"clientID": "vscode",
"clientName": "Visual Studio Code",
"adapterID": "unity",
"pathFormat": "path",
"linesStartAt1": true,
"columnsStartAt1": true,
"supportsVariableType": true,
"supportsVariablePaging": true,
"supportsRunInTerminalRequest": true,
"locale": "en-us"
}
12:21:25.834326: Command: attach: {
"name": "Android Player",
"type": "unity",
"request": "attach",
"__exceptionOptions": [
{
"path": [
{
"names": [
"System.Exception"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.SystemException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.ArithmeticException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.ArrayTypeMismatchException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.DivideByZeroException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.IndexOutOfRangeException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.InvalidCastException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.NullReferenceException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.OutOfMemoryException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.OverflowException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.StackOverflowException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.TypeInitializationException"
]
}
],
"breakMode": "never"
}
],
"__sessionId": "4f8c79d2-d427-4c99-814f-6e5980a932f2"
}
12:21:25.837248: UnityDebug: Attach: VSCodeDebug.Response ; {
"name": "Android Player",
"type": "unity",
"request": "attach",
"__exceptionOptions": [
{
"path": [
{
"names": [
"System.Exception"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.SystemException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.ArithmeticException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.ArrayTypeMismatchException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.DivideByZeroException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.IndexOutOfRangeException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.InvalidCastException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.NullReferenceException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.OutOfMemoryException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.OverflowException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.StackOverflowException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.TypeInitializationException"
]
}
],
"breakMode": "never"
}
],
"__sessionId": "4f8c79d2-d427-4c99-814f-6e5980a932f2"
}
12:21:25.858207: UnityDebug: SetExceptionBreakpoints: [
{
"path": [
{
"names": [
"System.Exception"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.SystemException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.ArithmeticException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.ArrayTypeMismatchException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.DivideByZeroException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.IndexOutOfRangeException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.InvalidCastException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.NullReferenceException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.OutOfMemoryException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.OverflowException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.StackOverflowException"
]
}
],
"breakMode": "never"
},
{
"path": [
{
"names": [
"System.TypeInitializationException"
]
}
],
"breakMode": "never"
}
]
12:21:25.884553: UnityDebug: Searching for Unity process 'Android Player'
12:21:25.888105: Trying to find all Players
12:21:25.940018: Setting up multicast option: 225.0.0.222: 54997
12:21:25.940351: Setting up multicast option: 225.0.0.222: 34997
12:21:25.940525: Setting up multicast option: 225.0.0.222: 57997
12:21:25.940657: Setting up multicast option: 225.0.0.222: 58997
12:21:25.940875: Setting up multicast option: 225.0.0.222: 54997
12:21:25.941044: Setting up multicast option: 225.0.0.222: 34997
12:21:25.941204: Setting up multicast option: 225.0.0.222: 57997
12:21:25.941374: Setting up multicast option: 225.0.0.222: 58997
12:21:25.942224: UnityPlayerConnection is constructed
12:21:25.944791: Known size of available Players: 0
12:21:28.952360: New size of available Players: 0
12:21:28.956093: Error while initializing usbmuxd
12:21:28.956644: Could not find the correct process name: Android Player
12:21:28.956757: These are the one that could be found:
12:21:28.970717: Unity Editor process: Unity on id: 30910
12:21:28.973756: UnityPlayerConnection is constructed
12:21:28.973904: Known size of available Players: 0
12:21:31.979831: New size of available Players: 0
12:21:31.980242: Unity Editor (Unity) : 30910
12:21:31.980483: Could not find target name 'Android Player'.
12:21:31.999718: Command: setBreakpoints: {
"source": {
"name": "Console.cs",
"path": "/Users/byronwright/Projects/viperflypinball2d/Assets/Console/Console.cs"
},
"lines": [
437
],
"breakpoints": [
{
"line": 437
}
],
"sourceModified": false
}
12:21:32.027426: Command: setBreakpoints: {
"source": {
"name": "Game.cs",
"path": "/Users/byronwright/Projects/viperflypinball2d/Assets/Scripts/Main/Game.cs"
},
"lines": [
777
],
"breakpoints": [
{
"line": 777
}
],
"sourceModified": false
}
12:21:32.028130: Command: disconnect: {
"restart": false
}
12:21:32.029389: UnityDebug: Disconnect: {
"restart": false
}
12:21:32.029629: UnityDebug: Disconnect: VSCodeDebug.Response
`

 

@miniwolf_unity : Why isn't debugger 3.x available via VS Code's extensions updates? Most recent version it detects is 2.7.5

 

hey @miniwolf_unity, do you mean your update effort is not a Unity priority, or more broadly that providing a debugger for VSCode is not a Unity priority? I know that your extension is officially unsupported but do you have any idea of how many Unity devs are using VSCode? All except one of our team use it and having working tools (Unity VSCode package, VSCode Unity debugger extension) is obviously really handy. Thanks for your efforts keeping the debugger working!

 

@miniwolf_unity thanks very much for your reply - much appreciated. Yeah, I usually skim the marketplace stats when upgrading VSCode extensions so it's certainly being installed 'a lot' but no idea of the proportion vs. Visual Studio and Rider etc. It's frustrating that Unity aren't treating it like a first-class citizen but the VSCode team are acting like it is in the wider .Net world.

For us on macOS the tools and components seem to change every few days and stuff breaks all the time. I'm often chasing github issues and installing pre-release extensions for Omnisharp or backing out versions of VSCode or finding manual installs of the debugger or downloading .Net developer sdk installers to make them all happy again for another week or two. It's quite an effort keeping everything talking... and your efforts with the debugger are very appreciated.

My current versions: VSCode 1.43.2, Omnisharp 1.21.15, Unity Debugger 2.7.5 and Mono 6.6.0.155 - seem to talk ok after a patchy last few weeks.

VSCode is useful for us because the setup is light and can be the same across Editor platforms, rather than full Visual Studio on Win vs Visual Studio on macOS and everything those full IDE's require. We have not tried Rider but I expect it would be the same across platforms too.

 

That's very disappointing and surprising. Please push for more resources. Half a million marketplace installs is substantial.

Even large organizations like Facebook are using VS Code now (not necessarily with Unity, but the point is the IDE is gaining even more traction). Source: https://www.zdnet.com/article/faceb...code-is-now-our-default-development-platform/

Or maybe... I don't know, just focus on non-breaking changes?
https://github.com/Unity-Technologies/vscode-unity-debug/issues/166

Honestly, MonoDevelop sucks, and VS Community is too bloated. VS Code has been perfect, (until recent breakage).

PS: Can I request that your changelog list release dates?

 

MonoDevelop has been deprecated for years.

Xamarin Studio, which it was a fork of, is now named Visual Studio For Mac, because Catbert is in charge of naming things at Microsoft.

 

I wonder who still uses msvs... my colleagues all use vs code.
Come on guys, somebody M$ or Unity, support @miniwolf_unity to release the extension, it's not like it's some common useful extension, it's The Extension.

EDIT:
I've read on some forums and expected this custom version to work with static variables (singletons). It doesn't... oh well...
And please guys don't start a holy war on statics and singletons... it's basic C#, not a C-like language that's been supported by Unity.

 

The issue is reported here and I've also seen you mentioned here

The issue manifests like this: when debugging and hovering over PlatformManager in PlatformManager.Instance.current it reads "Evaluate request failed (Unknown identifier: PlatformManager)"

 

Thank you. It still shows the Evaluate request failed error.

 

With Reo.PlatformManager.Instance.current
it now says "Evaluate request failed (Unknown identifier: Reo)" where Reo is the namespace.

 

It looks like this version is still pointing to the old c# library name

 

More info:
With or without namespace qualifier step-in works fine on PlatformManager.Instance.GoToPlatform().
Also Instance.current (in PlatformManager.cs script) works as expected, shows proper details.

 

Should I consider this semi abandonware for now and shelf the idea of using VSCode as my daily driver for now?
I'm loving everything about VSCode, but something like

Code (CSharp):

1. [System.Serializable]
2. class car{ int price = 20; }
3.  
4. List<Car> cars = new List<Car<();   // then populate it
5.  
6. blah = cars[ i ].price;

I can hover over 'blah', 'cars' and 'i' fine, but 'price' or the serializable class is a no-go with the "Evaluate request failed" business as usual. (Works in e.g. rider, vs, etc for reference).

Thanks!

 

I can confirm for you that all works normally [for me] with the following versions:

- C# extension 1.21.18
- Debugger for Unity 2.7.5
- Visual Code 1.43.2 (there are updates but I keep clicking "later")

 

And now... for whatever reason, debugging does NOT work. All the same versions of software and extensions I listed previously.

Any news @miniwolf_unity ? Unity is doing an IPO. You should push to get a stable budget for this.

 

I realized Visual Code is too young. Using Visual Studio 2019 for the time being.

 

Update:
I've updated to:
Unitu 2018.4.27f1
VSCode 1.49.3
C# 1.23.2
Debugger for Unity extension 2.7.5

I can debug! I can see var and object values when I rollover the mouse cursor. I can step through/over code.

The only weirdness is if I rollover something like StartCoroutine() then I get errors that pop up in VSC and in Unity's Console it shows sound related errors that have nothing to do with my code or project.

eg:
maxVolume is not supported anymore. Use min-, maxDistance and rolloffMode instead.
rolloffFactor is not supported anymore. Use min-, maxDistance and rolloffMode instead.

Those errors do not appear when running my project normally, and only appear if I rollover my mouse cursor on StartCoroutine, or other function calls. I think i can live with this though.

 

Is this extension still being supported?

 

I just filled it out. I hope it encourages more support of VS Code.

 

I recently switched from Windows 10 to Ubuntu 18.04 as a dual boot and have been pleased to see everything running swell including this debugger. I look forward to future releases. Especially those evaluations on things such as static classes and variables.

 

Hey @miniwolf_unity is this extension still being supported? I updated unity to 2019.4.13f1 and have been having several issues getting the debugger to work with this version of Unity.

 

Just saw an official update is available via the extension marketplace. This seems promising!

 

I have 3.0.2 installed from Marketplace and when using Logpoints it says "Breakpoints of this type are not supported by the debugger" . What's wrong?

 

Debugger v.3.0.2 with VS Code v.1.65 does not detect unity 2021.2 instance (when using both launch.json pre-configured entries or using "Unity Attach Debugger") for me on Ubuntu 20.04.

 

UPD: It seems for 2021+ unity editor + Linux combo, extension cannot detect running instance when debug mode for editor is off. (For older versions it was detected and asked to turn debug mode on, afaik).
I found out this when i tried to attach to unity with other extension (Mono Debug) on unity-mono port (56***, last 3 numbers are the same as last 3 of unity editor processs PID). And after this, unity-debugger was also able to detect & attach.

 

What's the status of the Unity Debugger VSCode extension?
It hasn't been updated for two years, and apparently VSCode is planning to mark it as deprecated since you haven't replied to them.
I hope you're aware that this extension is a requirement for anyone developing on Linux (and more and more Windows developers are preferring VSCode over VS), so it could really need some more love from your development teams.

@miniwolf_unity

 

Thanks for the quick answer!
And thanks for the suggestion. I didn't know Rider was in a better state for Unity development on Linux, so I'll try that out. I would still prefer to use VSCode though, since that's what I use for development in general - and I'm definitely not alone about that. So I hope MS will be able to take over the extension then

Have a nice day!

 

hi @xoofx, we've been using VS Code for years on macOS and Windows. It's a real shame to hear that support for the Unity debugger might disappear, making VS Code a somewhat second-class Unity script editor again. Your suggestion of 'use Rider' is fine and I've heard that Rider is great, but obviously there are time and budget costs associated with moving IDEs like this which could affect teams of any size.

Personally, VS Code has become my go-to editor on macOS for nearly everything. If there's a way to keep the Unity support for it alive I'd appreciate it and so would many other devs I know. If this is not possible, then hearing about your plans to deprecate support for it if Microsoft can't help out would be much appreciated.