Experiencing stutter in lock step mode only
|
Hi!
I am having a pretty big issue where every 2-5seconds or so my game stutters(small pause). So far I have isolated this to being in lockstep mode. Any help would be great! Here are some system specs: 16gig ram 980 msi video card Sandybridge i5 processor windows 10 http://imgur.com/pCgNoQ7 : poe settings Please let me know if anymore information is needed. | |
|
Are you trying to force PoE to use two video cards in SLI?
| |
|
Not seeing anything unusual, you are using lock step and your latency is not stable, thats how latency manifests itself in lock step when the latency is all over the place.
Ancestral Bond. It's a thing that does stuff. -Vipermagi
He who controls the pants controls the galaxy. - Rick & Morty S3E1 |
|
" It looks like you are showing latency spikes. Notice the graph for latency showing spikes over 100ms. When using lock step, if your latency spikes over 100ms the game will feel choppy and uneven. I'd say it would be best to try to figure out why you are seeing the latency spikes. Could you post some results in WinMTR for periods you are having troubles? Let it run for 10 mins or so ( or at least 500 cycles ) HERE is a link to a guide for WinMTR. "I would have listened... I would have understood!" - Scion Have you removed Asus ROG/GameFirst yet? Last edited by MaxTheLimit on Nov 25, 2015, 9:55:56 AM
|
|
" Just want to say, thanks a lot for the help! Hopefully we can get this resolved. It's also important to note that ping spikes like this only occur while playing poe. Here are the results of that tool:
Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | RT-AC66U-11F0 - 0 | 501 | 501 | 0 | 0 | 0 | 0 | | c-71-205-150-1.hsd1.co.comcast.net - 0 | 501 | 501 | 7 | 17 | 76 | 13 | |xe-9-1-2-0-sur03.greeley.co.denver.comcast.net - 0 | 501 | 501 | 7 | 17 | 83 | 12 | |ae-34-0-ar01.denver.co.denver.comcast.net - 0 | 501 | 501 | 10 | 20 | 83 | 38 | |he-6-1-2-cr01.1601milehigh.co.ibone.comcast.net - 0 | 490 | 490 | 10 | 98 | 3000 | 11 | |be-11719-cr02.denver.co.ibone.comcast.net - 0 | 501 | 501 | 11 | 23 | 188 | 11 | |hu-0-11-0-5-pe02.910fifteenth.co.ibone.comcast.net - 0 | 501 | 501 | 11 | 21 | 85 | 16 | |xe-0-0-0.bbr01.cf01.den01.networklayer.com - 0 | 501 | 501 | 10 | 20 | 86 | 12 | | ae12.bbr02.eq01.dal03.networklayer.com - 0 | 501 | 501 | 24 | 34 | 93 | 24 | | ae1.dar01.sr01.dal01.networklayer.com - 0 | 501 | 501 | 24 | 33 | 111 | 25 | | po1.fcr03.sr04.dal01.networklayer.com - 1 | 498 | 497 | 0 | 27 | 88 | 27 | | speedtest.dal01.softlayer.com - 0 | 501 | 501 | 24 | 34 | 94 | 27 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider I also tried using a different gateway and still experienced stutter. | |
|
So this is the results at the destination:
| speedtest.dal01.softlayer.com - 0 | 501 | 501 | 24 | 34 | 94 | 27 | There is no packet loss, and average times look good. Latency did spike up to 94, which isn't great, but shouldn't cause the degree of problems you've been seeing. Was this run performed while the game was seeing latency spikes? Or is it pretty much constant? Could you post WinMTR results to a couple other locations as well? Just to see if the spikes show up at all in anything else. PoE may just be the most prone to showing these spikes. A lot of games, you might not even notice this sorta thing. Try going to 8.8.8.8 as the destination IP. That is the public DNS for Google. Should be pretty reliable. One concern I have is that the hop leading from you out to comcast: | c-71-205-150-1.hsd1.co.comcast.net - 0 | 501 | 501 | 7 | 17 | 76 | 13 | Already showing a spike up to 76ms. This is concerning because it does seem to carry forward to the hops that are reporting back proper results. You shouldn't be seeing spikes like that so early on your routes. "I would have listened... I would have understood!" - Scion
Have you removed Asus ROG/GameFirst yet? |
|
|
I don't see anything in the trace that shows signs of real issues that would cause stuttering with lockstep. The latency is sub 100ms by the time it hits the destination, and there is no sign of packet loss.
One thing I notice though is that you're tracing to the gateway and not to the instance server itself (which could be a different route). It might be worthwhile (if we want to continue diagnosing possible network problems) to get the instance server address from the Client.txt log file and trace to that instead while inside. The way to do that is to connect to the instance, then ALT+Tab and open up the Client.txt log file in the logs folder. At the bottom should be something that says "Connecting to instance server at <ip address>:6112" Take the address listed there and put it in as the destination of your trace. That will trace from you to the actual instance server you are inside (assuming you used the very last connection line as the destination). Let it run the whole time you are inside of that instance. Hopefully it can capture a stutter in the lockstep. If you still experience stutters, and the MTR trace looks clean... it could be not network related at all and could instead be due to a system resource issue (something on the PC causing resource contention regularly which causes the stutters). Those are a little harder to diagnose as you have to basically use a resource monitor or similar to find out what is using resources at the same time as PoE experiences the stutters. Good luck. Last edited by Drakier on Nov 25, 2015, 12:27:13 PM
| |
|
Thanks for the follow up.
To answer MaxTheLimit's question, the spikes are very consistent everywhere in the game. Here are the results when listening to connected server 173.192.12.44:
Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | RT-AC66U-11F0 - 0 | 153 | 153 | 0 | 0 | 8 | 0 | | c-71-205-150-1.hsd1.co.comcast.net - 0 | 153 | 153 | 8 | 17 | 152 | 12 | |xe-9-1-2-0-sur03.greeley.co.denver.comcast.net - 0 | 153 | 153 | 8 | 18 | 147 | 14 | |ae-34-0-ar01.denver.co.denver.comcast.net - 0 | 153 | 153 | 10 | 19 | 150 | 15 | |he-7-1-2-cr01.1601milehigh.co.ibone.comcast.net - 0 | 153 | 153 | 10 | 39 | 739 | 26 | |be-11719-cr02.denver.co.ibone.comcast.net - 0 | 153 | 153 | 12 | 21 | 155 | 17 | |hu-0-10-0-4-pe02.910fifteenth.co.ibone.comcast.net - 0 | 153 | 153 | 10 | 20 | 149 | 14 | |xe-0-0-0.bbr01.cf01.den01.networklayer.com - 0 | 153 | 153 | 10 | 21 | 153 | 17 | | ae12.bbr02.eq01.dal03.networklayer.com - 0 | 153 | 153 | 24 | 33 | 169 | 31 | | ae1.dar01.sr01.dal01.networklayer.com - 0 | 153 | 153 | 24 | 33 | 162 | 24 | | po1.fcr05.sr06.dal01.networklayer.com - 0 | 153 | 153 | 24 | 36 | 167 | 29 | | 2c.0c.c0ad.ip4.static.sl-reverse.com - 1 | 149 | 148 | 0 | 28 | 168 | 24 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Here are the results of google's dns 8.8.8.8:
Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | RT-AC66U-11F0 - 0 | 419 | 419 | 0 | 0 | 1 | 0 | | c-71-205-150-1.hsd1.co.comcast.net - 0 | 419 | 419 | 8 | 11 | 32 | 13 | |xe-9-1-2-0-sur03.greeley.co.denver.comcast.net - 0 | 419 | 419 | 8 | 11 | 35 | 12 | |ae-34-0-ar01.denver.co.denver.comcast.net - 0 | 419 | 419 | 10 | 13 | 47 | 15 | |he-6-1-2-cr01.1601milehigh.co.ibone.comcast.net - 2 | 329 | 323 | 0 | 507 | 4887 | 3328 | |be-11719-cr02.denver.co.ibone.comcast.net - 0 | 419 | 419 | 11 | 16 | 42 | 13 | |hu-0-10-0-4-pe02.910fifteenth.co.ibone.comcast.net - 0 | 419 | 419 | 11 | 14 | 26 | 17 | |as15169-1-c.910fifteenth.co.ibone.comcast.net - 0 | 419 | 419 | 11 | 15 | 49 | 13 | | 216.239.42.249 - 0 | 419 | 419 | 11 | 15 | 25 | 17 | | 216.239.42.237 - 0 | 419 | 419 | 11 | 16 | 206 | 14 | | google-public-dns-a.google.com - 0 | 419 | 419 | 11 | 14 | 24 | 13 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Thanks again! | |
|
So that trace to the instance server seems to match more closely with the latency meter in-game.
Would you say that you are seeing similar results to the "worst" column in the latency graph in-game at approximately the same time? If you run then both side-by-side and watch, you should see the responses correlating with the spikes. The problem I see is that it is very intermittent and isn't even being captured every node necessarily. The google DNS trace is only showing a couple of hops with latency, but that could be the node itself and not your connection... but yet the PoE trace is showing immediate latency at your second hop and following through the whole trace. Have you tried unplugging the power on your network devices (modem/router/etc) and then plugging them back in after waiting 30 seconds or so? | |
" You're a genius Drakier, rebooting router/modem fixed the issue. I will be sure to do this next time i am experiencing similar issues. Thanks everyone for the help! |
