Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.1
Issue ID
710229
Regression
No
Using StackTraceLogType.Full causes Debug.Log entries to not be clickable
1. Set Application.stackTraceLogType to Full
2. Have a script do a Debug.Log call
3. Double-click the entry in the console
Expected: should go to the location in the script file where the Debug.Log call is
Actual: doesn't.
Reason is that the logic in DebugStringToFile in LogAssert.cpp bypasses gPreprocessor when full traces are requested. That logic leads to ExtractMonoStacktrace, however, which is necessary for fixing up the file and line information (which originally points to the Bindings.gen.cpp file).
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment