UXML looks completely broken in Runtime

Unity Engine
1

It is the only one that does that, also the only one I am loading through

            VisualTreeAsset VisualTreeAsset = Resources.Load<VisualTreeAsset>(SourceXML);
            if (VisualTreeAsset != null) {
                VisualElement = VisualTreeAsset.CloneTree();
                WindowContainer.Add(VisualElement);
                return VisualElement;
            } else {
                Debug.LogError("UXML not found in: " + SourceXML);
                return null;
            }

Normal working version: (top left, bottom right is old working version in Unity UI)

6394304--712955--upload_2020-10-7_17-34-23.jpg
6394304--712955--upload_2020-10-7_17-34-23.jpg1920×1040 837 KB

Non working Runtime version:
6394304--712961--upload_2020-10-7_17-40-22.jpg
6394304--712961--upload_2020-10-7_17-40-22.jpg1920×1080 659 KB

I have no idea why or how this happens, there is no error message. I can only assume thing like the compiler not figuring my Resources called UXML exists and it creates it wrong therefore.

2

It looks as if the stylesheet failed to be applied. You can try to load it manually and add it to your UIDocument’s rootVisualElement.

3

There is no style sheet, it’s all inline. Is there some sort of ‘default’ stylesheet that might be failing to load?

4

The default style sheet looks present given that buttons are appearing at the top.

Which UI builder version are you using? I remember a bug with styles disappearing in play mode a short while ago:

That generated some errors in the console though, is that your case?

5

Yeah… I am using an old version because I made changes to the package to implement custom inspectors for custom elements…
I guess I will update, then I will report here if the bug still happens.

None whatsoever.

Edit: Actually, I figured out I will have to remake all of my interfaces to UXML for the drag and drop to work between (UXML ↔ Unity UI) them without too much temporary code full of static variables, so I won’t be touching this for some months and instead move to implement other things. So I won’t be updating my packages anytime soon.