Search Issue Tracker
Fixed
Fixed in 6000.0.60f1, 6000.2.9f1, 6000.3.0b6, 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
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
- "Too many sprite tiles on Image" error is spammed in the Console when editing Pixels Per Unit Multiplier on a Tiled Image Type for Scroll View
Add comment