Recently, can’t pin-point exactly when it became so bad, the time it takes to click on a script in Unity and have that script become editable in MonoDevelop is upwards of 5 minutes… yes that is not an exaggeration.
I click the script, MonoDevelop start to open, the MacBook fan kicks in, things churn for a good 5 minutes… finally everything settles down and I can work with the script.
Anyone else see this behavior? Is there some configuration or something I can tweak to fix this… it’s practically un-usable as is.
I’m working on a relatively new MacBook (8 gig ram) so I don’t thing that is the issue.
I find the startup time is excessive, but that’s relative…it’s about 15 seconds here, whereas, say, Photoshop takes maybe 10 seconds (and Unity takes a few seconds).
Got the same problems. On my iMac it needs 5 long minutes to startup before I can type in the first lines of code.
Don’t know why this takes so long. I only know, the more files I gather up, the longer the startup and if I add a new file, while MonoDevelop is opened it scans in the new file and takes another 5 minutes!!
But for me this feels like an eternity…
That’s why I recently changed to Sublime Text, which isn’t perfect either, especially to Unity, but still far better than MonoDevelop.
At least I can code without any more worrying about startup and rescan issues. I fell in love with the awesome speed of sublime text. Just missing top level code completion and debugging
Only if I need debugging (meaning Debug.log doesn’t help me anymore or takes longer to find the error),
I still use MonoDevelop, but it’s unbearable.
Tried UnIde too, but it’s still too incomplete for my opinion. (Many missing features. Simple features!)
I’m waiting for updates, but at the moment the developer doesn’t reply in his thread.
Hope he brings another updates soon. For quick lookup on the debug stack it’s convenient.
