Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X
Fixed in 6000.4.0a1
Votes
0
Found in
2021.3.55f1
2022.3.66f1
6000.0.56f1
6000.1.16f1
6000.2.2f1
6000.3.0a6
6000.4.0a1
Issue ID
UUM-115655
Regression
No
Unclear error pop-up appears when loading incorrect preset from disk
*Reproduction steps:*
1. Create a new project
2. Save Unity Toolbar preset to file (right click on Main Unity Toolbar > Preset > Save Preset To File…)
3. Open Overlay Menu by clicking on Scene window kebab menu (Overlays > Overlay Menu)
4. Click on dropdown selection and select “Load Preset From File…”
5. Select Unity Toolbar preset file and observe
*Actual result:* “Trying to load an 0 preset with the name 1. This preset targets the window type 1 which isn’t valid for this window.” warning message pops up
*Expected result:* Warning message with clearer explanation pops up
*Reproducible with:* 2021.3.55f1, 2022.3.66f1, 6000.0.56f1, 6000.1.16f1, 6000.2.2f1, 6000.3.0a6
*Reproduced on:* Windows 11
*Note:* It’s unclear what the numbers mean, using words instead of numbers would make the message easier to understand
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment