"server ping timeout (>30.0000sec)"

[ericinexile]

I've been getting this when I am on some, but not all, servers. First started happening around the time of the first DCS update and happens most often on 3rd Sqdn, and STP (Spare Time Pilots) servers. I'm sure the problem is on my end but if anyone else has encountered this or has a solution I'd really appreciate the help. Pings for servers I join are always less than 100.

 

Thanks and regards,

 

(Edit: I should add that I am connected by cable to a Belkin Router)

Edited December 23, 2009 by ericinexile

[Boberro]

It means that your BS is frozen for more than 30 seconds. Example I get it often, cos when I click fly cockpit loads much longer than 30 seconds and I must reconnect to load it faster. In my case it is due to low ram amount. I have only 1 GB. There is in config file entry which should be responsible for it... but doesn't work, or work only when you are server. So....servers should set higher value IMHO.... 60 seconds ;]

[ericinexile]

Hmmm.

 

Thanks Boberro. I seem to get it during long flights enroute to a target area when not much is happening. That might also mean that I am no longer communicating to the server, but because there is nothing in the "world" with which to communicate, I don't notice. The last time it happened, I spent 10 minutes flying alone up a valley when another player zoomed by. I decided to fly to the top of a ridgeline to get a good view of any action he was about to attract. The very instant I popped flares at the top of the ridge, I was directed to the Client screen and given the "timeout" messege above. Maybe I should pop flares every 29 seconds so that the server knows I'm still around.

Edited December 23, 2009 by ericinexile

[Boberro]

You can't be kicked (timed out) for only flying, in your case I think connection has broken for while.

 

But often this timed out messages appear when you load from briefing to cockpit. System must load cockpit, textures ect. It takes while until it loads it into RAM and if Windows has to use swap memory time increase beyond 30 seconds and we have message then.

 

I wonder why during cockpit loading BS doesn't contact to server and vice versa.

[AustinN360]

I've been getting this when I am on some, but not all, servers. First started happening around the time of the first DCS update and happens most often on 3rd Sqdn, and STP (Spare Time Pilots) servers. I'm sure the problem is on my end but if anyone else has encountered this or has a solution I'd really appreciate the help. Pings for servers I join are always less than 100.

 

Thanks and regards,

 

(Edit: I should add that I am connected by cable to a Belkin Router)

 

One tip. Get a new router! Belkins are notoriuos for their really poor signal quality. Especially the F5D7230-4 model. The one I used to use had an 88% packet loss which is really bad for multiplayer. You can check your signal quality by running a test at http://www.pingtest.net for confirmation.

[ericinexile]

Thanks. My next step is port fowarding but haven't been home to test it.

[ericinexile]

Port Forwarding didn't correct the problem. Plugging directly to the cable modem DID correct it (so far, as of one day of testing). Looks like the Belkin was in fact the culprit. Thanks for all the suggestions!

[Panzertard]

Just a quick heads up.

I think you can get that message when your ping spikes over 300ms for periods. I've experienced it first hand at certain servers - regular ping was about 200ms, somethimes a spike or five notched it up - and I would get "server ping timeout > 30.00000sec"

 

So it may be a problem from where you're sitting to the servers you're playing on. If thats the case it's nothing much you can do.

 

If you're on a wireless connection you may try to improve it, because wireless connections tends to give such issues more frequently than cabled conneciton (in your house - or your ISP).

[ericinexile]

So far direct-to-modem is working fine but I'll continue to test.

[Boberro]

Last time on 3Sqn during loading DCS demanded more RAM, as I din't have more it had ti use swap file. After loading to server I entered to cockpit and startup everything... after while I've been kicked with 120 second notice. Not 30 seconds...so either 3sqn has changed value... or my settings finally has worked.

[Grimes]

I'm not sure where that setting would be. However I have checked the network logs and there are lines upon lines of

 

NET: 64541.690000: kicking 7: ping timeout exceeded (>30.000000s)
NET: 64541.730000: kicking 7: ping timeout exceeded (>30.000000s)

 

I'm honestly at a loss to convert the "NET :xxxxx.xxxxxxx" time to something I can actually measure. My best guess is that it appears to be the time since the server had started.

 

 

That said, looking at the log files and comparing which mission was loaded with clients in game. Bob it looks like you got kicked for teamkills. The server network log shows you were kicked, however it fails to remove your client ID and are therefore "in the game". 2 Minutes later it has a whole slew of "NET: 76405.485000: kicking 4: ping timeout exceeded (>120.000000s)" errors appear.

 

 

 

ericinexile, what name are you playing under when logged into BS?