Search Issue Tracker
Fixed
Votes
2
Found in
4.3.4f1
Issue ID
613056
Regression
Yes
After clicking on a Debug.Log statement output in the console text cursor does not show to corresponding line
How to reproduce:
1. Open the attached project "new1"
2. Play the "scene" scene (which has C# script with a Debug.Log Statement)
3. Click on second Debug.Log in the Unity editor console, while MonoDevelop is still closed
4. Notice that it opens corresponding file in MonoDevelop but text cursor is not showing to the corresponding line in the C# source code
Note: if pressing on Debug.Log error while MonoDevelop is open, the text cursor will be in correct position
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment