Playing on ME servers and for some reason my game runs fine when I’m in the training bot area but when I load up quickplay or comp I get a match and pick a character and as soon as the match starts the game just dies. Like not on my end but on the servers end. The characters are stuck in place with their walking animations. I can’t even quit the game without exiting to desktop.
Checking using Ctrl + Shift + N shows me that the network is fine but as soon as I’m a minute or two into a match I get huge lag spikes and the game just dies. Started happening today, don’t know why.
2 Likes
Hey there,
Lets go ahead and grab a winMTR so we can further investigate the problem. Here are the instructions:
- Download the tool from this page
- Enter the game IP into the “host” field. The IP address for our games are listed on the winMTR instructions page
- Start the test and play the affected game for at least 15 minutes. Ensure the problem happens while the winMTR tool is running.
- After recording the problem data, click “export text” and save the winMTR file in an easy to find location.
- Once you have that made, open the file. You’ll need to copy and paste the contents of the Text document into the post, and put four Tilde (~) marks above the winMTR. It’ll look like this:
WinMTR goes here
If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).
WinMTR |------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.18.1 - 0 | 241 | 241 | 0 | 0 | 1 | 0 |
| 58-65-175-242.nayatel.pk - 0 | 241 | 241 | 1 | 2 | 26 | 2 |
| 172.16.11.149 - 0 | 241 | 241 | 2 | 3 | 38 | 4 |
| 58-65-165-42.nayatel.pk - 0 | 241 | 241 | 1 | 2 | 4 | 2 |
| 203.135.5.69 - 0 | 241 | 241 | 21 | 23 | 27 | 23 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| 150.222.7.41 - 0 | 241 | 241 | 39 | 42 | 60 | 41 |
| 52.93.69.93 - 0 | 241 | 241 | 38 | 41 | 57 | 41 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| 52.93.133.156 - 0 | 241 | 241 | 47 | 50 | 65 | 50 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| 52.93.226.188 - 0 | 241 | 241 | 47 | 50 | 63 | 50 |
| 52.93.226.203 - 0 | 241 | 241 | 47 | 50 | 74 | 50 |
| 52.93.226.202 - 0 | 241 | 241 | 48 | 50 | 63 | 50 |
| 52.93.226.193 - 0 | 241 | 241 | 48 | 50 | 63 | 50 |
| 52.93.227.72 - 0 | 241 | 241 | 48 | 51 | 67 | 50 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hey again,
Thanks for following up! Going over the winMTR test I do not see any unusual packet loss or changes in latency. I did want to ask, did the problem happen while the test was running?
If yes, it might be worth trying a different network (friends house, internet cafe, or VPN) to see if the behavior changes. This can help us further narrow down the source of the issue. Be sure to check online for any restrictions on vpn usage in your area.
If no, please re-run the winMTR test. Ensuring the problem happens while the test is recording so it can track any changes in the data flow!
Hope the info helps. Cheers!
Yes, I started a quickplay match and used the IP I got from using Ctrl + Shift + N. And sure enough while the test was running I got the disconnect. I just logged in and tried a match and got the same error.
I ran the test again: |------------------------------------------------------------------------------- - Pastebin.com
Could also record a video and share a youtube video link if that would help.
Hmm, I don’t see any packet loss in the test so the problem is likely not related to upstream data. Unless it’s de-prioritized by the service provider. I noticed a number of users connecting from the same country as you having similar issues here.
This actually would be amazingly helpful if you could keep the netgraph open while gaming for a bit. I know it’s annoying to look at while trying to get headshots and stuff but it should yield some good data for us.
Once you have the video could you follow up with me on that other thread? I’m suspecting that it could be a routing issue of some kind since many users in the same country are having similar issues.
If possible please also run this looking glass test. It might be difficult to grab it at the right time but if you run it at around the same time as the disconnect I’m hopeful it will show the data. Looking Glass is downstream vs winMTR which is upstream. Gotta check both sides of the connection!
Cheers!
1 Like
Link: Youtube link to problem: https://youtu.be/RMnytMb3wG0TRACEROUTE:tracerou - Pastebin.com
Ran the looking glass test just as I got control of my character. Since the disconnect for me happens 8-10 seconds after I get control of my player character in a match. The YouTube video link is included at the top of the text.
In the video it shows the network icons flashing to alert you of a connection problem. This is very likely related to the issue that Kaldraydis mentioned in the other thread, since you’re connecting from the same country. Unfortunately, the test shows the ISP hops losing all of your data, so you’ll want to show them the results to work on a resolution.
I’ll ask with my service provider and get back to you on this.
Although if multiple other people from the same region are experiencing the same issue maybe there’s a common point of failure between the region and blizzard servers?
1 Like
That’s absolutely possible (and probably in this situation), but Blizzard only controls their servers and they have contracts with the routing peer that is 1-2 hops before the server. This means if the point is somewhere in Pakistan, which it appears to be from the tests, this would be beyond their control. As a customer, you are unlikely to be able to communicate with the routing peers the ISP is using. They would need to investigate this on your behalf.