Info needed for running a server.

[Panzerlang]

I ran one before, briefly, for WW2 (from home). It was never stress-tested for large numbers however so before I have another go for a WW1 jobby I need some basic info. What kind of bandwidth is needed for a 25 v 25? I have a steady 5 megabyte connection, though my wife and son share it (wife's use is mostly browsing, son's is Fortnight type stuff).

Hardware, does the server app use multi-core CPUs to any great effect or even multi-chip setups? RAM amounts...

TIA.

I've just tried (again) to create a server on this rig via the game's process. My bro can get into other servers ok but when he tries to get into mine it freezes his game and he has to use Task Manager to get out. Anyone got any clues why it's not working?

Edited October 4, 2019 by J3Hetzer

[Panzerlang]

I've been into the router and under the DNS option I've port-forwarded (internal and external) the TCP and UDP to the game's 28000. I can't find any option to specify those setting's to the game's IP number (on my PC that's 192.168.1.3) so I'm assuming such a thing isn't necessary. It still freezes my brother's game when he trys to join via the in-game dogfight browser but he can join other servers ok.

Totally stumped. "Make your own server then!" they say when complaints are made about a lack of servers. Fat fking chance with this broken sht.

[616Sqn_SpocksOddSocks]

I don't know how the listen server (in game) use multiple cores, but dserver doesn't.

 

I've noticed a lot a servers have this problem, with connecting, and I don't know if this works for listen servers, but I had this with dserver at first, but that lets you set bandwidth up and down speed limits. I found that the default upload speed was higher than my internet connection could handle, and lowering that worked. I'm not 100% certain how this works in listen servers, but if you check your "startup.cfg" file in the game's "data" folder and scroll down to this bit:

 

[KEY = network]
    available_ip = ""
    client_download_traflimit = 1000
    client_ip = ""
    client_upload_traflimit = 1000
    downloader_port = 28100
    server_download_traflimit = 1000
    server_upload_traflimit = 1000
    tcp_port = 28000
    udp_port = 28000
[END]

 

It's possible that amending the server traffic limits here might help. Those figures are from my config file, and if those are the defaults, they seem rather low, so it's possible getting in just takes a hell of a long time. Particularly as the listen server uses the larger ".mission" file rather than the smaller binary that's used by listen servers. You could try upping those to something closer to your bandwidth. (I'm presuming they are in kb/s like on dserver).

 

IP address can be added in the "multiplayer" section of the game client's settings, but not sure if that's needed. Also, you're going to want to add the port 28100 to TCP as well as 28000.

 

 

[Panzerlang]

Ok, finally got the ports forwarded correctly, brother can join but as soon as the map loads he gets:

#10009 game server connection lost

 

56 minutes ago, SpocksOddSocks said:

I don't know how the listen server (in game) use multiple cores, but dserver doesn't.

 

I've noticed a lot a servers have this problem, with connecting, and I don't know if this works for listen servers, but I had this with dserver at first, but that lets you set bandwidth up and down speed limits. I found that the default upload speed was higher than my internet connection could handle, and lowering that worked. I'm not 100% certain how this works in listen servers, but if you check your "startup.cfg" file in the game's "data" folder and scroll down to this bit:

 

[KEY = network]
    available_ip = ""
    client_download_traflimit = 1000
    client_ip = ""
    client_upload_traflimit = 1000
    downloader_port = 28100
    server_download_traflimit = 1000
    server_upload_traflimit = 1000
    tcp_port = 28000
    udp_port = 28000
[END]

 

It's possible that amending the server traffic limits here might help. Those figures are from my config file, and if those are the defaults, they seem rather low, so it's possible getting in just takes a hell of a long time. Particularly as the listen server uses the larger ".mission" file rather than the smaller binary that's used by listen servers. You could try upping those to something closer to your bandwidth. (I'm presuming they are in kb/s like on dserver).

 

IP address can be added in the "multiplayer" section of the game client's settings, but not sure if that's needed. Also, you're going to want to add the port 28100 to TCP as well as 28000.

 

 

He changed all the 1000 values to 2000 (2MB I guess), no joy. No way his conn needs that anyway. Thanks anyway dude, it was a likely fix.

Next attempt will be both of ours set to 5000.

Edited October 4, 2019 by J3Hetzer

[616Sqn_SpocksOddSocks]

Ah, I was suggesting upping those on the machine running the server rather than the one connecting. Not sure if that will help.

[Panzerlang]

We've now tried both our rigs at 5000 and 500. He finds his connection holds longer at 500 but it still disconnects within seconds. At 500 he's able to join other servers without problems.

 

The final part of the jigsaw...PING. The settings default it at ZERO, instead of something sane like 100. I set it to 300, now he can stay connected.

Shame they have that big black empty space in the 'Settings>>>Multiplayer' area when it could be filled with at least some CLUES about how to make a listen-server actually do what the MP hosting function implies it will. HMOG.?

Edited October 4, 2019 by J3Hetzer

[616Sqn_SpocksOddSocks]

Glad to hear you got it working in the end.

[Panzerlang]

I had it running from 9.30pm until half an hour ago (overnight), I saw up to eight players on until I went to bed and it ran very well.

Thanks for the input Spock.