Page 1 of 1

For Latency.

PostPosted: Wed Jun 03, 2009 4:03 pm
by Narlya
This is a latency fix VB script.
How a network connection proceeds?
-Packet x1 is sent, from A to B.
-B sends Acknowledgment for Packet x1.
-A sends Packet x2.

What the script does, is remove the Ack's.

Latency Fix Download

If you don't like it, you can roll back the change with another VB script included.

It works quite well, you'll feel that you cast faster(at least i did) i used to have 258ms :p now its 113ms.

//narlya

Re: For Latency.

PostPosted: Wed Jun 03, 2009 11:51 pm
by Caeth
this is exactly what Fasterping does, it just doesn't come with a rollback so if you dont like it you have to change the value in your registry manually.

Re: For Latency.

PostPosted: Thu Jun 04, 2009 12:00 am
by Mickelus
What's this ack's you speak of?

Re: For Latency.

PostPosted: Thu Jun 04, 2009 12:32 pm
by Ironsights
is this not the exact same thing you can do with a registry edit and therefore not have 3rd party programs playing with your registry?

Re: For Latency.

PostPosted: Thu Jun 04, 2009 12:39 pm
by Issues
Yes it is. I've been using the registry change for over a year and a half and it's total win. cba with programs doing it :D

Re: For Latency.

PostPosted: Thu Jun 04, 2009 1:47 pm
by Aeliren
What do I change in the registry?

Re: For Latency.

PostPosted: Thu Jun 04, 2009 1:59 pm
by Issues
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).

Re: For Latency.

PostPosted: Thu Jun 04, 2009 2:13 pm
by Narlya
It is exactly the same :D, the only difference is. This is ran by a VbScript(Visual basic script) which means, it just does it all without you having to go through all this, its not a program its a 1 time run .exe.

:p just to clear things.

Re: For Latency.

PostPosted: Thu Jun 04, 2009 3:21 pm
by Ironsights
do not trust ze exe!

srsly mick once took control of my char logging me out and stuff through his addons

/TIN FOIL HAT

I AM BULLLLLLLLLLLLLLETPROOOOOOOOOOOOOOOF

Re: For Latency.

PostPosted: Thu Jun 04, 2009 4:01 pm
by Mickelus
:roll:

Re: For Latency.

PostPosted: Thu Jun 04, 2009 7:27 pm
by Slaughtered
Ironsights wrote:/TIN FOIL HAT

I AM BULLLLLLLLLLLLLLETPROOOOOOOOOOOOOOOF


Image

Re: For Latency.

PostPosted: Thu Jun 04, 2009 10:56 pm
by Aeliren
Okay I don't know how this can be possible but not only am I sitting at 60 ms now, my fps has pretty much doubled.
Oh well.

Re: For Latency.

PostPosted: Fri Jun 05, 2009 8:18 pm
by Rizz
Network Fix #2

The problem:

http://elitistjerks.com/f15/t40955-wow_ ... ost1252436
Each time there has been a patch (and some times very sporadically after a patch) my comp lags out when i try to log my main into dalaran. Its always the same, I log in, graphics load but everyone around me is "unknown the noble" etc. After logging in and getting disconnected (this takes from 10-100 secs) what seems like a set number of times (around 10-20), I can log in no problem.


The Fix:

Next, go into your network settings in the system properties if you are playing under windows. Select the network card and select the "configure" button. You should get dialog box with some tabs on it. Select advanced. You will find several options. Ensure that specific features that might be called like "TCP offloading" is switched off. Also you might want to shut off powersafe functions (unless you are playing on a laptop they might not make much sense anyway). I can't give you specific names for the options to turn off, because the naming of those are driver dependant and thus change depending which hardware and driver you are using. In general, every option that sounds like the hardware is "accelerating" or "offloading" some functionality from the operating system into the hardware or driver should be switched off. These features have in the past proven to be more counter-productive than useful. Again a system reboot is necessary after changing something here.

Here's a 10 step screenshot to show you how to navigate to the correct options if it sounds too confusing (windows XP users skip #3, I think):
http://khornn.pp.fi/images/network.jpg


Why it works

http://en.wikipedia.org/wiki/Tcp_checksum_offload
http://publib.boulder.ibm.com/infocente ... ffload.htm
TCP checksum offload

The TCP checksum offload option enables the network adapter to compute the TCP checksum on transmit and receive, which saves the AIX® host CPU from having to compute the checksum.

The savings vary by packet size. Small packets have little or no savings with this option, while large packets have larger savings. On the PCI-X GigE adapters, the savings for MTU 1500 are typically about 5% reduction in CPU utilization, and for MTU 9000 (Jumbo Frames) the savings is approximately a 15% reduction in CPU utilization.

TCP streaming throughput with MTU 1500 is slower on machines that have processors faster than 400 MHz if the TCP checksum offload option is enabled because the host system can run the checksum faster than the Gigabit Ethernet PCI adapters, FC2969 and FC 2975. Therefore, by default, this option is off on these adapters. When these adapters use jumbo frames, it can run at wire speed even when it has to compute the checksum.

The PCI-X Gigabit Ethernet adapters can run at wire speeds with the TCP checksum offload option enabled and it reduces host CPU processing so it is enabled by default.


This should probably fix some of the random disconnect issues by taking a lot of workload off of your shitty network card and making your CPU work more. Again, if you experience any problems just reverse these steps to restore the original settings.

Re: For Latency.

PostPosted: Fri Jun 05, 2009 8:19 pm
by Rizz
Thats what we used for our members and seems to work;)