Hello,
I hope this is the right place to post this.
I’ve been using Unity 2019.4.14.f1 and Unity 2020 (sorry, uninstalled and forgot the specific version) for several weeks. I replaced my router and the wireless adapter last weekend, and since then I have been unable to open anything in Unity (not sure that it is related, but it’s the only difference I can think of).
No matter what I’ve tried, I get the same result – the splash screen gets to Resolving Packages and then just closes out:
Here’s what I have tried so far:
- Rebooting
- Updating Nvidia graphics driver
- Deleting Packages folder from one of the projects and trying to reopen
- Uninstalling 2020
- Installing new version 2019.4.16f1
- Opening old projects
- Creating new projects
- Activate new license, log out of hub, log back in
- Uninstall/reinstall Hub
I can’t think of anything else that has changed other than the new wireless adapter. Any suggestions? The one thing I see in the info-log.json is:
{"moduleName":"LocalProject","level":"info","message":"[ 'openProject projectPath: I:/Users/Mario/MyFirstOculus, current editor:',\n undefined ]","timestamp":"2020-12-18T21:47:47.786Z"}
{"moduleName":"RestEvent:Project","level":"info","message":"[ 'onProjectOpen data:',\n { projectPath: 'I:/Users/Mario/MyFirstOculus' } ]","timestamp":"2020-12-18T21:47:47.786Z"}
{"moduleName":"LaunchProcess","level":"info","message":"[ 'child process exited with code 1' ]","timestamp":"2020-12-18T21:47:58.712Z"}
Didn’t realize I left this out yesterday – I’m running Windows 10 Home.
I’ve also tried the following since the original post:
- Switching back to the original wireless adapter
- Complete uninstall and reinstall of editors and Hub
When I create a NEW project, it closes at Importing Scenes – it gets to Done, then closes out the splash screen. I was able to install Hub and 2019 on a different computer (it’s just not a very good one for Unity).
Here is what I see in the info-log.json when trying to create:
{"moduleName":"WindowManager","level":"info","message":"[ 'New Project Window is called for editor 2019.4.16f1' ]","timestamp":"2020-12-19T17:29:23.764Z"}
{"moduleName":"LocalProject","level":"info","message":"[ 'createProject projectPath: F:\\\\Users\\\\brain\\\\Unity2019\\\\PleaseJustWork, current editor: ',\n undefined ]","timestamp":"2020-12-19T17:29:53.052Z"}
{"moduleName":"RestEvent:Project","level":"info","message":"[ 'onProjectCreate data: ',\n { projectName: 'PleaseJustWork',\n projectDirectory: 'F:\\\\Users\\\\brain\\\\Unity2019',\n projectType:\n 'F:\\\\Program Files\\\\Unity\\\\2019.4.16f1\\\\Editor\\\\Data\\\\Resources\\\\PackageManager\\\\ProjectTemplates\\\\com.unity.template.3d-4.2.8.tgz',\n selectedPackages: [ ],\n defaultScene: '',\n organizationId: undefined } ]","timestamp":"2020-12-19T17:29:53.054Z"}
{"moduleName":"LaunchProcess","level":"info","message":"[ 'child process exited with code 1' ]","timestamp":"2020-12-19T17:30:21.746Z"}
I’ve finally got this resolved – I found the other logs under AppData\Unity and saw it was failing at trying to access anything under c:\Users\AppData\Local\Unity. I went to check permissions on that folder and saw that it had the little shortcut icon on it, like it had become a symlink to somewhere else. I couldn’t open it by clicking on it, so I deleted it. After deleting, I still had to reinstall one more time in order for it to create files under cache, packages, etc, but after that it is finally working again. I’ve re-enabled my firewall, virus scanning, old network adapter, everything is working as it should. If anyone sees this weirdness in the future, you may want to check under C:\Users[Profile]\AppData\Local\Unity and :\Users[Profile]\AppData\Roaming\Unity. Ultimately it’s the logs there that showed the problem.
1 Like