Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0f3
Issue ID
900022
Regression
No
Clicking message in Console window opens a new Xamarin Studio instance every time
- Create a script in Unity that has two or more compiler errors
- Set your default code editor in Unity's Preferences to Xamarin Studio
- Double click on one of the error messages in the Editor Console window to have it open Xamarin Studio and show the script that generated the error
- Remove the cause of that error and switch back to Unity so that the script gets recompiled
- Double click on another one of the error messages to go to the script that has an issue
Expected: the already open Xamarin Studio shows the script with the error
Actual: an additional Xamarin Studio instance gets open with the script (every double click in the Console window will just open a new instance of Xamarin Studio)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment