Bug First Element of a Custom Class in a List isn't drawn correctly [2021.3.3f1]

Pretty self-explanatory, I'm posting two screenshots for the bug. It messes up everything for the first element, can't press it, can't see it. It's a simple custom class, no editor scripting at all in a new fresh project.

 

+1

Happens to me as well.

I was also able to reproduce it in an empty project and with a struct. It occurs with both Arrays and Lists.



This is the code that I'm using.

Code (CSharp):

1. public class SimpleClass : MonoBehaviour
2. {
3.     [Serializable]
4.     public struct SimpleStruct
5.     {
6.         public int SomeInt;
7.         public string SomeString;
8.     }
9.  
10.     public List<SimpleStruct> List;
11.  
12.     public SimpleStruct[] Array;
13. }
14.  

I've reported using bug report - it has id: IN-3315

 

UP, as above. All reorderable list are broken on element 0

 

Was about to file this bug myself, saw it was already filed. Extremely easy to reproduce in a fresh project and has an extreme impact on workflow. I updated my project to 2021.3 and none of my element 0 dialogs are practical to edit.

 

Same for me here when I upgrade to 2021.3, and when I downgrade to 2020.335f1 and start a new project, the problem follow me in this verssion too, weird !

 

Same problem here

 

2021.3.4f has the same problem STILL

 

Yup, same here !
Annoying

 

They've also backported this bug to 2020.3.35 as well. How is such a basic, easily reproducible issue let through for LTS releases across the board? This makes the engine literally unusable.

Currently affected versions are 2020.3.35, 2021.3.3 and 2021.3.4. Use an earlier version of the engine to fix the issue.

 

Well,

I got an answer for my bug report but it's not very helpful.


As I've replied to it - this bug needs to be fixed in LTS versions. Having it fixed in an alpha release of 2022.1 is not a solution at all.

 

No kidding. Do you have a bug number that we can vote on?

Update: Just wanted to confirm, I went back to 2020.3.32f1 and problem is indeed gone.

 

I've used the editor bug report and I have no idea how this integrates to the Issue Tracker. It created a case on Unity's Jira and there is no voting as far as I know.

 

You could try searching issue tracker with the title of the bug, it works for me for one of my bugs. I tried searching for the same title as this thread but nothing came up. Maybe it's a different title OR internal bug report was never created by Unity. When my bug was confirmed I got an email with a link to the bug, it had an Issue Tracker Link and activity stated that a bug report was created with internal ID of UUM-2516.

It looks to me like Unity is using IN-xxxx bug report IDs for reporting from developers and then if the bug is confirmed by QA it gets an actual internal ID of UUM-xxxx. It's only at this point that the bug is searchable in Issue Tracker. So if UUM-xxxx was never created for your bug it won't be in there. Please keep in mind that I don't know this 100% but it certainly looks like that's how things are organized. Did you get a reply to your message? I would very much be interested in what you hear back.

 

Fix In Review for 2020.3.X, 2021.3.X: https://issuetracker.unity3d.com/is...n-for-arrays-that-use-custom-property-drawers

 

Thanks.

 

The 2021.3.4f1 still has it. Hopefully .5 will have it fixed.

 

For those looking for the answer, I have upgraded to 2021.3.6f1 and can confirm the issue is resolved.

 

You can try to put [NonReorderable] before the array. It's not the best solution, but it solved the problem for me.

 

You should look up upgrade your project's Unity version (ensuring you're using proper precautions), as this issue has long been solved in recent LTS versions.