i saw some one mention they disable something or other to drop there latency on wow , i was wondering if someone can explain how u do it , i have abit of an issue :P many thx
Printable View
i saw some one mention they disable something or other to drop there latency on wow , i was wondering if someone can explain how u do it , i have abit of an issue :P many thx
I heard something in the AV grp, but its WITHOUT Guarantee etc...
i don't know WHAT this changing, but i believe something with the packages size...
Right click on
My Network Places -> properties
Local Area Connection -> properties
then you see "connect using:" then you see your network card and right of this field "Configure..." click on it
then to "Advanced"
Then i think it was the "Flow Control", but i'm not sure whats happening and when your are not known what you're doing, better do not changing somethings.
here is the wikipedia link to the "flow control"
http://en.wikipedia.org/wiki/Flow_control
wait until next major patch and the data transmission type is chaning which will increase latency.
fixed :)Quote:
wait until next major patch and the data transmission type is chaning which will decrease latency.
I R NEWB I R NEWB.
Fixed by Wilbur <- gay!
Meh, decrease of latency, but more bandwidth usage. More overhead, especialy for ADSL users. :(
HAHA I R PWNT!
Yes Decrease latency.
Quoted from the patch notes for the next major patch
this will DECREASE (:P) latency by between 50-250 depending on locationQuote:
Reduced network latency by disabling the Nagle algorithm.
That means I'll have -10 latency :shock:Quote:
Originally Posted by Majestic_Clown
It's actually 2 registry changes that need to be done. I noticed a very nice drop in my ping. I've quoted a guide I used to do the changes, If your not comfortable touching your Registry please please please do not do it, this is pretty much the brain of your system and 1 wrong key entry may = PC does not work. If you do in fact make the changes, be very careful triple check!!!
Quote:
International lag fix
WoW lags, it's not something new if you're playing on servers a bit far away from your country, but don't worry people are fixing it ! Out of all the methods offered to fix the lag on your machine, one of them posted on Elitistjerks forums seems to work very well.
<> <> <> Read this first <> <> <>
1 - It might have side effects, like slowing down your download speed or affecting your performance on other softwares. (In my case, it didn't change anything)
2 - If you're not sure about what you're doing, just don't do it. I don't want to be responsible because you crashed your computer in some way because you wasted your registry.
2.1 - Seriously, if you don't know what you're doing, don't do it. It will be fixed in one or two weeks anyway. (and the official fix won't have any impact on other softwares)
3 - If you don't have the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\ directory, you can download and apply this file to your registry.
4 - Windows Vista users might want to check this post too.
Source - Elitistjerks.com
"1 - TcpAckFrequency - NOTE if you are running Windows Vista this setting may not have any effect - a hotfix is needed which i'm tracking down. This works fine under Windows XP
Type "regedit" in windows "run.." dialog to bring up registry menu
Then find:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\
There will be multiple NIC interfaces listed in there, find the one you use to connect to the internet, there will be several interfaces listed (they have long names like {7DBA6DCA-FFE8-4002-A28F-4D2B57AE8383}. Click each one, the right one will have lots of settings in it and you will see your machines IP address listed there somewhere. Right-click in the right hand pane and add a new DWORD value, name it TcpAckFrequency, then right click the entry and click Modify and assign a value of 1.
You can change it back to 2 (default) at a later stage if it affects your other TCP application performance. it tells windows how many TCP packets to wait before sending ACK. if the value is 1, windows will send ACK every time it receives a TCP package.
2 - TCPNoDelay
This one is pretty simple (Discussed here)
Type "regedit" in windows "run.." dialog to bring up registry menu
Then find:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Paramet ers
Right-click in the right hand pane and add a new DWORD value, name it TCPNoDelay, then right click the entry and click Modify and assign a value of 1.
Click Ok and close the registry editor, then reboot your PC."
Basically, this fix is deactivating the Nagle algorithm to improve your ping. If you don't want to do it you can just wait for the 2.3.2 patch as it's supposed to deactivate it too, but I don't think you can test it on PTRs right now because the updated patch notes from the latest PTR Build (7705) are actually for the upcoming build (7710).
Quote from: Hortus (Source)
The patch notes that were included with this build (7705) are actually for the next build (7710).
Once you're done with the technical stuff (it probably won't take more than 1 minute if you're not too bad), you can finally get your reward.
Even if in this case, the fix was used to decrease a very high ping, it seems to work very well on low (~100ms) ping for some people (lowered to ~20 or ~30ms).
btw doing this will get your account banned as it intercepts the world of warcraft data between the user and server.
This is FACT that it will get you banned, even blue postings on this, will have to dig to get them.
hmmmm...i dont agree that this will get you banned...that is if you are talking about the registry fix.Quote:
Originally Posted by Majestic_Clown
I did this on UO(ultima online) UO finally had to make changes within their system to control the speed hacks.
Again, I would say that if its on ur registry ur PC then HOW can WOW ban you? lol doesnt make sense. Your not changeing anything within the game. WOW cannot tell you how your PC should be run and in FACT is illegal if not questionable that they even monitor your PC with their WARDEN crap.
yeah sorry misread the tutorial, there is one very simular which used tunneling traffic with a regedit.
My mistake :P
Nice find Ellay, latency down from 120+ to between 30-40 :)
Damn I have Vista64.
Not sure if there is any additional performance improvement with this fix AFTER the patch???
There's not... I tested it, just to see. The patch basically removed the Nagle's algorithm (relative of the fisherman) itself.Quote:
Originally Posted by schlange
I found this tutorial on patch day and decided to hold off seeing how the patch would fix this... the past 3-4 days I've had some terrible lag at night... my latency has been around 200ms before and after the patch, but after the patch I've seen my one or two of my character's (I'm running 5) suffer from lag issues and then DC.
I ran all 5 in the day yesterday with no problems at all, even in the day my latency is around 200ms... and then around 8-9pm the problems started, running 1 character is fine. Is there a way to tell if it's my ISP or it's just my server getting busier?
The TcpAckFrequency hack is still making a difference post patch from my tests (by disabling on one PC, these toons follow half a body length behind).
Download Ping Plotter Freeware. This is a Great Tool(tm). ;) Then do a trace to us.logon.worldofwarcraft.com. You'll see something like this:Quote:
Originally Posted by Bravo
http://l00py.net/wow/Trace1.jpg
Look for the last line you see before you get the "destination unreachable" error. That is the last upstream server before you get into the WoW network (if one of you other folks remembers how to get the server IP, lemme know...I forget). Put that address into the "Address to trace" box, set your "# of times to trace" to 9999, set your trace delay to 1 second, set your "Samples to include" to 9999 and click the Trace button. Let that run for several minutes while you're having trouble. If you see any link in there that's got a huge spike in response time or shows any packet loss, you've probably found the culprit. If it all looks good there, then yeah, the problem is probably your server.
the logon server ip is 12.129.232.113
Actually, I meant the actual play server IP (i.e.: the direct IP for Magtheridon). I say this because the logon server is for everyone, whereas the play servers are in different datacenters.Quote:
Originally Posted by marvein
Oh :)Quote:
Originally Posted by Ughmahedhurtz
*edit* I think magetheridon is 12.129.224.113
blizzard seems to own a large range of IPs. like 12.129.210.0-12.129.240.0
*edit* n/m that isnt mag it is another lobby server.
looks like everything that ends in .113 is part of their logon server cluster.
*edit* kel'thuzad is 206.17.111.86 gimme a min to find mag's
it looks like mag is 206.16.23.44 but that makes no sense unless the registrant is outdated...
WoW servers seem to be in the range of 206.17.111.0-206.17.111.255
*edit*
if you want to try this yourself open a command prompt (start>run cmd) and type netstat and note the addresses listed. Then start wow, login and load the character on the realm you wish to identify. You should wait a minute or two to make sure you are not still communicating witht elobby servers then go back to the command window and do netstat again and look for XXX.XXX.XXX.XXX:3724 And that is your server's IP
Whoa. I'm astounded. This registry fix has decreased the apparent lag time on my followers by about 70%. As an example, without the TCP settings above, I'd hit jump on my keyboard and the 4 alts would jump about time my main hit the ground. With the TCP settings, the alts jump when my main is about halfway UP. Targeting delays seem a LOT lower, too. :D
I know this is an old thread but I just tried the TcpAckFrequency/TcpNoDelay trick and it changed my latency from 200-220 to 60-70. Took 1 minute to do. :thumbsup:
There was for me (Vista x64). My pings are a consistent 70-90 ms now.Quote:
Originally Posted by 'Zutok',index.php?page=Thread&postID=26344#post263 44
I tried this once; I have about 8 or 9 entries in my registry for the connections. I put the tcpack thing in one that had my IP; didn't do shit.
I tried again more recently(When Comcast was being a bitch and the entire southeast US was being routed through a bad 300+ms hop in Sharp's Ridge TN) and put the entry in TWO registry slots that had my IP in it; my pings have been a consistent 30-60ms now, down from 160+.
I'm super skeptical, but will try this when I get home.
If you want to know more about what it's doing to your computer and why it helps search for the 2 regkey names on microsoft.com. I think there is an article explaining.
I vouch for this fix still works 21/6/08 im in australia pings are often 300-500 now its normal ping too USA as if i was playing a FPS. Now its 180-230. SOOOO MUCH BETTER TY TY TY TY
THIS SHOULD BE PINED.Quote:
Originally Posted by 'Ellay',index.php?page=Thread&postID=24972#post249 72
Note that this is an easy fix and does work well. The TCPNoDelay part DOES NOT apply to Vista, however. Just the first step is required (note that you must verify you have the correct network interface if you have more that one).
By doing the two registry changes my ping on The Forgotten Coast dropped from 240's to 120-130's.
I recently moved there and on Illidan I had a ping of 70, so I noticed the weird behavior and was shocked when i saw my ping was in the mid 200's.
Much nicer back at a more reasonable number.
can anyone confirm if this actually reduces latency? or does it just drop your listed ping number?
What do you mean just drop the listed ping number? This isn't some type of visual hack that shows you a wrong ping, tracking people into thinking it helped them.Quote:
Originally Posted by 'yarr',index.php?page=Thread&postID=77752#post7775 2
It lowers your latency..
It actually works. It's not just the visual confirmation on your latency bar - performance changes wildly, especially for people that have high latency before.Quote:
Originally Posted by 'yarr',index.php?page=Thread&postID=77752#post7775 2
Anyone knows where I can download the registry adds required? I don't have HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\ in my registry.
If you can't find that key, just do the first one. The one that works on:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\
That's the only one I did, and it worked great.
I thought they implemented this in the 2.3.0 patch?
Yeah, working good, playing with about 50ms now instead of 120 :)Quote:
Originally Posted by 'BobGnarly',index.php?page=Thread&postID=118269#po st118269
I don't think it ever went in. This "trick" still seems to make an improvement when used.Quote:
Originally Posted by 'Griznah',index.php?page=Thread&postID=118303#post 118303
Im just gona leave this here:
http://www.youtube.com/watch?v=aKV4iHvdR2M
You can download a little program off of cursegaming that fixes the problem. I went from 200-300 on each toon down to under 125 for all 5. It is called faster ping. Here is a link to it on curse:
http://www.curse.com/downloads/details/10599/
Changing the TcpAckFrequency seriously hampered my download-speed on my Vista Ultimate x64. I can usually download at about 5MB/sec but got stuck at 50kb/sec, so this just isn't for me. Shame 'cause it really helped my latency.