Stuttering/packet loss/lightning bolt with arrrow - help

Keep getting the lightning bolt with arrow and packet loss little orange icons when trying to play OW2. Tried almost everything I can think of to fix. Tried capping frames, same issue. Any help would be great makes the game hard to play.

Windows 11
13600k
3080
32gb ddr5

https://www.reddit.com/r/overwatch2/comments/yn3v84/stutteringlag_issue_in_game_not_sure_how_to_fix/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

This is an example of what it looks like

1 Like

Replying and bumping hoping you get traction, same issue, no responses, ISP confirmed healthy connection at my side, and I’m at my wit’s end.

I wrote up a more detailed post with steps to replicate and context Rubberbanding/Lag Issue Replication & Detailed Steps

My guess is its a combination of player volume, waiting for a player volume stabilization before committing/optimizing resources, and/or some of the new tech/monitoring is behaving poorly in certain configurations. Its frustrating because we have no idea if its being worked on at all.

Hey there,

Packet loss or latency spike issues like this can be caused by a lot of different things. Wireless issues are most common, so if you are using wifi try swapping to a wired ethernet connection.

There may also be issues between your ISP and the game servers or along the route which is causing the packet loss. I recommend running WinMTR to try and capture where exactly packet loss is happening.

  1. Download WinMTR
  2. Right-click on the downloaded .zip folder and select “Extract All”, to extract the files to a new folder.
  3. Open the new folder that was created, then open the WinMTR_x64 folder.
  4. Right-click on the WinMTR application and select “Run as administrator”.
  5. Launch Overwatch and join a match. Once you’re in the match, press Ctrl+Shift+N to open the Network Graph.
  6. Look for the server name displayed in brackets and the IP address at the top. Note you will need to remove the colon and port number after the IP address before running the test. (12.345.67.89:PORT)
  7. Alt+Tab back to WinMTR, then type the server IP addres s in the “Host” field.
  8. Click on “Start” and Alt+Tab back into the game. Allow the test to run for at least 10 minutes or the duration of a match. Click on “Stop” when you’re done playing after you have experienced the latency or connection issue.
  9. Click on “Copy Text to Clipboard”, paste the results here, then highlight everything and hit the </> button in the posting section so it will allow links.
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.1 -  100 |  113 |    1 |    1 |    1 |    1 |    1 |
|                          10.138.140.130 -    0 |  553 |  553 |    8 |   12 |   32 |   11 |
|                           68.86.120.129 -    0 |  553 |  553 |    8 |   12 |   32 |    9 |
|                          96.216.134.102 -    0 |  553 |  553 |    8 |   12 |   31 |    9 |
|                           96.216.134.49 -    0 |  553 |  553 |    8 |   13 |   33 |   10 |
|ae-97-ar01.pontiac.mi.michigan.comcast.net -    0 |  553 |  553 |   10 |   14 |   48 |   12 |
|                           96.216.134.10 -    0 |  553 |  553 |   10 |   17 |   59 |   13 |
|be-32111-cs01.350ecermak.il.ibone.comcast.net -   84 |  130 |   22 |    0 |   21 |   24 |   22 |
|be-2111-pe11.350ecermak.il.ibone.comcast.net -    0 |  553 |  553 |   16 |   20 |   66 |   18 |
|as8075-1-c.529bryant.ca.ibone.comcast.net -    0 |  553 |  553 |   16 |   24 |  108 |   19 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|         et-0-0-0-pe01-eqch2.as57976.net -    0 |  553 |  553 |   16 |   20 |   56 |   18 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  112 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like

@Jambrix I’ve done this and there is no loss or unusual ping spikes between the root node and the last responsive node (once GCP is hit, the servers no longer respond to ping requests).

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.