So I upgraded to Unity 3.4.2 ( OSX Snow Leopard ). I can no longer get the debugger to attach to Unity.
The only version of Monodevelop I’ve ever had installed is the one from Unity. Unity’s preferences have the external script editor set to “Use built-in editor (Monodevelop)”. I’ve launched monodevelop from Unity by double clicking on a script file and it loads my project into MD.
Firewall is turned off.
I’ve restarted Unity and Monodevelop at least a dozen times now and rebooted. Nothing… same thing. I attached a screenshot. Needless to say, this is a problem. Anyone have any ideas?
I also recently installed 3.4.2, and I’m receiving the same message.
My system is running Snow Leopard, and rebooting hasn’t solved the issue. I haven’t attempted to change any system settings, such as the firewall, since the debugger was working with the previous Unity release.
It seems run on Windows.
EDIT:
I downgraded to 3.4.1 on Mac, and I’m now able to debug again.
Using Mac OS 10.7.2, with Unity 3.4.2f2 with MonoDevelop 2.4.2 and am getting the same error. Firewall off, used Sync MonoDevelop Project to open up MD.
System.Net.Sockets.SocketException: Connection refused
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint remoteEP) [0x00000] in <filename unknown>:0
at Mono.Debugger.Soft.VirtualMachineManager.ConnectInternal (System.Net.Sockets.Socket dbg_sock, System.Net.Sockets.Socket con_sock, System.Net.IPEndPoint dbg_ep, System.Net.IPEndPoint con_ep) [0x00000] in <filename unknown>:0
Well, I just found a workaround. Normally I run with Monodevelop open and Unity open. Write code in monodevelop, click on unity to compile. Run the game in unity, and if I need to debug something, in monodevelop I do Main Menu > Run > Attach to Process… > Unity Editor
That’s how I get “Connection Refused”. On a whim, I just ran Main Menu > Run > Debug which starts a new instance of Unity ( not efficient! ). That actually works - except, when you try to stop debugging, Monodevelop stays in “debug mode”, hangs when you try to exit and the Unity instance started keeps on running. I did have to delete the Mixamo Store plugin as that didn’t seem to be compatible running that way, but that’s not a big deal as I don’t use that anyway.
I really need the ‘Attach to Process…’ working again as this is a major dent in my productivity workflow.
It is the weekend so hopefully tomorrow someone from Unity will see this thread. Additionally, I filed a bug report.
+1 and thanks for the workaround. Found that one yesterday for myself, but it just kills productivity.
Did anyone submit a bugreport to the folks at Unity on this?
I haven’t tried reverting yet, but possibly will try that. I submitted a bug report as well a few days ago. Given the seriousness of this bug (a showstopper), I’m distressed at the lack of IMMEDIATE response from Unity. They must be buried with 3.5 development, but the CEO oughta yank the engineers onto this problem ASAP. This should have been fixed by now. Totally unacceptable.
