Search Issue Tracker
Active
Votes
2
Found in [Package]
3.0.1-Hotfix
Issue ID
HUBX-744
Regression
No
Unity is not launching from the Hub when having an unstable internet connection
How to reproduce:
1. Open Unity Hub
2. Run any project
Expected result: The Project launches
Actual result: Unity's icon appears for several seconds, then disappears. The Project never launches
Reproducible with: 3.0.1
Note: Unstable internet connection is required to reproduce
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
- "Unsupported texture format R16 for a swizzle" error and texture is not correctly rendered when using texture Swizzle and reimporting texture asset
- Tab order is incorrect after re-ordering
- [Ubuntu] Red squares instead of ticks in dropdown options
- Multiple simultaneous input with the touch screen sometimes leaves button in not default state
- Crash on ShowDelayedContextMenu(bool) when changing the Size options of a Visual Element in the UIToolkit Inspector
Gillissie
Sep 14, 2022 17:46
This is still an issue in Hub 3.3.0. Why isn't this seemingly easy fix getting done?
Gillissie
Apr 27, 2022 20:32
Still an issue in Hub 3.1.2.
Gillissie
Mar 30, 2022 06:02
This may be the same underlying issue that's causing https://fogbugz.unity3d.com/default.asp?1413577_vum8c85uhviq4p6a
Ridiculous workaround: Disconnect computer from the network, launch Hub, launch Unity, reconnect to network.
This means Unity is cool with launching if there is no internet detected, but refuses to launch if there's internet detected, but can't reach the mothership successfully. The same action should be taken in both situations (launch Unity!). Why is Unity calling the mothership at that point anyway, if it works without internet?
Gillissie
Mar 22, 2022 21:55
Unity should never rely on an internet connection to launch. Using bad internet like Hughesnet randomly makes it so I can't even launch Unity, and I can't even work.
Gillissie
Mar 18, 2022 20:46
This is still an issue in Hub 3.1.1.