bad link, we will have something to say in the audio area soon!
4 Likes
I just opened my project in 6.5.0f1 but immediately discarded all changes in source control and went back to 6.4.11f1.
Problem is that all my UI Toolkit designs are entirely broken. All bottom and center aligned elements got anchored to the top, so the whole UI was entirely squeezed into the topmost 20% of the screen. The layout is already broken outside playmode when looking at the game view, it’s not a runtime-only issue.
Is there a known change that could cause this? This may have some easy, straightforward fix .. I hope. My UI is a single “HUD” document with edge, corner, and center anchor elements into which I drop other UXML documents.
Update:
I also get a lot of these errors in the console, I didn’t initially notice they were UITK related and it looks like it might be related to the new panel renderer since it mentions “UpdatePanels”:
Unknown property id 131084
UnityEngine.UIElements.UIElementsRuntimeUtilityNative:UpdatePanels ()
This is what the main menu now looks like:
Correct layout in 6.4:
Sent a bug report => CASE IN-145911
UPDATE: Resolved
I had cloned and modified the Unity default stylesheet to get rid of some colors. I reverted back to default styles and fixed my original USS issue.
Still, apparently a copy of the default stylesheet (from 6.4 with just color values modified) seems to cause “unknown property id” errors.
1 Like
I know there were some big changes to UIToolkit Initialization I don’t know about alignment
This sounds really concerning. My current project is using UI Toolkit instead of uGUI.
Nothing changed that should have affected existing UI Toolkit usage, especially going from just 6.4 to 6.5. Thanks for reporting the bug. We’ll look at it asap.
1 Like
I thought UI Documents were replaced now by PanelRenderers, no? Or is this something that has to be done manually?
Have you actually seen your uxml or styles changed in git or is it purely visual bug? I often had random bugs like this after upgrading and usually they could be fixed by just opening file in UIBuilder and saving it again.
UIDocuments is still a thing and haven’t been replaced. PanelRenderer is a separate component
2 Likes
I also have expeierence this with changing versions.
Edit: Note the most recent beta didn’t have this issue. This issue only started with the 6.5 stable first release. Might want to try the most recent beta and see if it looks correct on there.
Note in 6.6 the newest release also spits this error out at the same time. Note sure if they are related. Error that says the AccerlationCacheServer noticed a duplicated USS Theme sheet that is cached so discarding new set theme sheet for panel.
I noticed the layouts break during panel update when this second error pops up and when looking at the UI Debbugger the biggest difference is that the panels isn’t loading style sheets from set theme. Not sure if this is also messing with your UI as well, but something to check in the UI Debugger.
i went from 6.3 to 6.5 with full UITK and had no problems
1 Like
Hoping for the best with this new release, for Unity and all the developers out there. Thanks, Unity!
1 Like
Hi,
I had a quick look at your project. It looks like the UIDocument root element is broken due to invalid styles being applied, as indicated by the console errors (Unknown property id ....).
I found that the main Theme is inheriting from another theme file named default-modified.asset. It looks like this asset is somehow corrupted, possibly due to serialization changes that happened in 6.5. I am assuming this file is a copy of the builtin Unity styles with some changes applied. Until we figure out exactly what happened, would it be possible for you to re-generate this asset based on the 6.5 contents ?
As a quick test, I tried changing the main SimulatorSurvivorsTheme.tss to use @import url("unity-theme://default"); and it seems to restore the layout to its normal state.
Also, would you mind starting a dedicated discussion for this issue ? Thank you !
6 Likes
why did you remove 6.4 from the Hub?
(installed 6.5 but it can’t build my Android project… odd compilation error) had to go back to 6.4 latest version, that i found here Download Archive
PLESE do not remove last working version when releasing a new major
1 Like
If you want a stable version, use LTS. The whole thing with tech streams is that support is dropped as soon as the next version launched.
That aside, the archive if always there
2 Likes
Continuing here: Default.uss issue in Unity 6.5
The default theme clone was a workaround with just color changes, I can regenerate this.
Definitely on the correct path!
I currently use System.Text.Json@10.0.9 and Microsoft.Extensions.Logging.Abstractions@10.0.9. After upgrading, I’m receiving errors with duplicate source generation but also conflicting versions. Is there any way to disable and use the most recent version?
Are the game objects now created in contiguous memory?
No change to the allocation of GameObject or MonoBehaviour instances.
Is that planned for newer versions?