Clicking on Debug.Log console output doesn't me to the corresponding source code line

@BroVodo I had the problem with completely newly installed Unity 4.5.x and newly created projects...on Mavericks,

 

Hi guys, I've had the same problem since 4.5 or so, months now. Double clicking will open the file in mono but not go to the line number and will not open the entire solution, just that one CS file. I am on Mavericks, latest Unity and monodevelop. I've tried removing any files related to Unity/monodevelop (prefs, etc..) and reinstalling from scratch, but nothing has worked.

 

I gave up and installed Mountain Lion and Unity on an external firewire drive which I boot from when I want to get some work done. Lately Unity is more concerned in being the Jack of all Trades (supporting every platform under the sun) rather than being the master of anything. And the founders are looking to sell, hmmm....

Since the price has come so far down UE4 is looking better and better

 

script editor they ship with unity on osx has been useless since mavericks came out a year ago. Pretty glaring omission if you ask me! Just use xamarin I guess...

 

read my earlier posts about xamarin editor. I tried it and it was so sluggish.

 

xam is little slower than monodev but at least it works. Whatevs floats ur boat I guess.

 

It wasn't a little slower. It was nearly unusable. Not a ' float ur boat' kind of situation. If it had been usable I would have used it rather than having to boot from an external disk everytime I wanted to do some development.

 

I am so sick of this MonoDevelop problem. When are Unity's engineers going to fix this goddamed issue!​

 

xamarin works fine, albeit overall slightly slower than monodev. It has some issues forgetting the project or whenever you make/delete a new script in unity or quit/re-open unity. This results in it being really really slow - perhaps you are experiencing this?
To fix it just quit xam then in unity go to the assets menu and select "Sync MonoDevelop Project". This will open xam and all the syntax highlighting should appear after a brief delay. This fixes it every time for me.
EDIT: grammar

 

I've also had this problem since 4.5 (from 4.3) on Win8.
Logs on console (normal, warning, error, exception) can't be clicked at runtime, i.e. they don't highlight any code when clicked.
But all logs that comes from editor is clickable & highlights the code properly.

 

Same issue for me. Console messages do not appended with "filename:linenumber" anymore. Hence the double-click on them do nothing. I cant work like this.
Had this issue a week or two ago, and now it came back.

Windows 8.1, Unity 4.5.3 free.

UPD. I setted external editor to mono, disabled "editor attaching option", rebooted pc and problem has gone. But this is very strange.

 

If I was on windows I'd be using visual studio! Wish we had that on mac

 

Same problem here. It used to work fine until a week a go or so.
Not sure what changed but now it's happening 100% of the time, pretty annoying.

Unity 4.5.3f3
Monodevelop 4.0.1
OSX 10.9.4

 

I'm experiencing the issue and get this error (4.6b20):

EditorHelper: Unable to use the internal script editor /Applications/Unity 4.6b20/MonoDevelop.app. Trying the default system editor now.

The file opens in sublime text (default editor). This happens whether MonoDevelop is open or not.

 

yes, it's installed there. I'll try it with 4.5.4p3 as soon it is available.

 

Great! Can't wait for 4.5.4.p2

 

@JoshPeterson thanks for the update! Really looking forward to the script editor issues on OSX being solved!

 

Great! Downloading now. You'll have a log within the hour.

 

Ok, that's what's happening:

EditorHelper: Attempting to open file: /Volumes/Data/Library/Unity/bug reports/test/Assets/Test.cs.
EditorHelper: Attempting to open file (using Apple events): /Volumes/Data/Library/Unity/bug reports/test/test.sln.
EditorHelper: Failed to open file: unable to get process descriptor for /Applications/Unity 4.5/MonoDevelop.app.
EditorHelper: Attempting to open file (using Apple events): /Volumes/Data/Library/Unity/bug reports/test/Assets/Test.cs.
EditorHelper: Failed to open file: unable to get process descriptor for /Applications/Unity 4.5/MonoDevelop.app.
EditorHelper: Unable to use the internal script editor /Applications/Unity 4.5/MonoDevelop.app. Trying the default system editor now.

 

Here are my logs with explanation of what I did:

 

Also here are the diffs between the two Editor.logs: (right side is on Mavericks)

 

