I am very excited by today’s announcements. I have Unity 5 Personal installed on my machine (Windows 8.1) and when it starts after creating a new 2D project I get an error on the console that states:
Socket: bind failed, error: An attempt was made to access a socket in a way forbidden by its access permissions. (0)
Any idea on how to fix it?
I have Unity 4.6.1 installed currently in another folder and it starts without any error such as this. It doesn’t seem to keep me from working but thought it should be mentioned. Hopefully there is a work around.
I’m on OSX 10.6.8, 64bit. The minimum requirements state Unity 5 Personal is for 10.6+ , but the installer assistance says it can only install to 10.8+.
I downloaded the editor by itself, and when I click on the launch icon on the dashboard, it jumps up and down for a long time, but doesn’t start the editor.
It seems to be running as a process on the mac, because I can quit it and even force quit it.
After installing Unity 5 on OSX 10.6.8, when I click on Unity App the icon jumps up once, and that’s it. I don’t see the editor at all. Activity monitor says Unity is running on 2 threads and using up 50.2% of CPU process and just 29.6 MB of memory.
Well, I sucked it up and upgraded from OSX 10.6.8 to OSX Yosemite.
The problem is now gone. They did said it in the minimum requirement that Unity requires OSX 10.8+…
I now have the same problem, I didn’t have this before.
I opened one of my old projects that I made in 4.6, after I closed the project and opened my current Unity 5 project, I got that error.