as the title methioned . Unity3d 5.1.0f3 Pro Win7 64Bit. How can I fix it??
I don’t use Mono anymore, but IIRC if you keep Mono open and restart Unity to get it to sync properly again (or vice-versa? I can’t recall).
You may also need to have “Editor Attaching” checked in Edit->Preferences->External Tools.
This is an old thread, but I get the same issue now. When I click to open a script, an extra MonoDeveloper instance is started. I get a new instance for every time I open a script. However, the new instances never opens the script, the script is opened by the instance that was started first.
My settings.
– Single Unity install (Unity 2017.3.0.b10).
– OSX 10.13.1
– Preferences–>External Tools->External Script Editor: MonoDevelop (build-in)
– Preferences–>External Tools->Editor Attaching: enabled
– Finder set to open .cs and .sln files with the same MonoDevelop as default for all.
Please let me know if you have the same issue or have managed to solve it.
Carl Emil
I have the same problem using Unity 2017.2.0p3. Did not find a way to solve it yet
I ditto fred_gds. Same problem on 2017.2.0f3. Any solution yet?
I follow your tips, but it still not works on 2017.2.0f3.
Is it a new issue introduced by version 2017.2? I didn’t encounter this issue earlier …
BTW, I don’t think Carl Emil resolved this issue … He was talking about what he met.
Anytime I click on an error in the console, another instance of MonoDevelop opens… VERY DANGEROUS! (Unity 2017.3.03f)
edit… this is if I open MonoDevelop, from my desktop, then open any relevant script from Unity.
MonoDevelop for Unity is deprecated, and has no support in the next major Unity release. I’d be moving off MonoDevelop rather than troubleshooting its issues at this point.
I will wait for 2018 to be fully released.
Go into your project folder and delete the .csproj files and the .sln file. These files will be regenerated. See if you still have the problem.
This still opens multiple copies = (
This was a VS fix https://answers.unity.com/questions/1078859/unity-keeps-opening-new-instances-of-microsoft-vis.html so it may not work for mono if you are using that instead. Was just a suggestion in case it did work. Otherwise, honestly not sure.