Double clicking Unity console log does not goto MonoDevelop file and line

Question

Hi guys,

I have a rather irritating issue in Unity (apart from debugger cras$$anonymous$$ng Unity most/all of the time)

When I double click an error or even a Debug.Log in Unity console, it used to open up MonoDevelop and go to that line of the file. But now all of a sudden it opens up that C# file in Sublime Text. I can still use MonoDevelop and select the C# file in MonoDevelop and do all the rest, but not being able to goto file and line is sort of infuriating.

I'm on OSX 10.9.5 with Unity 4.3.4 with MonoDevelop 4.0.1 (build in mono for Unity 4.3.4). Unity preferences 'External script editor' set to 'MonoDevelop (build-in)'

I did however update OSX from 10.9.3 or somet$$anonymous$$ng like that (I can't remember for sure). At the moment I'm t$$anonymous$$nking it's somet$$anonymous$$ng to do with that OSX update. Anyone else experiencing t$$anonymous$$s issue?

Any advice is welcomed. Thanks in advance.

Answer 1

Answer by GameVortex · Oct 16, 2014 at 12:39 PM

Select Monodevelop as the default program in the preferences:

Edit - Preferences - External Tools - External Script Editor

0 Show 3 · Share

$$anonymous$$ · Oct 16, 2014 at 02:05 PM 0

Share

Thats already selected. Sorry if that wasn't clear on my question. That's why I said "Unity preferences 'External script editor' set to 'MonoDevelop (build-in)'"

GameVortex · Oct 16, 2014 at 03:55 PM 0

Share

That is what I get for skimming the text I guess. Sorry about that.

nevilleshane · Nov 27, 2014 at 04:46 PM 0

Share

I had this same error and I manually selected MonoDevelop from the Edit - Preferences - External Tools - External Script Editor path and it fixed it. Even though MonoDevelop(built-in) was selected, when I manually set it up, it fixed the problem.

Answer 2

Answer by $$anonymous$$ · Oct 20, 2014 at 01:14 PM

Answering my own question.

Basically, I couldn't find ANY way to fix t$$anonymous$$s annoying problem and it kept bugging me so far that I HAD to fix it before doing any meaningful work. So t$$anonymous$$s is what I did.

1) I backed up my mac using time mac$$anonymous$$ne. 2) Installed a fresh copy of OSX 10.9.2 3) Migrated all my user and application data using 'Migrating assistant'

T$$anonymous$$s seems to be working for me.

It however broke MonoDevelop and when I double clicked in UnityConsole it would open up MonoDevelop and then immediately closed it. I just changed the permissions by right clicking on Unity folder from finder and set all the permission to 'read and write' and 'Apply to enclosing items' as well.

Hope t$$anonymous$$s helps someone else.

0 Show 1 · Share

Orc_Horn_Productions · Oct 20, 2015 at 10:17 AM 0

Share

I know this isn't an answer or any help after the event but I would seriously recommend moving over to Visual Studio 2015 and forget about monodevelop. I've found that it's more stable and easier to debug with as you seem to get more detailed information.

Answer 3

Answer by Hell raiser · Oct 20, 2015 at 11:59 AM

It work for me:

Export current project to a package
Create new project
Import package from step 1

0 · Share

Double clicking Unity console log does not goto MonoDevelop file and line

3 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions