Search Issue Tracker
Fixed in 2021.3.33f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0b16, 2023.3.X
Votes
0
Found in
2023.1.4f1
2023.2.0a23
Issue ID
UUM-42246
Regression
No
Preset Window selection does not match when switching tabs
Steps to reproduce:
1. Open attached project "PresetBug.zip" and scene "SampleScene"
2. In Hierarchy window, select the "Cube" GameObject
3. In Inspector window, select the Mesh Filter Component and open the Presets window
4. In Presets window's "All" tab, select "Assets/MeshFilterA.asset"
5. In Presets window, switch to the "Project" tab
6. Observe the currently selected Preset
Expected result: The MeshFilterA Preset remains selected
Actual result: The MeshFilterC Preset is selected, due to it having the same position in the "Project" tab's list as MeshFilterA did in the "All" tab's list
Reproducible with: 2023.1.4f1, 2023.2.0a23
Could not test with: 2021.3.28f1, 2022.3.5f1 (Outdated Presets window)
IMPORTANT Note:
- this is not a Preset Window specific bug. This is a Search Window bug (hence why backports were created up to 21.3). The search window would retain the same "selection indices" when you were clicking on tabs.
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 2023.3):
We try to sync items being selected when user switch tabs. If an items doesn't exist in the new tab, we discard it from selection.
Resolution Note (fix version 2022.3):
Fixed in 2022.3.13f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.33f1