Tons of compiler errors and fonts disappearing in the UI Builder GUI and Package manager which make the editor useless is all I get almost 2 years after watching the video from Unite Copenhagen 2019 about the new UI Builder…
Is this really the current state of the new UI System? (Preview 15 and Unity 2020.3)
This is really disappointing… Lost a whole day trying to implement toolkit and UI Builder (which was a really nice idea), but its not usable at all.
Best regards,
Marco
Actually, the current state of the new UI System is the one found in Unity 2021.2, without the package.
The package version allows users in 2020.3 and 2021.1 to keep experimenting with UI Toolkit in Runtime, but the package is experimental, as you can see in the Package Manager. Many new features are missing on the package because the focus is now on 2021.2+, as you can see in this Forum announcement from a while ago.
Hi Julia,
the forum announcement you mentioned is about the 2021 implementation but says nothing about other Unity versions, so I am not sure why you mentioned this. Anyway, people using 2021 having the same errors as you saw in the forum already. Further more I use the manual and not the forum for programming in Unity which says:
“Although Unity recommends using UI Toolkit for some new UI development projects, it’s still missing features found in Unity UI (uGUI) and IMGUI. These older systems are more appropriate for certain use cases, and are required to support deprecated projects. For information about when it’s appropriate to choose an older system instead of the UI Toolkit, see the Comparison of UI systems in Unity.” (2020.3 manual)
I am not sure how should I understand your message, so it is not recommended to use UI Toolkit in the 2020.3 LTS version? Are all other LTS versions except the 2021 version are not supported anymore then? Then you should change the according docs. Well, UI Toolkit is even recommended for new projects (which my project is and I don’t need all features). I followed the recommendations and all I got was a mess which is not working using the latest preview version and I am disappointed that a technology which was introduced 2 years ago (on Unity 2019) is still not working at all…
Best regards,
Marco
Yes.
Had similar experiences.
Walked straight back to uGUI or whatever it’s called.
Hello again, I’m sorry if all the information we put out there is confusing, I’m bringing this feedback to the team so we can hopefully avoid this in the future. In the meantime, this older announcement may help clarify some additional details. Also you’re right that our manual is not clear on our package being experimental for 2020. However, to clarify, UI Toolkit for Runtime has only been available for about 1 year now, not since 2019 as it was Editor only at that point.
As to what is recommended right now, we do encourage users to try out UI Toolkit for Runtime starting at 2020.3 especially if they plan to upgrade your project to 2021.2+ or 2022.x eventually. However the experimental package for 2020 or 2021.1 is not considered production ready. We know of some customers who still decided to go with it for 2020 LTS so it’s not impossible, but not what Unity recommends.
We’re also not happy that our latest release of the package has lead to errors and instabilities and we’re actively working on improving this, getting it right the next time, hopefully.
What are the specfic issues you’re having? Are you importing into an existing project?
Out of the box on 2021.2 (the incluhded version, no package needed) on a new project, I’m seeing no errors and it works fairly well. You may find some awkwardness if you’re trying to create a very animated, active, stylized UI; the closer your game UI is to a web UI the better it will feel. However, compiler errors and missing fonts sound like a versioning error.
Hey,
its as I mentioned Preview 15 and Unity 2020.3. But other people have the same probs with 2021, preview 15 and empty projects. Did you try the new preview 15?
Best regards,
Marco