are there patches to that thing?
I click on a tab, I get an internal error then after a few clicks, it crashes which is a problem because if unity was paused by a break point, it’s frozen forever and must be put out of its misery
are there patches to that thing?
I click on a tab, I get an internal error then after a few clicks, it crashes which is a problem because if unity was paused by a break point, it’s frozen forever and must be put out of its misery
Glad to see the feature in the title is cross platform! ![]()
It’s working fine for me in Win7 x64 so far. Are you using the version included with Unity 3.0, or have you installed your own? Could you post details on what the unhandled exception error actually is?
It is the unity version of mono and I installed mono 2.6.4
Unfortunately as you can see on the capture, the error message doesn’t provide any information, it’s the typical “unknown exception”. What I know is that it happens a lot when I close tabs … oh and I just tested ONLY WHEN UNITY IS RUNNING IN DEBUG
There is a “+ details” button on that error message. Does it contain any useful information, assuming this isn’t a know issue already?
BINGO!
it was as simple as launching unity in debug mode and playing with the tabs in MD

There’s a few threads about this issue:
http://forum.unity3d.com/threads/52848-Solved-Debugging-with-Unity3-on-Windows
http://forum.unity3d.com/threads/54631-Iinstalling-Mono-Develop-that-comes-with-Unity3-Beta
http://forum.unity3d.com/threads/54161-MonoDevelop-Requests
installed 3.1 and still crashing
i get A LOT of crashes with mono develop, not debuging just coding and using the interface, so i returned to using visual studio…
i seem to experience the same kind of crashes with mono develop on OSX(10.5.8) too…
im using the one included with unity, but i have tried mono develop before and always has been a piece of crap.
the way monodevelop behaves is one strong point on why i dev on windows and use osx only for testing