No, the reason is that they eventually got around to fixing the problem around 1-2 years ago.
Maybe they just let it crash to push technical-unaffine users into giving up and just allow the connection and data siphoning.Īs what I have seen so far in NMS, Dying Light and so on, I don't trust them anymore. I think the reason is, while a written rule blocks the connection activity and directly, the error occurs while the other method provokes a timeout, which is silently disregarded by the galaxy.dll maybe interpreted as "no interface available". Interestingly, if I don't write the rule but just wait for the alert pop-up (it first tries to connect to an outbound IP, which I deny by hand, than it tries the loop-back, which I also deny by hand), and the game starts just fine, even though it never connected. Try googling how to set up a rule for localhost in Windows firewall.Īndreas.scholz: I have this problem currently with Planet Nomads when blocking the game via a written rule in Comodo Firewall (5.12, because all later versions suck) even when allowing loop-back zone (127.0.0.1). I also can't really have a look at it because turning the Windows firewall on would interfere with the firewall I have installed. So I do not really know how to configure it. Even though it was improved over time I have always used better firewalls. I have never used the Windows firewall because it was way inferior to any other product out there when it came out. But you still need to allow the games to connect to localhost to check whether Galaxy is there or not. If you don't have Galaxy installed you do not need to worry about that. But the Galaxy service then connects to GOG's servers to relay all sorts of information.
To be more precise they connect to the Galaxy service running on your computer. Galaxy games should only connect to localhost. In this case you aren't actually running two firewalls at the same time. I didn't know that Sphinx was just a front end for the Windows firewall. If I allow a connection the game(s) will run, if I don't the game(s) crash :( As I don't know for sure where these games are trying to connect to I'd hoped to be able to set up a firewall rule in Windows Firewall itself allowing access to localhost for each of the problem games to bypass this issue.
Everything has always worked perfectly until this Galaxy thing. by showing a pop up when anything wants to connect somewhere. I've used 'Sphinx Software Windows Firewall Control' for years with no problems as it is designed to be a 'front end' for the built in Windows Firewall helping to easily create rules, etc.
0 kommentar(er)
