Hi,
I updated to 6000.2.6f2 after the CVE issue. But I’m getting a lot of problems with the inspector. It’s blanked on me a few times (just a black gap), but it’s not very reproduceable. What is reproduceable is the corruption you get with the array display, and it makes arrays pretty much unusable. I’ve done a video at Watch Unity_2NNUUqkNma | Streamable. You get a whole load of errors that looks related to threading and/or screen resolution. If it matters, my screen is an HDR WQHD (2560x1440). I was scaled at 125%, but I switched back to 100%, but it still happens.
To repro, create a MonoBehaviour with a serialized array, add it to an empty object in a clean scene, and then click on the object in the hierarchy so that its properties appear.
I found it does it with GameObjects and ints too. I found it behaves similarly with lists, but in the same way.
using UnityEngine;
public class BugTester : MonoBehaviour {
[SerializeField] int[] _bugPrefab;
}
Errors include:
- UnityException: GetName can only be called from the main thread.
- NullReferenceException: Object reference not set to an instance of an object
- MeshGenerationContext is assigned to a VisualElement after calling ‘UnityEngine.UIElements.UIR.MeshGenerationCallback’. Did you forget to call ‘End’?
- ArgumentException: The state of the provided MeshGenerationNode is invalid (entry isn’t empty).
Kind regards.