Official UI Toolkit 1.0-preview available

Have been playing around with the new package for a bit and really like the new workflow. I have some additional questions/feedback:

1. Selectbox is really missing in the basic components as it's an essential one for any UI. Will it be available any time soon?
   
2. Is there any alternative to CSS background-repeat and background-position properties? Couldn't find these in the UI Builder.

Thanks!

 

Tested an empty project with the package list and version mentionned by @Chris-Trueman could not add the UI Document.
Tryed remoing hte input package and then I could add the UI Docmument.

 

Thanks for the quick reply!
Yes, I mean the Select tag. I know in editor it's called PopupField and I've been using it already. I was asking more about the runtime version of the popupfield as it's not visible in the components. If I check the Editor authoring checkbox and then drag the PopupField to the canvas, will it work properly in runtime?

 

I tried this, and while I was able to get a UIDocument added to the scene, it caused far to many errors to be usable. At first it was cyclic reference errors when I added the InputSystem back in(had 102 compiler errors because of the missing InputSystem).

Code (CSharp):

1. Assembly with cyclic references detected (Packages/com.unity.2d.animation/Tests/Editor/Unity.2D.Animation.EditorTests.asmdef)
2. (Filename:  Line: 0)
3.  
4. Assembly with cyclic references detected (Packages/com.unity.ui/Core/UnityEngine.UIElementsModule.asmdef)
5. (Filename:  Line: 0)
6.  
7. Assembly with cyclic references detected (Packages/com.unity.inputsystem/InputSystem/Unity.InputSystem.asmdef)
8. (Filename:  Line: 0)

Then I got a whole bunch of "The referenced script (BlaBla) on this Behaviour is missing!" Which looking at each one said to fix compiler errors, which there were none.

I removed UI Toolkit and the missing script errors went away, but I ended up loosing some of my references. Not a big deal to drag them back in. I had restarted the editor to see if it would fix the missing script warnings which may have caused it to loose some of the references, it may have only been on the GO's that I looked at before restarting.

I'll wait for the next version to test it out in this project, so I don't run into any more incompatibility issues. Any eta on that drop?(I know, I know you just dropped this one )

 

Ok, but how do you assign the font with the needed characters, say for Japanese? Similarly to TextMesh Pro?

 

What is the proper way to move visual elements to a specific position?
I would like a panel to appear in a specific location after I click on another element. I have:

Code (CSharp):

1.  
2. var v3 = new Vector3(Screen.width - container.layout.width, Screen.height - container.layout.height, 0);
3. Debug.Log(v3);
4. //container.transform.position = new Vector3(v3.x, v3.y, 0 );
5. container.transform.position = new Vector3(1367.1f, 394.2f, 0);
6.  

If I assign the exact values as "numbers", the panel is correctly translated. If I assign the vector, which contains the same exact values, the panel disappears. What am I doing wrong?

By debugging I have also noticed that right after enabling the UI, layout.* is NaN. Is there like a "layout ready" event or something? Maybe that is breaking the panel? If so where should I get the desired size?

 

I would set the style position to absolute with the pixel coordinate I want.

 

Is there any plan for multi-screen support?

 

