Official UI Update - Q3 2021

Grid Layout and Virtualized Grid Layout in List View'd be great for Q3

 

Where should we report beta bugs related to UI Toolkit, this forum or beta forum? (Besides reporting it via unity bug report)

 

why uitoolkit doesn't use same font asset as TMP?? If we use both tmp and uitoolkit,there would be two fontasset in project.One normal fontAsset and one is TMP_fontAsset.This would generate two font atlas.

 

Just wish I could finally dish the legacy UI and switch completely to the toolkit... but alas I need world space UI!

Keep up the great work!

PS. Should we expect to have up to date Unity-Learn tutorials / training specific for UITK when it hits production-ready? (I assume... 2021.2 LTS?)

Thanks!

 

Hi @benoitd_unity. I didn't see any mention about UI toolkit dots runtime. Can I expect a UI toolkit dots runtime preview package release when dots compatible with Unity 2021.2?

 

Are any plans to backporting UI Toolkit for current Unity LTS (2020.3.x)?

 

Any news when preview-15 will be available for 2021.1?

 

World Space UI is such a critical matter for UIToolkit to be honest. I see that it is on the "Planned" section, I really hope that we can see something on that front soon enough

 

Interesting thing: setting element height in percents actually makes its height equal to 0.

Steps to reproduce:
1) Create a VisualElement with 100x100 px size and set the color to red
2) Change width measurement units to % - everything's fine.
3) Change height units to % - the element is still visible in UI Builder, but has 0 height in game.

 

This is probably planned for Unity 2022, looking at the forum answers.

In general, it would be nice to have more ETA on the product roadmap (something like "Planned for Unity 20XX.X" or "Planned no earlier than Unity 20XX.X").
It would be easier for people to know if/how they want to use the framework

 

Indeed! For example, we have a project that we want to ship by next year. There we have 100+ separate world space canvases, plus some screen space overlays and combinations of camera+ui->render target->ui raw image->camera.
As can be imagined, overhead of ugui is heck. UIToolkit's "one batch" and high performance idea was charming, if it would have world space ui support ofc.

 

This looks amazing! Would support for keyboard UI navigation be coming soon? Like selecting elements in code/by arrow keys?

 

I'd love to be able to see and debug my Runtime UI in the Scene view

Also, the documentation needs a lot of help. There are no examples and the only help is spread over random, years old demo videos.

 

Well, I have 100+ world space canvases and probably just one screen space at max. Tbh, the bottleneck on-screen space UI doesn't worth the effort of switching/learning UIToolkit.

I have world space background images and text on world space canvases, they also tween and animate. I would say there are separate windows in a 3d space.

 

Hmm, I couldn't find this anywhere, and I see that none of the Button or its superclasses implement ISelectable interface. I also couldn't find anything about specifying navigation explicitly, e.g. pressing down key while "Start Game" button is selected will select "Load Game", in the UI builder or in code. Does selection/navigation works differently than the currently uGUI?

I did find a focus method, but that seems to deal with text input instead of navigation with keyboard.

I'm happy to read any code if there isn't any documentation available yet

 

I mean like UGUI's canvas with the Render mode set to either Screen Space Camera/Overlay. I'd really appreciate being able to see the UI in the scene view, in context of where i'm working (with the option to turn it off) - especially working on a 2D game. And a lot of the time i'll have the Game view "closed" (not the active tab), even while in play mode, so being able to debug the UI in the scene view would be nice.

 

@benoitd_unity We’ve brought this up multiple times on the forum, filed a bug report and repeatedly asked your team for help but the issue has been ignored for months, so I’ll try here.

Text wrapping in UI Toolkit is completely broken and causes text to randomly wrap even when there is enough space. So a text such as “Start game” randomly gets split into two lines if text wrapping is enabled.

I do not see how you can release UI Toolkit with this bug, or how you would expect developers to use the library in real world projects until that problem is solved. Text wrapping is a must in even the most basic games.

The case number is 1332695 and the issue is also listed here:
https://issuetracker.unity3d.com/is...tally-or-changing-the-match-in-panel-settings

Does your team have any update on this?

 

@benoitd_unity Is that the development of dots UI runtime has been stopped until this UI Toolkit out of beta at 2021.2?

 

