Search Issue Tracker
Fixed
Fixed in 6000.0.56f1, 6000.2.1f1, 6000.3.0a5
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
6000.3.0a3
Issue ID
UUM-112357
Regression
Yes
Debug.Log empty string displays visual artifacts in Console when "Log Entry" in Console is set to "1 Line"
Reproduction steps:
1. Open the attached “IN-108808.zip” project
2. Open the “SampleScene”
3. Open the Console Window
4. Click on the three dots to edit the Console Window settings
5. Go to “Log Entry” and select “1 Line”
6. Enter Play mode
7. Observe the logs in the Console
Expected result: The first 6 lines are empty with no artifacts
Actual result: The first 6 lines have artifacts in them
Reproducible with: 2023.1.0a20 (be935afddb32), 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a3
Not reproducible with: 2023.1.0a19
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Issue does not occur with any other strings, including single whitespace or tab character or passing in 'null'
- Does not reproduce with other “Log Entry” options
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 6000.3.0a5):
Fixed artifacts in console window when using Log Entry = 1 with an empty string.
Resolution Note (fix version 6000.2.1f1):
Fixed artifacts in console window when using Log Entry = 1 with an empty string.
Resolution Note (fix version 6000.0.56f1):
Fixed artifacts in console window when using Log Entry = 1 with an empty string.