Hard Light Productions Forums
General FreeSpace => Multiplayer => Topic started by: ksotar on October 17, 2018, 09:59:23 am
-
Now it is my time to ask questions :)
Is there a way to do it? I want to be able to have standalone, but also to connect to it from the same PC if there will be need.
I now that I can make them to use different ports, so they will start normally (without socket/protocol is in use error). But then they will not see each other, logically enough.
I can change something in the source code, if someone has the idea what it could be.
-
If you only tell the client to use a different port, it should work... If it doesn't, what kind of error do you get?
-
It works but then client doesn't see that server, that seems logical enough.
-
Oh, right. You're not using a tracker (PXO/FS2NetD) but local discovery. I guess that won't work with different ports.
Hm... I guess you could pass the server port to the client? IIRC there was a flag or multi option for that. Not sure though.
Anyway, local discovery doesn't work with different ports and there's pretty much no way to fix that due to how it works.
-
>pass the server port to the client
can you elaborate a bit more on that?
-
You should be able to use the -connect flag (http://wiki.hard-light.net/index.php/Command-Line_Reference#-connect) for that. Like this: -connect 127.0.0.1:95541
-
That looks feasible, I'll try, thanks!
-
Well, IDK what I've changed, but I ran client with
-port 7809
and client just saw the server. Maybe last time I tried the other way around and with no luck. So the problem is solved, but the key provided by you is nice to know as well.
-
And
-connect
led to this. Maybe I'll have time someday to fix this.
[attachment stolen by Russian hackers]