I have a big problem when it comes to debugging unity projects. When I start MonoDevelop run debugging there, it starts unity and the debugging works - but only once. If however I wish to debug again I have to close the recently MD opened unity and start again. This is a pain in the butt, and if I have read correctly there is no bug here tho.
BUT when I read the possibility to attach the debugger while unity is running, I thought that this would do fine, however I am unable to make it work. When I have unity running, open the MD from unity and try to attach the debugger (MD sees two unity processes - I guess this is normal?) it always complains that connection was refused on 127.0.0.1.
I tried to disable the windows firewall with no luck.
I am running Unity 3.4, using C# in unity, Windows 7 Ultimate x64, and Mono Develop that comes with unity.
My game is really procedural/dynamic and if I cannot debug the app(I am a developer in work life, cannot live without debugger and printing thousands of vertex arrays just doesn’t suit me) I’m afraid I must look other solutions because while Unity is a great package, this is a deal breaker for me.
Well first I dont get the point of using the debugger if you dont se anything is wrong.
Also you can easy use a print statment in the code where you want to check.
The debugger in unity do sucks big time for you cant say what it shall look for and sometimes it just print alot of nonsene warnings.
I always find it better in all development tool I used to use your own way to debug and I havent found anything that better then put a debug “print” where I want to look for error och to make sure its right.
Well I have a bug in my code that is somewhat odd and needs a debugger to solve it quickly.
The printing is ok for small things, but if I - for example - want to pause the game and inspect the states in my script a debugger is a must (the inspector does not cut it).
And adding a print to the code needs one to stop the run time, edit the code, compile the code, start the program and seek the correct print in the console. With debugger it’s just a matter of adding a break point.
But seriously, does anyone have any suggestion what do try to make the attaching work?
do not hit the stop button…this will disconnect your debugging session…same thing happen to me…
if you do not hit stop…you can debug as much as you want…
I have worked a partial solution (don’t know if these were the steps that actually helped).
I ran Unity with Administrator privileges - this helped the MD actually to see one unity instance and attach itself to it. However almost every time I attached the debugger and pressed the “start” button from unity it crashed.
I ran the project from a drop box folder - Unity certainly don’t like it, moving the project to other location helped to solve the crashing.
After those those changes the monodevelop could attach itself without any noticeable problems, it remains to be seen if this works tomorrow.
I am beginning to think that neither of those actually helped anything - could be just that when I rebooted the machine the debugger attaching began to work. It is still unstable as hell - crash occurring about 1 in 5 debugging attempts. THIS SHOULD BE FIXED!