A-Net ~ Biting off more than they can chew.
Patrick Smit
Frames per second has only to do with your hardware (and other software if it clogs the system), nothing with net connectivity
Firebaall
lol @ all the bitching and finger pointing......
Take that IP from the ping window, and run a traceroute on it. If the MS jump starts at Anet's servers, then carry on with the rant.
If not, stop being a jerk. Post a pic of the traceroute. If you don't know how to perform a traceroute, ask here or look it up on google.
Take that IP from the ping window, and run a traceroute on it. If the MS jump starts at Anet's servers, then carry on with the rant.
If not, stop being a jerk. Post a pic of the traceroute. If you don't know how to perform a traceroute, ask here or look it up on google.
phil_carter
have you tried using wired instead, i think a-net said in the support that wireless is not advised as you can miss packets.
Another thing you might try is updating or rolling back the driver for your wireless card, i had a huge lag problem a few weeks ago and found that it was because windows had changed the driver to one that sucked, rolling back solved the problem.
or perhaps one of your neighbours is stealing your connection and running multiple intensive tasks on it.
Another thing you might try is updating or rolling back the driver for your wireless card, i had a huge lag problem a few weeks ago and found that it was because windows had changed the driver to one that sucked, rolling back solved the problem.
or perhaps one of your neighbours is stealing your connection and running multiple intensive tasks on it.
Theosebes
Above all, get tech support on the issue. They can help you track down the cause and eliminate it. Don't just complain, do something about it!
SotiCoto
Quote:
Originally Posted by Patrick Smit
Frames per second has only to do with your hardware (and other software if it clogs the system), nothing with net connectivity
|
Quote:
Originally Posted by Firebaall
Take that IP from the ping window, and run a traceroute on it. If the MS jump starts at Anet's servers, then carry on with the rant. If not, stop being a jerk. Post a pic of the traceroute. If you don't know how to perform a traceroute, ask here or look it up on google. |
Quote:
Originally Posted by phil_carter
have you tried using wired instead, i think a-net said in the support that wireless is not advised as you can miss packets.
Another thing you might try is updating or rolling back the driver for your wireless card, i had a huge lag problem a few weeks ago and found that it was because windows had changed the driver to one that sucked, rolling back solved the problem. or perhaps one of your neighbours is stealing your connection and running multiple intensive tasks on it. |
AND... nobody is stealing the connection since ours is protected.
.... though I neglected ironically to mention that my "secondary" connection is the neighbour's unprotected link that they practically don't do anything with (I suspect they have it just for checking e-mail or something), so I just eat their bandwidth in emergencies (no scruples).
Theosebes
Quote:
Originally Posted by SotiCoto
My wireless connector is a UBS-connected external deal... and I've never changed the driver on it.
|
Quote:
Originally Posted by SotiCoto
Wired isn't a choice since it is my flatmate that organised the whole thing
|
Quote:
Originally Posted by SotiCoto
(and actually gave me a whole talk about how wireless has less resistance and thus faster than cable...
|
Kuldebar Valiturus
General and/or more specific tips for reducing/solving lag problems are great, flamefully arguing amongst each other...is not so great.
-CLOSED-
-CLOSED-