koobas.hobune.stream
Unity Weird Inspector Layout Behavior: Can't Scroll To the Bottom of Component Fields
So i got this weird issue where i can't scroll to see the bottom fields of a component (Ther's no scrollbar, and scrolling with the mouse doesn't do anything) I have to collapse many of the other components, to give enough size for the fields i want to see to come into view. As you can see in the image below some of the fields overlap with each other. Weirdly enough it only happens with the project I'm working on. it doesn't happen when i open other projects.
<<<<<<<<<<<<>>>>>>>>>>>>
I tried restarting the pc, and relaunching unity again and again but to no avail!
Any idea as to why this is happening and how to fix it? [Unity 2020.1.12f1] 
Sounds good Thanks :) I created a new project and moved the assets and scenes to it, and it fixed the issue. However, the next day the issue came back! Doesn't want to go lol. I filed a bug report, but no response yet.
There's someone else with the same issue here: https://answers.unity.com/questions/1793720/inspector-is-all-scrambled-and-unusable.html
They said it helped to rename the Library folder. i.e. reimport.
I got exactly the same problem for a few days. And I have some pretty big components. But I can't scroll down to fill up all the component fields because the inspector has this weird behavior. I can't make my game to work without it. I don't know what to do
I confirm I had this randomly happening to me this week without any clear idea as to what causes it. Had to restart Unity and it just worked without issues. I am at this moment just doing basic tutorials to refresh my unity knowledge so using exclusively standard Unity without any packages plugins or any other 3rd party items . Version is Unity 2020.1.8f1 and behavior is identical to OP.
Did you (or anyone else having this) try reporting the bug? (Help -> Report a bug)
I have the same issue and it makes things sooo hard.... scrollbar gone and so is the the Sprite Editor as OP mentions
I have no clue to how to get rid of this...it is kind of a showstopper in many cases :(
Using unity 2019.4.1.16f1
Also tested to load factory default on the layout. No difference :(
Same happening to me. Created a new project with the HDRP template using Unity2020.1.4f1 Personal and couldn't even read the HDRP readme asset because the inspector wasn't scrolling - without me actually touching anything.
idk what caused it, it started happening to me a couple of days ago, I finally managed to fix it by:
1) Closing Unity 2) Back up the "Library" folder inside your project 3) Delete it 4) Load your project and wait for it to generate the folder again 4.2) It'll show a lot of nullException errors in the console and the scene and game windows will apear empty, don't worry 5) Close Unity 6) Paste the backed up Library folder inside your project and replace everything when it asks 7) Load your project again, and everything will be fixed, no errors, all the windows normal again, and the inspector has a scrool bar again!, everything is fixed.
Hope this helps someone that sees this in the future, this is my first reply I make on the forum, I had been very annoyed with this bug.
Are you by chance using any of the *Group classes in any of your own components? If you have mismatched begin and end calls i.e. with BeginFadeGroup or similar stuff like this might happen. Unity used to handle these kind of errors gracefully, so asset store packages may often have similar issues if they're not maintained.
You can also try unexpanding the various components by clicking the little arrow on the top-left of each component, to pinpoint which one is causing issues.
I'm new to unity, never used a custom editor or group classes, I do though have DOTWeen Pro imported, which may be using them, but I only animate in code.
Did you try clicking the small arrows next to the components to $$anonymous$$imize all of them, and then expand one at a time?
Yes, doesn't do anything, but as i mentioned above I collapse all components other than the one I want to see the fields of, to make space for its fields to show up. But even then if the component had too many fields, some won't show up as there isn't enough space.
