Lockstep Stutter
I've tried searching for this, but haven't found anything that exactly matches my problem.
I have a recurring stutter that only affects the game when in lockstep mode. It reoccurs every 2.5 second - like clockwork. It's as if the game just freezes for a tenth of a second. It occurs no matter the graphic setting, character, leauge, server... anything I can think of changing. It completely goes away when using Predictive mode (but then I get the dreaded desyncs, ofc). My game has been running smoothly up until v2.1, and my latency/connection stability has remained unchanged. The latency graph shows no apparent lag spikes that would explain the stutter. This issue has made lockstep unusable, which is a real shame. Hoping for a fix soon. |
![]() |
Asus GameFirst installed?
Razer Gaming Service? Some other process also spiking every 2.5 seconds? |
![]() |
Nope. None of that. And everything worked perfectly pre Talisman.
Nothing else up with my system (no new installs, no spikes), and if there was some CPU sharing issues (or the likes) it most certainly would show up even if I used Progressive netwrok mode. It's rather aparent that this is some issue with the game. Everything works fine -> install a patch -> game is suddenly stuttering. I didn't think much of it first, but I've come to a point where I simply can't ignore it. Dernière édition par mats_mono#2060, le 2 janv. 2016 à 09:21:56
|
![]() |
Can you post a WinMTR capturing at least 300 packets as well as capturing during the issues?
Post the results and we can check network stuff to see if anything shows up. Instructions are linked in the "Rules" sticky post. |
![]() |
Haven't done any checks with WinMTR in a long time, since things have been working alright. Therefore I can't say if anyhting has changed with my connection or not. But like I said before: Game worked fine for months, patched for Talisman, get stutters.
This is what I get with nothing else running:
Spoiler
![]() Game running on Predictive:
Spoiler
![]() Game running on Lockstep:
Spoiler
![]() I recorded a small video to show what's going on - https://youtu.be/w9IAWqQekOc and another, running around - https://youtu.be/tt9hlllZIu0 Dernière édition par mats_mono#2060, le 2 janv. 2016 à 19:37:35
|
![]() |
Not sure why you took screenshots rather than posting the Text output of the WinMTR, but whatever.
You look like you have 2 layers of routers in your network, and you're losing packets between them. From your PC you are connected to some network device (1). That network device (1) is connected to another (2). That second device (2) is either a router by itself or a modem... the connection between (1) and (2) is dropping packets. Could be (1) causing issues, or could be (2). I'd unplug them both from power for a minute then plug them both back in and trace again. Dernière édition par Drakier#1520, le 2 janv. 2016 à 19:38:05
|
![]() |
Images, because the plain text's formatting got screwed in the post.
I have a modem, which I can't connect directly to, due to physical reasons. But I've had this setup for quite some time, and not had any problems with it. Lockstep has been working great ever since beta. The packet loss occurs just as I start the measuring. It drops 5-10 packets on all hosts as soon as I start. After that everything ticks away just fine. Modem and router reset - same results in WinMTR Dernière édition par mats_mono#2060, le 2 janv. 2016 à 19:53:13
|
![]() |
How long it has run without issue is completely irrelevant. Hardware can just "go bad" for no real reason you know of.
It happens quite often. The results from your trace show that you have an issue between 192.168.1.1 and 192.168.0.1. Not sure which end is the problem as with most peering issues. One of those two devices is failing. If you could reconfigure them, you might be able to determine which.. but that is up to you to do. Edit: You might also want to check the cable between them. Try unplugging it and plugging it back in, or swapping it with a new cable just to rule that out. Can also try different ports if they are available. Dernière édition par Drakier#1520, le 2 janv. 2016 à 19:57:53
|
![]() |
Even though the WinMTR results are the same, rebooting the routers seems to have fixed the problem. Stutter in game is gone. Thanks for the support!
Appears as though sometimes a coincidence is just a coincidence. ;) Dernière édition par mats_mono#2060, le 2 janv. 2016 à 20:14:15
|
![]() |