Is the 2021.2 beta the most up-to-date stream with preview 15 or are other release streams more up-to-date (LTS, 2021.1?)?

 

No, thank you, that's what I needed to know
> the more complete version is only in 2021.2

Going deep into UITK integration in a risky move for a project, wanted to make sure I -always- got the latest and most compatible version of it... so 2021.2 it is!

 

Sad that package is now compiled and source can't be changed anymore

My ability to experiment dropped down to 0

 

Hi @JuliaP_Unity @uMathieu Any special reason why can't ship it as built in package with source code?

 

It also allows me to fix bugs without having to wait months for Unity to do it. For ex. default TextMeshPro package is unusable for me because of localized fonts issues and input field bug. Reported them but 2 months later they are still not fixed.

Speaking of UI I've noticed that something very simple like drawing top bar of Game View takes a whopping 1ms, that's more than 20% of editor overhead in fullscreen playmode. Zoom slider (that i never use) alone takes 0.20ms...

I'm very surprised that Game View is still not converted UI Toolkit.

 

Not really, I have a solution that replaces single files in packages. That with source control makes it very easy. I guess ill have to make another one for dlls with mono.cecil.

Couldn't Unity have something like core packages? Or couldn't the package be available from package manager if someone wants source access?

The more source users can access the better for everyone, there's nothing to hide as dlls can be decompiled easily. I already said couple of times that all packages should be on github but it's also true for compiled libraries:

 

yes its better to first make it feature complete than adding dots

 

Indeed, don't bother connecting the DOTS. They won't lead you anywhere for at least a few years. ;P

 

In version 2021.2 UI Toolkit/ builder in Runtine will not support the new input system and visual scripting ?
thanks

 

The new default runtime theme ("Unity-theme://default") has broken some of my UI spacing and scaling, How can I revert to using the older default theme.
Setting my theme to a blank TSS file completely breaks my UI, (nothing visibly renders)

All I want is for it to work like it did in preview 14.

 

Sadly, that's why these are "preview" -- they aren't meant to be final (or built upon) -- since things _will_ change/break.


That said...

It could help the devs to show (visually) what "breaks" (and what doesn't) between versions. It could simply be an error.

 

Completely agree to JeddMorgan...
Same issue here (using preview16). It seems not possible, to even see that default values. Its just referred to the ("Unity-theme://default"). Its a tss file, that seems a unity-asset with attributes, not even a uss file related, or viewable with something except the array view of unity...

Other findings:
Bug1: The height calculations are broken... Setting margin/padding on a text will cause wrong height calculations. The text is overlapping, and the height is reduced... I needed to wrap all my Label Objects to other ones.... Am i the only one who set paddings on Labels?

Bug2: Unity Crashes when setting a "Focus" directly on instancing a InputField... It causes an index out of bounds... After long debugging into the horrible uncommented code: I found, that it needed to be rendered without a focus at least once, to fill the needed textinfo values...
Workaround: Add a 100ms timer before calling "Focus"... (even 1ms delay is not helping)
Simple usecase: Show a textfield and let the player directly start typing into it...

Bug3: The Text inside of the InputField has very big margins. Looks pretty horrible now...

Bug4: It looks like buttons now gets a focus and with WASD and Arrow-Keys can be moved around? Would be perfect to stay at a default behavior at default.
The main Bug at it: It seems just happening in the compiled version, not in the Editor....
Update: It looks it was just one of the compiles... No idea why it's now behaving normal again.

Bug5: That mentioned Theme file is completely bad. Please split that in some basics and a uss files (including an "empty" basic one, that is just functioning, without useless not wanted style changes... Using a new created empty one causes that the root panel is not rendered well... Please no "Magic" /default stuff, so people have a chance to find something...


If this "bugs" are not bugs, it would be good to mention that parts in the migration guide

 

Hi @benoitd_unity
Any plans for a Q4 Roadmap/Update?

 

Hi, are there any plans to migrate ColorField from UnityEditor.UIElements to UnityEngine.UIElements?
It would be very helpful if the ColorPicker logic would be available per default at runtime, too.

 

That and many other fields from UnityEditor.UIElements would really help too (to create fancy runtime tools)