Gaming over wireless

S

]SK[

Guest
Ive been testing wireless for our company who is looking at putting (a) game server(s) on a wireless network for gamers to use their wireless broadband connection to erm... game.
I currently have an ADSL connection at home with me connecting to it via wireless with 100% Signal Strength and 100% Quality (It is like 3 inches away from other wireless product. Now during gaming the game seems fine but after a while I notice nades and other things kill me when im out of range of them. EG nade kills me when ive blatently gone past it.

Is this me or anyone else get same kinda thing. I mean with decent replies why should that be?

C:\>ping 192.168.1.100

Pinging 192.168.1.100 with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64

Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
E

Embattle

Guest
I have a wireless network connecting two Laptops but I've never used wireless for gaming, although I wouldn't really want to tbh. It may prove nothing but how about trying a ping with larger packets?
 
X

Xage

Guest
a m8 got a wireless connection and got connection intterupts for a few seconds every minute, i wouldnt know why, but wireless seems bad for gaming to me because of this
 
S

]SK[

Guest
Code:
C:\>ping 192.168.1.1 -l 1200 -t

Pinging 192.168.1.1 with 1200 bytes of data:

Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=11ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=11ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=11ms TTL=250
Reply from 192.168.1.1: bytes=1200 time=10ms TTL=250

Ping statistics for 192.168.1.1:
    Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum =  11ms, Average =  10ms
 
S

]SK[

Guest
Other games that arnt ping critical of course are ok.

Dialo2, Priston Tale etc
 

Users who are viewing this thread

Top Bottom