Check out the image. I just downloaded Defold, and opened the tutorial project. But for some reason when I try to build it/run it, all these connection errors come up with regards to being unable to retrieve address family etc. etc.
Any ideas please?
Kind Regards,
Mr Business / Lukas
If you have any AV or Firewall software check them to see if they blocked anything.
I have allowed Defold through my Windows Firewall. And windows defender is the only type of antivirus software I have on my computer. And I am running Windows 10 if that helps. Same error still occurring…
Have you tested doing HTML5 builds? Does making bundles work?
Yeh, that doesn’t work either.
What I have realised is that, when I run as Administrator. The build DOES run.
But the errors still pop up, even though it builds…??? for some reason.
Not only that, but when I run as administrator I have to assign a new branch and it doesn’t see the other branch I just made when I didn’t run as administrator. And once I have made a new branch as administrator and then open Defold “not” as administrator and try to open the previous branch, Defold sorta stuffs up.
Hard to explain. So…
1: Defold builds correctly when I run as administrator (which is a pain in the arse…and I’d like to somehow avoid)…but still comes up with errors in console
2: Branch’s stuff up when creating new branch as administrator and not as administrator
Sounds like filesystem permissions issue then. Try to redownload Defold cleanly, and unzip it into your My Documents folder then run.
Is your Windows 10 login account is not an admin account?
Ok so I did that. And the problem was that I didn’t have Defold in my documents. I put it all the way in the Program Files. Which requires me to run things as administrator I guess.
So, now it builds without having to run as administrator. But I still get these errors, even though it ran fine…
This doesn’t happen on my mac though. Mac builds perfectly. Maybe it’s still a permissions problem??? It’s my computer, I should have full access.
The problem is that Defold modifies files within its own folder, and when Windows is more strict it can block programs from accessing or modifying files in certain locations. Generally it’s bad practice for installed programs to write to their own directory and not to the proper temporary or document folder, but Defold was made as a portable development tool and not a general consumer application.
If it works that’s good. Those error messages are unique to Defold it seems so a member of the Defold dev team would have to address them.
Is your Windows user account an admin account itself?
Ahhhhhh that makes sense. Thanks for the help man!
Umm yeh my account is an admin account.
But Windows 10 has a built in admin account for some reason which I just obtained access to (as it was inactive). But I don’t want to use that admin user for day to day use…so I guess I will have to just deal with those irrelevant error notices…although they will bug me…and hopefully this doesn’t cause problems in the future (hopefully they are addressed in future updates).
@sven, have you seen any issues such as the ones above when you tested on Windows 10?
@Mr.Business: For some reason the engine is unable to create a socket. I’ll have to look at the code but I don’t think there’s too much going on at that point which could cause a problem. You might be able to resolve the problem by resetting the TCP/IP module by issuing the command netsh winsock reset as Administrator, but if that’s the problem you should have noticed network problems with other applications as well.
Hmmm thanks for that. I reset the TCP/IP module by typing that into CMD as administrator as you said. I then restarted. But the same error messages in console still come up.
Okay, I’ve looked at the code now and there could be a problem with our SSDP (Simple Service Discovery Protocol) implementation, though if that’s the case I’m not sure why we haven’t encountered it before.
The problem is that the engine is unable to use a socket which should be bound to your local interface to broadcast a message and announce the service. For some reason an invalid socket handle is kept when we’re updating the sockets, and when it’s used later on we’re unable to identify it as either a IPv4 or IPv6 socket.
It seems as we’re not clearing the old sockets on update, so if the number of network interfaces changes it could cause a problem. I can’t explain why it would work when you run the editor from %USERPROFILE% but not from C:, but it feels as if there’s an Administrator/User kind of problem there…
Regards,
Jakob
I really appreciate your response Jakob, thanks.
Multiple network interfaces…nope. I’m using a normal laptop with normal hardware. So cross that off.
Detachable interfaces…nope. We use a router for the entire house.
Virtualisation environment with NAT…nope. We have a very normal network here.
Can I think of anything that could cause number of network interfaces to change when engine starts? Hmmm…ummm…no unfortunately I can’t.
I really don’t have a clue if its anything on my computer, or network that is causing this socket error…cause it works fine on my macbook (no errors).
I guess maybe it must be some sort of Windows 10 issue? Or back-end issue with Defold possibly?
Lukas
Just tested on a Windows build on Windows 7. Was using OS X only for a while. Maybe a regression because I’m pretty sure the notsock was not happening in previous builds. I can check if need be.
Everything seems to be working still when making builds.
INFO:ENGINE: Defold Engine 1.2.83 (1f14af3)
INFO:ENGINE: Loading data from: build/default
INFO:ENGINE: Initialised sound device 'default'
INFO:DLIB: SSDP: Started on address ...
INFO:DLIB: SSDP: Started on address 192.168.0.111
ERROR:DLIB: Failed to retrieve address family (-22): NOTSOCK
ERROR:DLIB: Failed to retrieve address family (-22): NOTSOCK
ERROR:DLIB: Failed to send to remote host, unsupported address family!
WARNING:DLIB: Failed to send announce message (-2)
ERROR:DLIB: Failed to retrieve address family (-22): NOTSOCK
ERROR:DLIB: Failed to retrieve address family (-22): NOTSOCK
ERROR:DLIB: Failed to send to remote host, unsupported address family!
WARNING:DLIB: Failed to send announce message (-2)
ERROR:DLIB: Failed to retrieve address family (-22): NOTSOCK
ERROR:DLIB: Failed to retrieve address family (-22): NOTSOCK
ERROR:DLIB: Failed to send to remote host, unsupported address family!
WARNING:DLIB: Failed to send announce message (-2)
INFO:DLIB: SSDP: Done on address ...
INFO:DLIB: SSDP: Done on address 192.168.0.111
Could you check if it’s a regression? If so its a IPv6 problem that I’ll have to look into asap 
Are full past releases stored somewhere? I don’t have an old downloaded version handy right now.
I have never seen it before, and now it seems to be “everywhere”, even here. Pretty sure it’s a regression, most likely ipv6. We should fix it monday.
The NOTSOCK problem has been resolved now and should make it to the 1.2.87 release.
The problem occurs when there is a network interface available that neither has an IPv4 address or an IPv6 address associated with it (such as a disconnected interface). The only effect of the bug has been the NOTSOCK error messages and no functionality has been negatively impacted, though these error messages has caused some unnecessary confusion.
Regards,
Jakob