sPanelSettings`


I added the 1.0 package in 2020.2.0a17, it cannot be used normally, when will the preview package 4 be updated =-=

 

ok

 

Probably it's always great to have various options, however, I want to emphasize that I personally love the way how authoring works in UI Toolkit, and I very much prefer it over the old canvas authoring way. Despite the bugs, the UI builder and the flex layout are awesome. I just wanted to mention that

 

Following up on the multi display question by @MdoobM ... Currently, when using UnityEngine.UI to render to another display, you just change the TargetDisplay property on Canvas component. What is the equivalent in UI Toolkit?

 

The new UI package could possibly be the cause of my editor and player hanging. More info here: https://forum.unity.com/threads/edi...rsing-profiler-data-0-xxxkb-processed.929217/
Debugging the Player made me become suspicious of the UI Toolkit package
Disregard this post. The issue was NativeArrays allocated with TempJob but not deallocating fast enough, these would hog up threads for some reason eventually stopping all threads, which is why at one point the debugger was indicating a UI Toolkit related thread hanging, it was just a coincidence as all threads were stopped.

 

Can't test this out yet because I use the new input system, but...

This is easily the best sample project I've seen from Unity. Not just for UI Toolkit things too. It's complete as far as I can tell and it's not overly complicated.Well done.

 

I held off on investing too much work into the UI in my project with UGUI because I was waiting for this. Unfortunately since I use Input System, I can't use UI Toolkit just yet. I'm very excited for this!

 

There is a bug with your UnityRoyale-TowerDefence-UIToolkit demo, the font in preview all broken. The issue apparently is that the preview windows reports dimensions of a preview frame which are very small but not downscaled properly.
Match Game View does not fix the issue as well since it just resizes the preview frame.

 

I'm not talking about the background, I'm talking about font scaling.

And honestly, why not use `zoom` to handle that? It will scale viewport properly and it should be good for preview.

 

Yeah, some way to store reference resolution data would be nice.

 

How reflective is 1.0.0-preview.3 in terms of CSS font/text properties support? Like, I see that `text-transform` does not work nor very custom `font-weight`.
Is there full list of what is supported? This one:
https://docs.unity3d.com/2020.2/Documentation/Manual/UIE-USS-SupportedProperties.html
does not seem up to date just general overview.

Where can we report bugs and issues?

Why is the guy who did this still on the team:

 

Yeah, don't be like that. People don't deserve to be fired due to introducing a single bug. That's a super toxic attitude!

 

That is not even a bug, it's the correct way to define the margin in CSS (there is no reason to not match that in USS) and the values from the ui builder are put in there correct spot in the uss file.
The only improvment that could be made is to rearange the order of definition in hte UI builder to match the CSS definition order which is clock wise starting from the top (top -> right -> bottom -> left)

 

Dont be ridiculous nobody was unironically saying someone should be fired over this, but the fact such issue even exist is kinda ridiculous as well. But then again, this is Unity, can't really say I expected something different.


After playing with the preview for few days I'm utterly disappointed. I was ready for USS to be limited in some aspects, mostly because of performance and rendering reasons (web usually tries to target 60fps, Unity has to consider higher targets) and I expected it to ditch a few thing due to its own layering and compositing but good lord I did not expect USS to be THIS bare. It is like we are back to the earliest days of CSS where we have some very basic sizing and positioning but with the luxury of Flex. And because of their different implementation of the rendering you cant even apply some old performance wisdoms from web CSS.

A lot of people who were excited gonna be dissapointed when first release of UI Tooklit comes with Unity 2020. And, judging by how long initial release took, it most likely will take literally YEARS before this UI framework will be expanded to something comfortable and better than current Unity UI.

 

Alright, I give up:



Guys, this isnt 1997, adding flex means jack sh*t. On its own it is unusable, it is suffering and misery when the rest of StyleSheet capabilities isnt just on par. I dont even remember when I last time had to pad an inline-element to get border right, jesus.

My suggestion: take another year or two and expand the team with people who have experience with WEB design. Do not try to aim for 2020, even as a public open preview. It just bad.

 

I knew it was a mistake introducing another web related tech in Unity. It is just like back in the UnityScript days. Call it Javascript and all the wannabe web-developers will mistakenly think they know what they are doing. It is the same with this. Just this time with the styling system.

 

Just use https://github.com/mikke89/RmlUi already . Is more advance that what unity team would do in 50 years.

 

This isnt a thread about other UI frameworks/libs, also, that framework integrated wont be on par with performance.

 

Of course, one should not expect that the knowledge about browsers can be transferred to Unity. They also use the name USS and not CSS to clearly distinguish that it is not the same.
Unity could have used Chromium, but that would increase the size of each Unity game and create an overhead. Size and overhead might not be noticeable on a gaming-PC, but on low-end devices.

what's wrong with that? CSS / USS padding / margin are always arranged clockwise (top-right-bottm-left). But that doesn't mean that it has to be that way in the editor, since it seems to group logical left-right and tob-bottom. But it could be confusing for people switching between builder and USS or people with web origin.

 

I did not mean to to offend, it was off-hand joke mostly.
Here is the problem though Damian:

Nobody likes UnityUI. I can go into any Unity community and there will be 1:10 people who like and hate it, just point fingers and they will tell telltales about it. This one of the biggest reasons a lot of people I've seen were exceptionally excited about UI Tookit. It was a promise to finally end the suffering.

That's what I'm saying - TAKE more time instead of underdelivering or you get the same disappointed response and feedback as with new Input System where people eventually would shrug and go back to Rewired.

Implementation isnt the problem, problem is how many workaround and compromises I have to construct. After working with CSS3.x before and such luxuries as fit-content/max content it just does not feel very good. I still can do whatever I want but it is a letdown and unnecessarily complexity.

 

Speaking of feedback you probably should open up an issue tracker, forums are terrible for this

 

I wouldn't put all the blame and frustration of current Unity on some of these hard working engine developers and community managers. It's mostly the top most upper management, and the lead directors, as well as human resources that has the biggest impact on prioritizing certain things over others. UI Toolkit looks awesome, I can't wait for the packages to be production ready.

It's just that Unity over promises, hypes up unnecessary features (like Unity Collaborate), and then abandons those features when teams really start implementing them. Unity needs to focus on core essential features that'll impact the future of game development, and abandon all the tech demos and features that most developers don't care about. It's about prioritizing essential features like the Input System, DOTS, UI Toolkit, and Rendering, while cutting out the fat, like Unity Collaborate, Unity Mars, Unity for Architecture, all these unnecessary tech demos where the models can't even be used in commercial products.

 

@sebastiend-unity

Please don’t think we all feel this way. In my instance, my friend and I use Collab everyday. I love it (even though it has some issues) and removing it would be a detriment to our development as my friend is not technical at all.

Thanks for all the hard work, and I cannot wait for UIToolkit!

 

New around here?

There was a suggestions site, it was such a garbage fire of horrible that it got shut down. The forums are much better for this kind of thing, since, if people are polite, we can have constructive discussions about things instead of just throwing suggestions into the void.


UI Toolkit is absolutely amazing this far for editor UI. I'm having a real great time rewriting a imgui based system to UIT. I hate UGUI with such a passion that I'd accept pretty much anything, so I'm looking forward to starting to write in-game UI's with UIT.

To be fair, I have a ton of frustrations when working with UIT, but almost all of them are simply that SerializedObject/Property is a pretty S***ty API, so Bindings end up inheriting that S***tyness. Hey, you removed an array element? Well, now all the bindings for later array elements are off by one, and have to be rebound! Not much to do about that for now.

Collaborate was a failure of product management the second that it was decided to be made, and it's been a continual failure since. What makes me worried about Unity is that most of the core stuff that's delivered for free with Personal is great, and every single service that you have to pay for is bad. Some of the more recent integrations might be worthwhile (Havoc), but Collaborate manages to be easily the worst source control system ever made, and stuff like cloud build or analytics are easily replaced with free services or just knowing how to send data to a server.