Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1174387
Regression
No
[Hub] Cannot manage multiple installations of the same Unity version and launches wrong binary
[Hub] Cannot manage multiple installations of the same Unity version and launches wrong binary
If the user needs to work with multiple copies of the same Unity version (different builds for example), Hub will be unable to manage this and their work can be launched in the wrong binary which could be potentially destructive and confusing.
Steps to reproduce-
1) Install a recent copy of Unity and open it so that it launches the Hub
2) Install another copy of Unity of the same version as before, but another build version and open it so that I launches the Hub
3) From the Hub, attempt to create a new project with that version
4) Observe that the user cannot manage the multiple versions in the Hub and that it will launch (often) the version that is not intended
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
- [Android] Particles aren't rendered when the shader "Particle/Standard Unlit" or "Particles/Standard Surface" is used on a Material
- Crash on nvoglv64.dll when opening a project
- [RenderGraph] [CameraStacking] Passes are failing when CameraStacking and RG are enabled
- Physics and Raycast have different behavior when enum is exposed in the Editor
- TextField's text is mixed up and overlapping when "Noto Sans-Display" font is used
Resolution Note:
Feature request added and in motion. Closed as bug.