Yes, I'm on mavericks.

 

Happy hunting Josh.

 

Hey guys,

having a similar issue, and one that has come up now and again.
It may have already been mentioned, apologies if it has, but didn't pick it up when looking through the other posts.

Moved project from one machine to another, and the project path still points to the old path, rather than the new one. So when double clicking on the console log, it can't find the file.

In the past I've been able to do a re-import all to fix the issue, but it's not helping for this particular project. It always points towards the old path.

The original path was Documents/Game Dev/Local/PROJECT ROOT

The only way I could get to fix this was to remove the spacing in the 'Game Dev' folder name, which is the sensible thing to do. When opening the project, it still pointed to the old path, but then a quick reimport fixed it.

Apologies if something like this was already mentioned, but just wanted to give my update on a similar issue.

 

There are no spaces in my project path.

 

It was unlikely that it would be the exact same thing for you. As far as I understand it, you're having it with new projects, too? As ever with this sort of thing, it's rarely because of one specific thing.

Does the debug log show the path to the file and line number? When I was having issues it would show the full path, rather than a project relative path (Assets/Scripts/) as it does when it's working fine...

 

script-editor issues appear to be resolved on OS X Yosemite with the latest unity patch 4.5.5p1. Thank you Unity!

 

Interestingly, after installing Yosemite today, the bug doesn't occur anymore in 4.6 (which doesn't include the fix yet)...

 

Hey everybody. Thanks to Josh this problem is finally fixed. Monodevelop now works perfectly with Unity on Mavericks! Thanks a million Josh.

 

Unfortunately I have to revive this thread, because something again doesn't work anymore about double-clicking console output. Now (since 5.4?), printed console output created by calling print() from a monobehaviour doesn't open the script editor (MonoDevelop in my case) or jump to the line. When I double-click on an entry, nothing happens. A workaround is to use Debug.Log(), where it works perfectly fine, but it would be nice to have this fixed anyway.

Submitted a bug report here: 856020

 

I'm having the same issue with double clicking entries in the console. Debug.Log doesn't allow double clicking, but errors thrown by Unity do. Using OSX El Capitan.

 

For me, it started working again in 5.5, maybe try if updating solves it for you too?

 

I'm also having a similar issue though not sure why this happened. Basically all I did was switch the external script editor selection from "internal" to "MonoDevelop(built-in)", and now it stops sending the source code line and double-click returns on any Debug messages.(Error logs still work fine) In addition, I am now also unable to switch back the selection to "internal", so I can't revert my changes either.

 

For anyone still having similar problem, I would suggest checking if Stack Trace Logging (from top right options in console tab) for Log and Warning is set to None, default is Script Only.

It started happening to a colleague of mine, and he found it. We have no idea when or how it changed.

 

Oh yes that was the issue. I think it was changed automatically after you change the Logging field values in the Player Settings when making a build. It somehow affected the Editor settings even though it was intended for specific device builds.

 

Pretty often clicking errors on Unity 5.5.1 doesn´t open VS here, too.

Doesn´t help here :-(

 

==>
* Removing Space from project path and project name
* Reimport project
Works fine..

 

I've had this issue for a couple years now. I've check the forums before and didn't find any answers, but this time I have found at least one. The Stack Trace Logging fix worked for me for now it seems.

I'm pretty sure my issue started because I would make a copy of the project when ever I wanted to make some radical change and then renamed that new project. This left older Microsoft Visual Studio files (and who knows what else) in the project folder each time I made a new copy.

The only way I fixed it before was to make a Unity Package out of my whole project, then create a new project and import that package. But that was a pain and I've been to lazy to do that.

Since I started using Collaborate I do not make copies any more.

Anyway, when you say "Reimport" what do you mean by that? Do you mean just shutting down Unity and then reopen your project again after you have renamed the project folders? I'm going to try that at some point, but everything is working now and I don't want to break it

 

If still someone is wondering...

Thanks me later..

 

here here

 

just check these boxes in player settings and yahoooooooooooooooooooooooooooo enjoy. Thank me later

 

My fix was stack trace logging, link goes to correct answer I found on the forums for my case

http://answers.unity.com/answers/1293556/view.html