Quake III - WiFi LAN Packetloss

Soldato
Joined
3 Apr 2007
Posts
3,438
Location
Manchester
Hi All,

Wondering if anyone can offer some advice, I have 3 PC's connected to a Netgear Wireless Router, 2 are connected via WiFi and 1 is connect via RJ45.

The PC connected via RJ45 is running a Quake III Listen Server, and the other two are connected to it, all seems fine until after about 5mins the packetloss on the 2 connected via WiFi gets that bad the game is unplayable. I have tried disabling QoS as suggested on another forum, but doesnt seem to help at all.

Anyone any ideas? I know Cabled connections for all machines would be better but its just not possible :(

Thanks
 
What signal level and connection speed does the wireless pc get to the router?
 
Duke said:
What signal level and connection speed does the wireless pc get to the router?

One of them is getting 85% the other is getting 100%, but the packetloss is happening at exactly the same time on both PC's
 
It's going to be very hard to get a game like Quake to run OK on wireless. I played EQ2 on wireless for a while and it was OK - but that's the kind of game where packet loss and a bit of lag doesn't spoil the experience too much. With the Quake style games tho you tend to notice every single dropped packet. It could be a few things causing your problems - microwave oven, cordless phones near by, etc. I would post in the networking forum (or get a mod to move this thread...) as there may be some tweaks you can try and I'm not an expert by any stretch :) But usually, wireless and fast-paced shooters don't mix.
 
try using the packetdup (sp?) setting, I believe it doubles the amount of packets sent to the server as a form of error correction. Also what is your sv_fps setting? 25 should be about right. I know that I used to have a few problems with q3 servers becuase of that setting. Is it a punkbuster enabled server?
 
Nope punkbuster is disabled, seems a million times better when one of the Wireless PC's host the game rather than the wired one.

Thanks for the tips I will try those.
 
Check all your sv_ vars - might be overloading the connection with packets from the server...

Also check the client snaps, maxpackets and rate - check your lagometer...

Probably best to only connect only one client to the listen server for testing - do you get the same problems under a dedicated server?

lawrence

ps3ud0 :cool:
 
Last edited:
Back
Top Bottom