Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.6f1
6000.4.0b6
6000.5.0a5
Issue ID
UUM-133850
Regression
No
Menu bar list orders change when Domain Reload is performed
How to reproduce:
1. Create a new project
2. In the menu bar, observe the 'Component > Mesh' sub-list order
3. In the Project window, create a new script to trigger a domain reload
4. Observe the order of the list from step 2
Actual result: The sub-list order changes, moving the “Legacy” item to the top
Expected result: The sub-list order does not change
Reproducible with: 2023.1.0a3, 6000.0.66f1, 6000.3.6f1, 6000.4.0b6, 6000.5.0a5
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Item order changes in the Component lists, Mesh, Rendering, Scripts, UI (Canvas), Visual Scripting and Input sub-lists within the Component list as well as Burst sub-list within the Jobs list
- Item order does not change in the Add Component list within the Inspector window
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.