Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.36f1
2022.3.22f1
2023.2.16f1
6000.0.0b13
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-67812
Regression
No
The first Panel Settings asset found gets randomly assigned when creating a new UI Document
Reproduction steps:
1. Open the attached “UITK Panel Settings Bug Report.zip” project
2. Create a new UI Document (GameObject → UI Toolkit → UI Document)
3. Click on the created UI Document
4. Observe the assigned “Panel Settings” in the Inspector
Expected result: There is a settings menu that allows to set the default Panel Settings that get assigned to all new UI Documents
Actual result: One of the three of Panel Settings assets in the project gets randomly assigned
Reproducible with: 2021.3.36f1, 2022.3.22f1, 2023.2.16f1, 6000.0.0b13
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Issue appears because when {{AssetDatabase.FindAssets("t:panelsettings", "Assets") }}is called the first Panel Setting found - gets assigned
- More of a productivity issue, since it takes extra steps or time to assign the correct settings every time a new Document, is created
- Issue is more visible when testing with different projects since the same project would usually assign the same setting on every version
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
We do recognize the problem and the impact on your workflow, but this will be tracked as a feature request and not along the bugs.