Uploaded July 2017 | Updated September 2026, 3 weeks ago
Since the dawn of time, I've had serious input latencies/ignoring in online matches, causing most of my defeats. If I press an input at a perfect time, and the game instead delays it for several hundred milliseconds, that's gonna change a blow to a parry bate, etc. Since patch v1.09 they've disabled a feature, they're internally calling TimeSnap. What it does (from my understanding of their description), is, it dispatches actions on 100 millisecond (ms) boundaries. For example, let's say the game stores an internal timer that counts time since the beginning of the match, then actions will only occur every 100th millisecond. That is, on 100ms boundaries, and not a delay of 100ms. So if the timer has reached 4691ms and you attempt to do an action, the action will be performed at 4700ms. If you attempted to do an action at 4604ms, your action would be delayed for 96ms (to time 4700), etc.
How exactly they've set it up internally, I don't know, but I've had suspicions this system might have been what has caused my issues, despite my delays being far greater than 100ms. however, they've always appeared to have been delayed to the exact moment the opponent performs an action as well, and TimeSnap was invented to ensure synchronicity.
This first match, I had no apparent input delays. Well, might have felt a slight delay with a light attack; but I did feel like the game ignored one of my guard break counters against the Raider (2:37).
I'll have to play a whole lot more matches to confirm or deny whether my input issues have been fixed, though.
Since the dawn of time, I've had serious input latencies/ignoring in online matches, causing most of my defeats. If I press an input at a perfect time, and the game instead delays it for several hundred milliseconds, that's gonna change a blow to a parry bate, etc. Since patch v1.09 they've disabled a feature, they're internally calling TimeSnap. What it does (from my understanding of their description), is, it dispatches actions on 100 millisecond (ms) boundaries. For example, let's say the game stores an internal timer that counts time since the beginning of the match, then actions will only occur every 100th millisecond. That is, on 100ms boundaries, and not a delay of 100ms. So if the timer has reached 4691ms and you attempt to do an action, the action will be performed at 4700ms. If you attempted to do an action at 4604ms, your action would be delayed for 96ms (to time 4700), etc.
How exactly they've set it up internally, I don't know, but I've had suspicions this system might have been what has caused my issues, despite my delays being far greater than 100ms. however, they've always appeared to have been delayed to the exact moment the opponent performs an action as well, and TimeSnap was invented to ensure synchronicity.
This first match, I had no apparent input delays. Well, might have felt a slight delay with a light attack; but I did feel like the game ignored one of my guard break counters against the Raider (2:37).
I'll have to play a whole lot more matches to confirm or deny whether my input issues have been fixed, though.
