Search Issue Tracker
Won't Fix
Votes
1
Found in
3.16.3
Issue ID
UUM-137010
Regression
No
Only one project opens when quickly launching two projects from Unity Hub
How to reproduce:
1. Open Unity Hub
2. Open a project
3. Quickly try opening another project immediately
4. Observe the outcome
Actual result: Only one project opens
Expected result: Both projects open, without any delay
Reproducible with: 3.15.4, 3.16.0-beta.2, 3.16.3
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- FBX Exporter incorrectly exports quad topology when exporting some meshes
- OS drag and drop animation acts as rejected when dropping a Shader Sub Graph into the Shader Graph even though it is added
- Selected scenario changes when using the Save shortcut in the Configure Play Mode Scenarios window
- Unable to deselect variables in Graph Toolkit when clicking below or above the element
- "Duplicate item named ... encountered while searching the Item Library" warning persists after renaming the variables in Graph Toolkit
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:
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.