I was excited to until I read "Unity has to have Android Support installed"I assume Android Studio… the bit I was hoping to get rid of with this package as a replacement
Also why not include a screenshot of what this thing actually looks like… we’ve all seen the package manager.
There are a number of screenshots posted if you follow the link to the documentation at the top. Also, you do not need Android studio. You need Unity’s Android support installed and the Android SDK (soon to be installed automatically by Unity). If your doing any Android developer with Unity you would already have the Android support installed.
Is there an option to output logcat messages, that are specific to the game only, to the Console window too? Or do I have to use the new Logcat Window?
This is not really a feedback on the functionality but feedback non the less… It’s, uhhh, it’s kind of ugly. Though it is so early in development that is probably the last thing on your minds.
Hi @Tomas1856 ,
I love the idea of having logcat directly in Unity. So thank you very much for your effort on this.
What I’ve noticed is that the search bar seems to be case sensitive. Please make it case insensitive by default (I think that’s what people would expect most of the time).
I think the look of the GUI could be improved at some points:
The search bar seems to be not in line with the rest of the menu bar (there is a gap of a few pixels at the top). Also the search icon is pixelated and streched (running on Windows 10 on a 1080p screen). The input text is not aligned in the vertical center.
And it looks strange that the search bar is round at the left and has edges on the right. I would say go for edges on both sides (as that’s what matches the button styles).
As a plus, updating the filtering while typing (instead of waiting for an enter) would be amazing. It’s especially weird when you remove the filter text, but the text is still filtered.
There is a small gap (of 1 or 2 pixels) after each scroll bar. On the left of the horizontal scrollbar there is also a gap.
The “Connected” text is not aligned in the vertical center of the footer. The green color is hard to read on the light editor skin (it works on the dark skin).
Suggestion: I think it would look better if every second log line is slightly darker (or lighter) like in the default Unity console.
Another Suggestion: If a filter is applied to a column, change the color slightly. This is to clearly show the user that there is an active filtering and that this might be the reason why he is not seeing certain logs.
Feature request:
I would love to have a button “Open Terminal” so that we can access the ADB via a Terminal. There are a few things that can only be done via ADB terminal commands (deleting sideloaded apps on the Oculus GO for example).
For search bar case sensitive: I think a toggle should help here.
For the GUI suggestions. #1. Yes, we also noticed the search bar problem, have an issue filed for it. #2. Nice catch, will check it out. #3. Good point, will talk with UX guys how to set it. #4. Did that in the new version. #5. Good suggestion, will file an issue to make sure it won’t be forgotten.
About the “Open Terminal”, good point! Thank you again!
Yes this would make sense. I think case insensitive search should be the default though. (Imagine you’ve created some log messages because you are tracing a bug in your game. You search for the messages in the logcat window and don’t find it. This would guide you in a completely wrong direction because you think your app didn’t log the message although you just haven’t used an uppercase for the first letter. That’s exactly what happened to me and it took way longer than I hoped until I figured out that the search is case sensitive ^^).
Hi @ ,
I’ve just played around with the Logcat Package (0.1.5) in Unity 2019.1.0f2 and I noticed some performance issues. Please notice the periodic CPU performance spikes that you can see in blue at the CPU Usage graph:
These spikes are clearly noticeable in the editor (e.g. when moving the camera through the scene or when playing in the editor). According to the profiler these spikes are caused by “AndroidLogcatConsoleWindow.RetrieveConnectedDeviceIDs()”, I guess because it makes a blocking call to ADB.Run(). Moving that call into a different thread would probably solve the issue.
Please note that I had no android device connected at this time.
Omg it properly detected the unity game process and only shows the relevant logs, something I never managed to do with the android monitor, I hated filtering by tag…
This package is fantastic! Thank you whoever made this!
The android logcat window cause some serious hickup for me. It basically freeze the editor every 2 second for 1 second.
Sometime it even does it when it is not in focus.
I’ve noticed that too (see my previous post ). I think this only happens when the logcat window is not connected with an android device. If you close the window while not using it you can workaround this issue.
