If you change your network adaptor from the one you used to login to the HUB, you wont be able to open any of your projects. You click on the project you want to launch, HUB closes, and the Unity Instance never launches. It just silently fails. No error dialogues etc. You have to re-launch the HUB, ensure you are on the old network adaptor and try to launch your project again.
First of all, I am really sorry about the delay of our answer. Your messages just passed under our radar.
Coud you precise the Hub version, editor version and OS you’re facing the issue.
I tried to repro on Windows, with latest hub version and switching between 2 wifi adapters and I did not manage to repro your issue.
More specifically, those are the steps I followed:
Open Hub with wifi adapter A enabled
Switched off wifi adapter A and switched on wifi adapter B
I’m not at my work station but it has happened in every version i can remember. Steps:
Connected on Adaptor 1
Open Hub
Open a Unity project (hub is now closed)
Change adaptor to Adaptor 2
Close Unity
Relaunch the hub
Open your project
Nothing happens.
I don’t know if it makes a difference but in my case I am usually on the LAN, and I disable the adaptor and enable my wifi adaptor and connect to the WAN. I am not sure if it matters whether or not I connect to the same network or a different network.
We are using WIndows, Hub 1.5, attempting to launch Unity Editor 2019.1b2. We just tested it again, and it seems like now instead of sitting idle, it relaunches the HUB. Used to be: Open Hub > Select Project > Hub Closes > nothing happens, now its: Open Hub > Select Project > Hub Closes > Hub Relaunches.
We can reproduce this on 2 separate computers at our office.
Here is a video if it in action. I launch the hub connected to the lan and launch our project. Works fine. I close our project, change to Wifi, relaunch the hub and relaunch out project. We get stuck in this loop where the hub closes and opens unity, then the hub relaunches and unity closes down. The project never opens successfully. Then I swap back to Lan and launch the project again and lo and behold it works fine.
Hi @Prodigga ,
Unfortunately, I am unable to reproduce the issue. Although, we have an idea of what may potentially be the issue.
It is possible that the license is not recognized as valid by the Editor.
One way you may check if it is the case:
Back up your license file “Unity_lic.ulf” under “C:\ProgramData\Unity” Quit the Unity Hub with tray menu and restart it once switched network.
If you are shown with license error, this will prove the validation failed due to network switched.
Sorry for the inconvenience
I can confirm this is not fixed yet, I had it happen again 2 weeks ago. So I still occasionally find myself sitting their waiting for Unity to launch because I was on Wifi instead of my Ethernet and it never launches.
@Prodigga Try going into your project’s file, into the assets folder, and into the scenes folder. You should see a Unity scene file. Click the Unity scene file to launch the Unity Editor with the scene loaded. The rest of your project files should open with it. This worked for me
@joeksy I found a temp fix from another forum but this isn’t the best one as it’s still providing issues. I’ve uninstalled Unity Hub and reinstalled on the new network card, deactivated license and activated brand new one on the new network card and I’m still getting the issue which is “Unity is already in list”.