These can block the connection to our servers. License issues tend to relate to a connectivity issue, this could be due to the following:ġ) You have a firewall or proxy in place. I'm so sorry to learn you are having these license issues, I understand how frustrating this must be. Thank you for getting in touch, my sincerest apologies for the delay in response! Today, that Unity_lic.ulf file was still there, and with the same timestamp as yesterday, but when I opened up the Hub again, Im back at the starting point I have to 'reauthorise' the Hub, I still cant launch any version of Unity from the Hub, and when I launch a version of Unity standalone, I was asked to 'reauthorise' that as well, and my Unity_lic.ulf file has been replaced with a new one. I also checked my C:\ProgramData\Unity and there was a Unity_lic.ulf file there timestamped to when I 'reauthorised'. Note that I couldnt launch any of these from the Hub, so had to launch each one directly, and even though I'd just 'reauthorised' the Hub, I had to 'reauthorise' the first one I launched. So Im not being asked to log in, but I do have to go through other steps to 'reauthorise.'Īt that point I installed the latest 2017.4, the final 2018.1 and the 2018.2 beta from the Hub, downloaded some asset store updates in 2017.4, and created a couple of empty test projects, one each for 2018.2, and filled them with packages from the new Package Manager (which needs a checkbox'd 'load selected' option by the way, one by one is annoyingly primitive and slow). Yesterday when I responded in this thread, the Hub had opened with the the 'machine identification is invalid' error message that JackPS9 links a screengrab of above, and was prompted for license type and the three-option income question associated with the Personal license but not my user account details. So to be more specific, Ive waited a day and gone through the whole process again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |