Debugging: unable to follow variables

Hello,

Using Visual Studio, I launch and test my scripts using "Attach to Unity and play". I ran onto a nell exception error, got the line and the class name on the Unity debug log, but after double clicking on the error on Unity, I am not able to check the values of the variables and objects on Visual Studio. Weirdly, it's working fine when usng bullet points, but it would be really useful when I get errors...
Am I missing something?

Thanks!

 

In Visual Studio the variables are normally only visible in the 'scope' of the function you're looking at. If you hit ctrl-alt-c (I think) to open the call stack window you can select the calling function and view the variables within that.

 

Actually, the problem is that Visual Studio doesn't seem to catch anything unless I use a break point. WHen I double click on the error on Unity, Visual Studios just points to the line on the right script, but doesn't get the error.

 

That's odd, it looks like it's not breaking on exceptions. This looks similar to this bug which was fixed recently so perhaps you need to update Unity? https://feedback.unity3d.com/sugges...tion-when-using-visual-studio-as-the-debugger

 

As far as I can remember, breaking on exceptions is no enabled by default. Look through the debug settings in VS, there should be somewhere you can enter eg. NullReferenceExceptions as something VS breaks on.

 

What you have there is a runtime exception, as far as I know, even in debug mode, visual studio will only display compile time exceptions in the log.
You will have to rely on unity logs for runtime issues.

Also, you're looking at the wrong windows, You should be looking at the Error window, accessible through View->Error List or Output(console).

 

Thanks for the answers! I've found what I need, I am going to play with that.