Champion moving and actions delay, stable latency

12
Comment below rating threshold, click here to show it.

Breaker

Junior Member

02-18-2013

Hello everyone, I'm here because I've tried everything else and this is my last resource. The problem started today, I've been experiencing some strange 'lag spikes' in the game, but my latency is still stable, around 180-190. I know this is NOT an internet problem because my brother is playing LoL right now with exactly the same connection (router), and he's not having this lag issues. My video card drivers are up to date, so is adobe air.
I'll try to explain the problem. I'm playing ADC, and when I'm kiting my champion suddenly ignores my command and freezes, but everyone else can move. This lasts like 1 second or so, it's not that long but still gamebreaking.

Please, help!


Comment below rating threshold, click here to show it.

Breaker

Junior Member

02-19-2013

Bump.


Comment below rating threshold, click here to show it.

Chasing Ghosts

Member

02-19-2013

i been getting this for past few days, about 3 days or so. im not sure if its my internet, but everything loads fine. i ask ppl in game if they lag, first day many team members said they were, but recently they are fine, i seems to be the only one lagging. probably just my connection. but i checked everything. the only thing that happened last few days was the weather go a bit stormy.


Comment below rating threshold, click here to show it.

Solaris Shadow

This user has referred a friend to League of Legends, click for more information

Wrenchman

02-19-2013

can you post your most recent logs from C:\Riot Games\League of Legends\Logs\Network Logs
as well as you http://netalyzr.icsi.berkeley.edu/ here.


Comment below rating threshold, click here to show it.

Righteousmoo

Member

02-19-2013

Has anyone found a resolution for this? Just lost another one due to not being able to do anything. Only my spikes are longer, Then it forces me out. And In a ranked match, I don't wanna lose my standing.


Comment below rating threshold, click here to show it.

AbortRetryFail

Senior Member

02-19-2013

Righteous / Breaker, have you got a netalyzer yet? This sounds a lot like buffering latency.

If that doesn't point to anything interesting, grab a capture of the issue and I'll look at it with you if you're interested:

1) Download & install Netmon 3.4 http://www.microsoft.com/en-us/downl...s.aspx?id=4865

2) In a cmd or powershell window, run: nmcap.exe /network * /capture /file LOLPerf.cap:100M

3) Play LOL until you encounter lag spikes / discos / etc

4) ctrl-c in the window where you started the capture

This may not clearly identify your problem, but it will clarify your symptom.


Comment below rating threshold, click here to show it.

Breaker

Junior Member

02-20-2013

Thanks you guys for your answers.
Network logs attached. Also, I must say that this haven't been happening every single game, it's kinda random, but I'm sure this is not a server hosting problem.

Here's the results of ICSI Netalyzr:

Quote:
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
The network indicated bursts of packet loss
Network bandwidth may be low
The network blocks some or all EDNS replies
Not all DNS types were correctly processed
Your computer's clock is substantially fast
Address-based Tests +
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Yes +
Reachability Tests +
TCP connectivity (?): Note
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): OK +
Traceroute (?): OK +
Path MTU (?): OK +
Hidden Proxy Detection (?): OK +
Network Access Link Properties +
Network performance (?): Latency: 170 ms, Loss: 0.5% +
TCP connection setup latency (?): 170ms +
Background measurement of network health (?): 7 transient outages, longest: 0.8 seconds
During most of Netalyzr's execution, the client continuously measures the state of the network in the background, looking for short outages. During testing, the client observed 7 such outages. The longest outage lasted for 0.8 seconds. This suggests a general problem with the network where connectivity is intermittent. This loss might also cause some of Netalyzr's other tests to produce incorrect results.
Network bandwidth (?): Upload 110 Kbit/s, Download 1.0 Mbit/s –
Your Uplink: We measured your uplink's sending bandwidth at 110 Kbit/s. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.
Your Downlink: We measured your downlink's receiving bandwidth at 1.0 Mbit/s. This level of bandwidth works well for many users.
Network buffer measurements (?): Uplink 78 ms, Downlink 120 ms +
HTTP Tests +
Address-based HTTP proxy detection (?): OK +
Content-based HTTP proxy detection (?): OK +
HTTP proxy detection via malformed requests (?): OK +
Filetype-based filtering (?): OK +
HTTP caching behavior (?): OK +
JavaScript-based tests (?): OK +
DNS Tests +
Restricted domain DNS lookup (?): OK +
Unrestricted domain DNS lookup (?): OK +
Direct DNS support (?): OK +
Direct EDNS support (?): Note
EDNS-enabled requests for small responses are answered successfully.
EDNS-enabled requests for medium-sized responses remain unanswered. This suggests that a proxy or firewall is unable to handle extended DNS requests or DNS requests larger than 512 bytes.
EDNS-enabled requests for large responses remain unanswered. This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 700 ms +
Direct probing of DNS resolvers (?)
Your system is configured to use 1 DNS resolver(s).
The resolver at 192.168.1.1 (ns4.dedicado.com.uy) could not process the following tested types:
Medium (~1300B) TXT records
Large (~3000B) TXT records
Large (~3000B) TXT records fetched with EDNS0
Requests from this resolver come from 200.108.192.5. This resolver requries 225 ms to fetch a result from our server and 40 ms to return a result from its cache. It validates DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
DNS results wildcarding (?): OK +
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?): +
IPv6 Tests +
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Host Properties +
System clock accuracy (?): Warning
Your computer's clock is 3608 seconds fast.
Browser properties (?): OK +
Uploaded data (?): OK

And AbortRetryFail, thanks, I'll try it out and post the results.


Comment below rating threshold, click here to show it.

Breaker

Junior Member

02-20-2013

Whoops, here are the network logs.


Comment below rating threshold, click here to show it.

djlemay1

Member

02-20-2013

Quote:
Originally Posted by Solaris Shadow View Post
can you post your most recent logs from C:\Riot Games\League of Legends\Logs\Network Logs
as well as you http://netalyzr.icsi.berkeley.edu/ here.

Hi, i'm hoping this might reveal a problem. This is from yesterday, and it was probably at its worst.

http://pastebin.com/z6g77RzY


Comment below rating threshold, click here to show it.

Breaker

Junior Member

02-20-2013

Bump


12