Am I crazy in thinking the console window would normally always be automatically scrolled to the bottom and the most recent messages? Currently mine will only stay scrolled to the top, and I need to manually scroll to the bottom. I can find people requesting the feature, but years ago, so I don’t know if maybe it was a setting I switched accidentally but I can’t find any way to switch it back.
Thank you
Bumping this because I’ve asked a bunch of other places as well and no one has any information. This is so annoying. If anyone can give me any insight at all I would be so appreciative.
Try to select latest message in the console. Works fine for me!
Up until a few days ago, mine would always be stuck to the bottom/the newest messages, unless I scrolled up or away from the newest message in which case it would stay where I was scrolled. Then all of a sudden it stopped, and nothing I do seems to be able to switch it back.
Tried this, basically I do this every time I hit play hoping it will magically stay this time but nope. No luck yet. Thanks though.
I just figured out why this was happening and I thought I would share in case someone in the future is confused about the same thing:
So, I had a bunch of components sending Debug.Log information, and on the first frame that the Console received any information to display, it received more than would fit in the area without a scroll bar and it doesn’t recognize the message displayed at the bottom as any “newer” than the message at the top because they were all generated at same time, so it stays at the top. Since smartscroll is not enabled on this first frame, it isn’t enabled at all, and it stays at the top. If I send a single message to the console before sending it a lot of messages in a single frame, smartscroll is enabled and it behaves as intended.
So, if anyone in the future is confused about this and finds this forum post:
Just add a single new Debug.Log statement when your scene loads and it will stop happening.
Thank you, @DWmDM !
Thank you @DWmDM !
For all who are too lazy to read and need a turnkey solution: Just add any Debug.Log in Awake()
I use such a universal stub: Debug.Log($"{GetType().Name} Initialized");
You would think if these developers actually used their own stuff, they would get as frustrated and annoyed as we are and do something about it.
Also this fix did not solve my scrolling problem…
I have the same problem in the Unity Android logcat package. The usual fix for badly designed terminals (there are lots of them) is to use keys to skip down to the bottom of the file - you need to get the cursor onto the last character for it to lock there. ‘End’ often does it, or repeated ‘PgDw’ keys, unfortunately logcat doesn’t accept keyboard input. It doesn’t seem possible to click the mouse after the last character.
To be clear: the window worked as expected until I selected a line which was not the last line, and even then it resumed scrolling to show the bottom line if I used ‘clear’ to empty the window. Then it stopped working during a long day of testing, and I can’t make it resume.
This truly is annoying behavior. What I have been doing when I need to monitor a stream of debug data as the game runs is adding a public member to the component that would be calling Debug.Log, and just setting that member’s value to whatever I would have been printing to the console. It doesn’t keep a record for me, but it lets me monitor the changing value without any scrolling problems.
Creating a terminal that doesn’t scroll. Impressive…
It’s actually fixed in recent releases.
But yeah, it’s indicative of some larger problems at Unity that this was an issue for so so long.
Crazzzzzzy, for real, its’ in 2021.3.5f1
On 2022.3 and have the problem still. I don’t remember ever using any version of Unity where this wasn’t an issue.
King
Also, toggling “collapse” often fixes this error
Still happens in 6000.3.12f1
Incredibly frustrating. Above workarounds do not work for me.