This is some technical resolution all the laggers out there..
All must be pissed with the lag in A3.. Well the biggest reason is the ISP and rarely the A3 server.
Many people here have a 128kbps connection and still play the game virtually lag free but poeple like me and others with a 2mbps connection lag... how and why???
The most simple answer to the question is the ADSL mode at which your DSL connection is operating. There are two modes of operation for a ADSL connection. Either Interleaved mode or Fast mode.
ADSL can be configured to work in either Interleaved or Fast (or FastPath) modes. Fast mode is more sensitive to errors but has lower latency or lag. If your latency to the closest node is above 25 ms, you're probably in Interleaved mode.
In basic terms, latency is the time needed for a round trip over the Internet between two points (e.g., your computer and remote host). Latency is usually not a problem with a proper TCP Receive Window (see "Why TCP Receive Window matters"), but high latency can adversely affect interactive applications such as on-line real-time gaming. High latency is usually caused by Internet routing and/or congestion issues. There's usually not much you can do about such issues other than complaining or even switching service providers. However, if your latency is is higher due to "interleaved mode" then it may be possible to get some improvement.
Resolution to Lags.....
-
Greatshop
- Posts: 247
- Joined: Wed Dec 13, 2006 7:27 am
- Class: N/A
- Town: N/A
- Location: I am the Lord of Mars
- Contact:
Interleaved Mode
Data is spread out during ADSL transmission. This improves the ability to correct errors due to noise pulses, and can thus make the connection more reliable. However, interleaving increases latency (delay). The amount of interleaving determines the amount of spread and hence the amount of latency. Interleaved Mode is required with G.lite (because more adverse line conditions are expected).
Fast (or FastPath) Mode
Lower latency than Interleaved Mode, but more vulnerable to errors due to noise pulses.
In Interleaved mode the latency is more that double-triple compared to Fast mode. This is due to error correction implied in it but at the cost of latency... it is not for online gamers..
In Fast mode, as mentioned earlier, the errors are more but very low latency and thus online gaming is lag free.
The First steps to troubleshoot the lag is to CALL THE ISP and get the mode changed to FAST or FASTpath.
Data is spread out during ADSL transmission. This improves the ability to correct errors due to noise pulses, and can thus make the connection more reliable. However, interleaving increases latency (delay). The amount of interleaving determines the amount of spread and hence the amount of latency. Interleaved Mode is required with G.lite (because more adverse line conditions are expected).
Fast (or FastPath) Mode
Lower latency than Interleaved Mode, but more vulnerable to errors due to noise pulses.
In Interleaved mode the latency is more that double-triple compared to Fast mode. This is due to error correction implied in it but at the cost of latency... it is not for online gamers..
In Fast mode, as mentioned earlier, the errors are more but very low latency and thus online gaming is lag free.
The First steps to troubleshoot the lag is to CALL THE ISP and get the mode changed to FAST or FASTpath.
-
Greatshop
- Posts: 247
- Joined: Wed Dec 13, 2006 7:27 am
- Class: N/A
- Town: N/A
- Location: I am the Lord of Mars
- Contact:
Now the Second Step:
Increasing the TCP Receive Window for Microsoft Windows XP.
The only Windows XP network setting that has any real effect on DSL or Cable Modem speed is the TCP Receive Window size, which can be controlled with the following Registry settings:
GlobalMaxTcpWindowSize (default for all interfaces - simplest method)
TcpWindowSize (individual interface - overrides default)
Do the following:
Save the appropriate lines of text below to your Desktop in the file name 2KTCP64K.REG, and then double-click on the resulting file to add the setting into your Registry.
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"GlobalMaxTcpWindowSize"=dword:0000ffff
You can also download the file from the URL below:
http://rahul.ueuo.com//A3/latency/2KTCP64K.reg
Reboot your system after making any change for the change to take effect!
Increasing the TCP Receive Window for Microsoft Windows XP.
The only Windows XP network setting that has any real effect on DSL or Cable Modem speed is the TCP Receive Window size, which can be controlled with the following Registry settings:
GlobalMaxTcpWindowSize (default for all interfaces - simplest method)
TcpWindowSize (individual interface - overrides default)
Do the following:
Save the appropriate lines of text below to your Desktop in the file name 2KTCP64K.REG, and then double-click on the resulting file to add the setting into your Registry.
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"GlobalMaxTcpWindowSize"=dword:0000ffff
You can also download the file from the URL below:
http://rahul.ueuo.com//A3/latency/2KTCP64K.reg
Reboot your system after making any change for the change to take effect!
-
Greatshop
- Posts: 247
- Joined: Wed Dec 13, 2006 7:27 am
- Class: N/A
- Town: N/A
- Location: I am the Lord of Mars
- Contact:
Why TCP Receive Window Matters
TCP is a packet-based protocol where data is transmitted in variable-sized blocks, typically with a maximum size of 500-1500 characters (usually 1500 characters for Cable Modem or DSL). Two important characteristics of the TCP protocol:
Packet Acknowledgments
In order to insure delivery of each packet, the receiver must acknowledge successful receipt by sending a special acknowledgment packet to the sender. If the sender does not receive the acknowledgment packet within a certain time limit, it assumes the packet has been lost and retransmits it (up to a retransmission limit).
Receive Window
If each data packet had to be acknowledged before another could be sent, then performance could suffer due to the delay time needed for the data packet to reach the receiver plus the time needed for the acknowledgment packet to get back to the sender. To avoid this delay, the sender is allowed to keep transmitting data packets prior to receiving acknowledgments up to a maximum "window" size advertised by the receiver, normally large enough for several packets. The larger the window, the more packets that can be sent before needing an acknowledgment; however, larger windows can require more packets to be retransmitted when a transmission error occurs. Hence, the receive window size needs to be large enough to keep data flowing continuously, but not excessively large.
The TCP Receive Window has a default value of only about 8K bytes in Windows 95/98/NT, and about 16K bytes in Windows Me/2000/XP, which is adequate for relatively slow dialup modems and for high-speed networks with relatively low latency (e.g., less than 20 milliseconds). Increasing the TCP Receive Window above the default settings (e.g., to 32-63K) can substantially improve throughput on high-speed (e.g., Cable Modem or DSL) connections where there is higher latency (e.g., 100-200 milliseconds), as is often the case on the Internet, particularly over long network paths. (Increasing the TCP Receive Window will usually not have an adverse effect on other connections.)
TCP is a packet-based protocol where data is transmitted in variable-sized blocks, typically with a maximum size of 500-1500 characters (usually 1500 characters for Cable Modem or DSL). Two important characteristics of the TCP protocol:
Packet Acknowledgments
In order to insure delivery of each packet, the receiver must acknowledge successful receipt by sending a special acknowledgment packet to the sender. If the sender does not receive the acknowledgment packet within a certain time limit, it assumes the packet has been lost and retransmits it (up to a retransmission limit).
Receive Window
If each data packet had to be acknowledged before another could be sent, then performance could suffer due to the delay time needed for the data packet to reach the receiver plus the time needed for the acknowledgment packet to get back to the sender. To avoid this delay, the sender is allowed to keep transmitting data packets prior to receiving acknowledgments up to a maximum "window" size advertised by the receiver, normally large enough for several packets. The larger the window, the more packets that can be sent before needing an acknowledgment; however, larger windows can require more packets to be retransmitted when a transmission error occurs. Hence, the receive window size needs to be large enough to keep data flowing continuously, but not excessively large.
The TCP Receive Window has a default value of only about 8K bytes in Windows 95/98/NT, and about 16K bytes in Windows Me/2000/XP, which is adequate for relatively slow dialup modems and for high-speed networks with relatively low latency (e.g., less than 20 milliseconds). Increasing the TCP Receive Window above the default settings (e.g., to 32-63K) can substantially improve throughput on high-speed (e.g., Cable Modem or DSL) connections where there is higher latency (e.g., 100-200 milliseconds), as is often the case on the Internet, particularly over long network paths. (Increasing the TCP Receive Window will usually not have an adverse effect on other connections.)
-
Misteroldie
- Posts: 736
- Joined: Mon Mar 05, 2007 4:58 am
Great Guide ..I really appreciate your patient summation !! 
Thanks !!
Thanks !!
Last edited by Misteroldie on Fri Jun 22, 2007 2:53 am, edited 1 time in total.
You said you a gansta but you neva pop nuttin'
You said you a wanksta and you need to stop frontin'
Regards,
cola_drinker
You said you a wanksta and you need to stop frontin'
Regards,
cola_drinker
