Ok, so I had 5.5 installed, and it all worked fine a couple of weeks ago when I last used it.
I ran it today, and even though the initial menu shows, selecting a project closes the window and nothing happens. I can see the Unity processes die off a few seconds later.
So I upgraded to 5.6, activated everything, got the usual message saying my game needed to be converted, so I select to continue, and nothing happens. Same as above.
I try a new project, and the same thing happens again.
One difference, is Win10 Creators edition was installed a few days ago. I had some annoying problems at the time (main one was 1.5 hours remote access by MS tech to bring back pretty much 99% of all text which was completely missing after update), so I’m guessing this is probably the issue.
Anyone else having issues with Win10 creators edition and Unity? If so, then any advice on how to fix this? Hopefully worse case is un-install and re-install Unity (although I do have another version installed for an older project that won’t work on > 5.3.5).
I upgraded to the Creator’s Update with no issues. I’d recommend re-installing your Unity installations. Note that you can get older versions of Unity here: Download Archive
I un-installed 5.6, and then re-installed. Same issue. The 5.3.5 version of Unity I have for an old project still works fine, but I’ve noticed even it fails when creating a new project (5.6 & 5.3.5 create the project directory and some files, and then that’s it. Nothing opens, and Unity dies off quietly). But my old project still opens and runs fine in 5.3.5.
My new project is in 5.5.1, so I may re-install that, but then it didn’t work before installing 5.6 either (it worked before Win10 Creators update).
Stuff it, I think I’ll put the old project onto an old laptop, and then wipe Unity completely off this laptop, before installing 5.6 from scratch and not having another version of Unity (5.3.5) installed as well. Pain, but there you go…
Out of interest, is there a Unity log file that may shed some light on this?
Hmm. I had a load of stuff loaded with my day to day workload (VirtualBox, Pulse Secure etc etc). So I thought at the end of the day I’d restart and see how it went. Note the editor.log file didn’t show any issues that I could see.
Nope still stuffed. But I ran it in safe mode, and it created a new project perfectly fine and opened the editor. Close Unity, re-open the new project. All good. Ok. Restart properly and… it’s all stuffed again. Good stuff though, as I can start killing things until it works. Must be something that’s updated in the last week. Possibly not Win10 CE, but then I haven’t manually updated anything else…
Found the problem. It’s actually something I mentioned, just as a small note, when reporting the problem directly to Unity.
Basically the NVidia control panel was set to use the NVidia card (Optimus settings) for Unity. Once I set this to Integrated graphics (Intel), then Unity loads up the editor fine.
Obviously an issue there with NVidia cards, or at least using Optimus video card switching, that wasn’t there with older Unity versions.
Well that’s a terrible, terrible solution as you shouldn’t be limiting yourself to Intel HD. When you start working on more taxing projects you’re going to need your Nvidia card. Did you update your Nvidia drivers? I use GEForce Experience to update them right away, the ones Windows gets are sometimes a bit old.
Also, did you mean “Optimal settings”? Because Nvidia has Optimus technology as well.
Yep, not great. Luckily my latest project is a simple enough 2D game designed for mobiles, so Integrated is fine for now. A bigger project we have would probably need the NVidia card, but as the 3D artist is now really busy with actual 3D professional film related work, then our hobby game has been parked. Happy-ish coincidence…
Yes, NVidia is completely upto date on the drivers, with GeForce Experience, as is Win10 itself.
No, I meant Optimus. Years ago I had GeForce Optimus settings setup so Unity used the NVidia card (used to be Integrated as default for automatic settings), which worked fine. Now it seems that these settings have NVidia as default for automatic settings. Turning it back to specifically use the Integrated Intel card gets it all working again, although obviously not ideal.
Quite amusing, as now I have Unity setup as Intel integrated card, and VS setup to be NVidia. A little while back I found VS to lock up quite badly for upto 30 seconds at a time. It happened in Unity projects as well as standalone C# projects (I also use it for work). Turned out I needed to setup Optimus to use NVidia for VS. Then it worked fine… Sigh…
