next »

[Please Support Us!]

Please Support Us!

Please help keep (=WDG=) alive

• Server rules
• Forum rules
• Join us
  
• Clan members
• About the clan
• Server stats
• WDG YouTube Channel
• WDG Downloads
• IRC Webchat

Steam groups:

• WDG community
• WDG clan group
• WDG Battlelog Platoon

Our allies:

• [NuB] TF2 clan
• Velocity Gamers Hub
• Destination Gamer

GoG Links:

• Wix Discord
• Wix IRC channel

TF2 Links:

• Official TF2 Blog
• TF2 Steam Forum
• The Fort 2

October 2025

Mo	Tu	We	Th	Fr	Sa	Su
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31
	Birthdays
Chaos (40)
	Upcoming Events
Upcoming Birthdays: Chaos (40)

[Twiggeh]

So i've been having this issue for quite some time and I think i've finally tracked some reproduction steps. The admins might know what I'm talking about, you know, when I message you asking to boot me off cos I haven't connected properly, that ol' chestnut.

Anyway - if I connect to WDG outside of TF2, i.e. the game launches and connects automatically, all's well.

If I go in game and connect via the console (if the server is full) or just manually in-game (and it's the first server i've connected to since launching the game) it hangs at "Sending client info" forever. This seems to happen with any server I join. If i've played on a server beforehand, then it connects just fine.

Any thoughts?

[Hzza]

Have you checked the SPUF? I'm pretty sure thats quite a common problem, but for the life of me can't remember what the cure is...I'll have a nose around when I get home because I'm sure I've seen the solution somewhere .

[Cheez]

Are you on bt?

[Mr Chug]

I occasionally get a similar thing, and not just with WDG. I find if I cancel it, then reconnect I'll get my name (1) and won't be connected to steam (so can't access loadout), then if I disconnect again and reconnect it'll all be fine. Haven't noticed any difference from launching out of game, but then again I haven't been looking.

[claws]

I'd probably cache verify/ clean TF2 folders out but keep gcf's.

[Officer Dibble]

I occasionally get a similar thing, and not just with WDG. I find if I cancel it, then reconnect I'll get my name (1) and won't be connected to steam (so can't access loadout), then if I disconnect again and reconnect it'll all be fine. Haven't noticed any difference from launching out of game, but then again I haven't been looking.

I have the exact same thing.

When my new pc arrives I'll do a fresh install of win 7, steam and TF2 to see if that makes any difference to this or my choke problems.

[Cheez]

Don't want to kill your hope dibble but it didn't help me

I think it is a bt thing, specifically a homehub thing, I had this exact problem but when junta lent me his netgear router it stopped happening.

Didn't help the choke though

[claws]

If it's different depending on how you launch it seems unlikely to be an ISP thing?

[Twiggeh]

Yeah - what Claws gets is pretty much what I get too. And yeah sadly I am on BT with a homehub. :/

[Mr Chug]

Ah, I'm not, guess it's a different issue.

[Officer Dibble]

I'm not on BT either, something fishy is going on here.

[Cheez]

Hmm I'm not sure then but it literally stopped happening the second I changed my router.

[Captain Valentine]

Have you set your router to send all TF2 traffic to your PC, helped for me back when I was using a BT homehub.

[Officer Dibble]

I set up port forwarding on my router, which helped with my choke issues but not with the hang at sending client info.

[scroggage]

Recently I've been getting a complete loss of connection every time I join any TF2 server. As in, all my internets die.
Then I disable the adapter, re-enable it and everything works fine again. I have no idea why this is.