You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set up a Dominatrix dedicated server on a linux machine. The server is externally visible as I tried to connect to it using vanilla Sin (run from a Windows 10 machine) and the game connected properly (as in: recognized the address), but the server rejected the client (and indicated it in the console log) because of the version mismatch.
Then I tried to connect using Dominatrix (from the same Windows 10 machine) and unfortunately the game was stuck at repeated attempts to connect. The connection attempts did not seem to reach the server at all (no client connection attempts were logged, unlike with the vanilla version). Vanilla Sin automatically asked me about adding an exception rule to the Windows Defender Firewall, where Dominatrix did not, so I added the exception manually, but it yielded no result.
One thing that caught my attention was that upon issuing the initial "connect" command I received the following messages in the console (maybe they are relevant):
Thanks for the report. I never actually tested the Dominatrix server from a Windows client. I'm not sure why it fails, since I copied a lot of the Windows netcode for the Linux code, which did work. I'll take a look at this, but it may take some time since I don't have quick access to a Windows machine.
I set up a Dominatrix dedicated server on a linux machine. The server is externally visible as I tried to connect to it using vanilla Sin (run from a Windows 10 machine) and the game connected properly (as in: recognized the address), but the server rejected the client (and indicated it in the console log) because of the version mismatch.
Then I tried to connect using Dominatrix (from the same Windows 10 machine) and unfortunately the game was stuck at repeated attempts to connect. The connection attempts did not seem to reach the server at all (no client connection attempts were logged, unlike with the vanilla version). Vanilla Sin automatically asked me about adding an exception rule to the Windows Defender Firewall, where Dominatrix did not, so I added the exception manually, but it yielded no result.
One thing that caught my attention was that upon issuing the initial "connect" command I received the following messages in the console (maybe they are relevant):
WARNING: UDP_OpenSocket: socket: WSANOTINITIALISEDWARNING: UDP_OpenSocket: socket: WSANOTINITIALISEDWARNING: UDP_OpenSocket: socket: WSANOTINITIALISEDWARNING: IPX_Socket: socket: WSANOTINITIALISED
WARNING: IPX_Socket: socket: WSANOTINITIALISED
WARNING: IPX_Socket: socket: WSANOTINITIALISED
The text was updated successfully, but these errors were encountered: