In the last update, we looked at a number of logs from players who reported this issue to us by pulling the match logs from the IDs they provided. Unfortunately, in the vast majority of cases (around 70%), the issue we saw was the client and server trying to reconnect several times, indicating a poor connection (such as playing on a WiFi connection) or packet loss.
However, we are still actively working with a number of players and content creators to try to verify if they're experiencing packet loss or poor connections - something we have less control over - or if it's indeed a gameplay issue we can smooth out.
To ELI5, all of the web pages you visit or games you play send little packages of information to the game server or web server where data is stored. These packets have to make trips back and forth from these server hubs to your computer or game console, requesting and sending information back and forth. Along the way, they bounce through nodes, or hubs, that make up the backbone of the internet. Sometimes, these hubs will lose some of your packets of information, so the game server doesn't have complete information when it sends packets back to your game. This results in what you see as "hitching," "slingshotting," or momentary game freezes where you either stop or run in place for a few seconds before a bunch of things happens at once.
As always though, I'm passing along feedback on these issues to the team and I'm happy to submit matchmaking IDs to the team to pull the logs to see if there is anything funny happening that we can improve.
devtrackers.gg