Search Issue Tracker
In Progress
Fix In Review for 6000.4.0a4
Votes
0
Found in
6000.4.0a3
Issue ID
UUM-122654
Regression
No
Runtime field menu in UI Toolkit Project settings shows duplicate options > “Default.tss (Default)” and “Default.tss
Steps to reproduce:
1. Create a new Unity project using the Universal 3D template
2. Open the Project Settings window (Edit > Project Settings)
3. Open the UI Toolkit tab in the Project Settings window
4. Change the "Runtime” property to “Default.tss” from “Default.tss (Default)”
5. Observe the field
Actual results: Changing Runtime field to Default.tss (Default) or Default.tss does nothing, field doesn’t update, always stays as “Default.tss (Default)
Expected results: Runtime field should update or menu item should only have one “Default.tss” selection
Reproducible with versions: 6000.4.0a3
Can’t test with versions: 6000.0.60f1, 6000.2.8f1, 6000.3.0b7 (the feature is only in 6000.4.0a3)
Tested on (OS): Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment