Thread: TF2 server client timeout with map change

Not sure if this is the right forum...I took a guess that maybe the issue is lonestar related.

The past couple of days I have noticed I am getting disconnected on map changes. Cprice just had it happen to him too at the same time as me.

The exact circumstances:

1. Playing gravelpit.
2. A vote came up for nextmap. Wasn't a rtv...just the usual. Badlands won vote.
3. Round ended and map changed.
4. I got an error and was disconnected as the map change started. That also corrupted my map file when I tried to reconnect, so I had to validate my game cache to fix it.

That's really odd. I don't think it's lonestar related. Is this happening on every map change?

I have observed this also, however not just today. Until a few days ago I thought it was an error on my internet connection (which has been iffy). But it seems every so often the server will crash / dump everyone out and not show up on my list for 30 seconds. I also think this only happens on the main server. Can someone else confirm?

It happened on Top5 tonight. Should've got the time, but my mind slipped... I think it was when it changed to steel, but I'm not quite sure... It may have been when we changed from steel.

:5

I posted about this yesterday in the CRASH REPORTS thread, where its supposed to go and get no response. I confirm, it happens.

it's happened to me a few times

there was also a time when i tried to connect just as it switched and it said the server was down

Not everytime...I should have been more clear. I'd say its happened 3 or 4 times in the past couple days.

When you time out and you reconnect is the server's map now dustbowl?

dustbowl is the first map in rotation, so if it's on dustbowl it means the server crashed and restarted (hence your timeout)

Nope, it was badlands, not dustbowl...so the server didn't reboot.

But I re-reviewed my post and remembered another detail that may help.

I remember checking the nextmap early in the match, and seeing it was gravelpit...even though we were currently playing gravelpit. I thought to myself, "Dang, we are on gravelpit right now, it must have been RTV'd here and goofed the rotation. Hopefully we can vote something else in or an admin changes it."

Then, the usual vote came up to choose a map, and badlands won the vote. So then it switched to badlands.

Maybe something about it already being gravelpit, and having the next map show gravelpit earlier, then switching to badlands per the vote caused a problem?

I played later that night and didn't have any problems. But I didn't have a scenario like the one above.

So I am thinking its when:

1. Server gets rtv'd to a map.
2. That map that won RTV was going to be the next map in the cycle....so server still shows it as nextmap.
3. People vote on the nextmap late in the match.
4. Server changes and cycles past that map that was originally in the cycle, and moves on to the one people choose late in the map. (Not sure if this is how the server process/config flows...I am hypothesizing here.)
5. In that time of cycling, some people lose the connection.