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

That's really good news! And thanks for the follow-up!

 

When I try to add an exception breakpoint, I get the error:
command 'exceptions.addEntry' not found

VSCode 1.24.0
Debugger for Unity 2.6.0
macOS 10.13.6

 

oh, okay, that's a little weird, but that did seem to fix it. but now I seem to have gotten myself into a situation where the debugger no longer stops on any breakpoints.

I don't, at the moment, have any exception breakpoints set. It's just normal line number breakpoints, like worked in previous versions. But the debugger just blows right past them. Neither restarting VSCode nor Unity gets it working again.

Not to mention, I haven't even got the exception breakpoints to work. With the basic System.Exception breakpoint set, I'm unable to start the debugger before launching my game in the Editor, as I usually do. If I try that, it will pause on all sorts of Unity exceptions and show "source file not found" files, never actually making it to my own code before I give up.

Also, quite a few "Debug adapter process has terminated unexpectedly" errors. Which usually ends up with Unity locked up, so I have to force-quit it & relaunch. Over and over again.

 

miniwolf_unity: First thanks for a new addon for unity. I downloaded and installed this debugger for vscode and unity.


#1. But when I go to the vscode extensions panel and look at the changelog for within vscode it says that the last change was up to version 1.3.1 I say is the most recent version. Is the vxix file that you posted even more recent?

#2 could you go over the actual process of debugging within unity. What I mean is do you press play in the unity editor first, then open the script in vscode then start the debugger OR do you start the unity editor,open the script in vscode, set breakpoints, the go back to the unity editor and press play??
Sometimes I get confused on the order that things should be done, and unity locks up. I have to ctrl-alt-delete and shut down unity and vscode and restart from the beginning.

#3 Sometimes when you are in debug mode and step thru code when you are suppose to supply input in unity, I go to the unity editor and press the designated input key and nothing happens in either unity or the debugger. Is that normal?

#4 Can you make a video screen cast of using the debugger in unity, I can find lots of videos about using the Visual Studio debugger<not code> or general use of the vscode debugger(json files,python files, c# file e.t.c) but nothing specific to vscode and unity debugging.

Thanks

PS.

#5 One more thing. When I do get the debugger running with these two scripts:

https://drive.google.com/open?id=1_5BJ0xKfs9J-AAvP8s2s7ZNlnXESUgiM

https://drive.google.com/open?id=140tZi6BGcFGiAWasfWUU4srqDZlFKHyZ

and this project:

.https://drive.google.com/open?id=1iSPudHqcHLHq_Cs7cDHRTktsljbgTBUJ

I get the debugger to stop at the appropriate breakpoint but in the variables portion of the debugger explorer I get all kinds of orange text showing unity internal variables, I am only interested in the variables that I use in my script. Is there anyway of turning that other stuff off?

I hope that this rambling post makes sense to someone.

Thanks again.

 

thanks miniwolf_unity. I have version 2.somthing running very well now and it is really usefule. As I said, the only real problem is unity locking up sometime. But I think that is because I do not really know how to use the debugger well. And the internal variables being displayed. It is a real pain having to scroll thor all the variable list just to see the one that I want to track.

 

For anyone who finds this thread because breakpoints stopped working sporadically - a (working) interim solution is to toggle specific breakpoints off and back on after starting your debug session. Unfortunate but works..

 

I get the following error when trying to debug
https://imgur.com/a/bfJBBrT

 

Yes the Unity editor is running. My game is not running though (I'm assuming that's the correct way to do it)

I'm on Windows if that helps at all

 

This is the only thing that allows me to debug. It fails to stop on breakpoints almost always if I just run the debugger and then hit play in Unity. [Unity 2018.1.2f1, Debugger For Unity 2.6.3, same on both Windows and OSX]

 

Hello,

custom breakpoints (expression evaluation, logs and hit counts) don't work properly. They all work like usual breakpoints, am I missing something?

 

Oh, I just checked you can have expression evaluation and log points at the same time. If there is only a conditional breakpoints it works correctly.

Logpoints and hit counts don't work. Breakpoint is marked with an exclamation mark and tooltip says Logpoints not suported by this debug type.

Thanks for your help.

 

@miniwolf_unity hi, sorry for the late reply. I set up a test project from scratch to see if I can repro the problem, but it seems to work fine in that. The project I'm working on has been upgraded through multiple versions of Unity, and started out as a .Net 3.5 project. Could there be some issue with my Unity or VSCode set up?

 

Hi, I updated to the latest (2.6.4) and it seems to be much more stable for me now. Thanks for your hard work!

 

I'm using Unity2018.1.5f1 andVisual Studio Community 2017 for Mac Version 7.6.3 (build 1)

Every time I attach the debugger it with Unity process and play unity project, it gives me a popup saying Debugger runtime is not responding. You can wait for it to recover, or stop debugging.

Apparently I've tried all solutions from the internet, from this thread but nothing is working. Any help will be highly appreciated.

Pls see the attached screenshot as well.

 

Anything blocking this from being released on vscode store? It's still 1.3.0 there.

 

Digging up an old thread.

Linux editor: I just installed the debugger for Unity from the marketplace and I get this error message:

Code (CSharp):

1. Cannot activate the 'Debugger for Unity' extension because it depends on an unknown 'ms-vscode.csharp' extension .

What must I do?

Edit: I downgraded to version 1.3.0 and the message disappeared.

 

Thank you.

Now, please, could you do me a favour and answer this question I asked some time ago? https://forum.unity.com/threads/can...roperly-with-unity.538224/page-2#post-5539960 Thanks again.

 

For Unity 2018, it seems that the last working "Debugger for Unity" version is 2.7.5
Three months I have tried everything I could think of. No matter what I try, it doesn't work for me with the newer "Debugger for Unity 3.0.2".

 

I'm trying to set up the debugger and I can't seem to make it work. It doesn't stop at the breakpoints when I run the game, and doesn't show any variables...

My debug console says that it's attached to unity editor but whenever i play the game, it won't do anything of my breakpoints...

I'm using v2018.4.31 of Unity and v3.02 of Debugger for Unity

Any idea why?

 

Well now it stops to the first breakpoint, but I can't step over, step into, or step out...?

If someone knows why this could be happening, I'll be more than happy to hear your solution

edit : also my breakpoint icon isn't yellow or highlighted, even though my game stops at the right breakpoint. It's still a red circle. Not highlighted like in this video at 4:25 :