I keep getting a brief stutter that happens every few seconds. the stutter is nearly instant but you can imagine a stutter every few seconds gets pretty intrusive on my gameplay. HotS is the only game I have this issue on. My PC specs far surpass the minimum. Myspecs are:
CPU: I7 - 7700k
GPU: Nvidia GTX 1080
16 GB of RAM
This is usually caused by an unreliable internet connection between your computer and the HotS servers. The stutter is due to your client pausing to wait for the HotS servers to respond.
I recommend running the support recommended ping, trace route and winMTR tests to check for this. Ideally you want 0% packet loss with sub 100ms latency and a very small standard deviation.
I can’t figure out how to paste the file to the reply but this is the text format of the WinMTR from a play session i had. No packet loss at all ```
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| - 0 | 8632 | 8632 | 0 | 0 | 0 | 0 |
|____________|||||||
Hey there Señor,
The issue does sound like a connection issue, although interfering programs or a hardware issue may also be a factor. What you pasted above doesn’t seem to show a problem. I’m wondering if you can paste the entire Winmtr test or grab a new one while this is happening.
Typically we just want to run the test for 3-15 minutes(a full match is fine even), restarting the test if nothing occurs in that time frame. When a problem happens, let the test run an extra minute and then end it. Save the results, then open the text file and paste them here between two ~~~ like so:
MTR Here
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
I’d also like to glance at a Dxdiag too. Once you have it, you can copy/paste it here just like the Winmtr results. A single post with them 2 files combined or 2 separate Pastebin links may be needed for all this.
This is whats inside the full WinMTR text file. I did everything the WinMTR guide said to do. I can’t paste the actual file but this is close enough i figure. I’ve never had issues playing other games. I’ve had this problem persist solely in HotS throughout the years and its the main reason I can’t get into it. I love the game otherwise.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| DESKTOP-H83M8MN.lan - 0 | 1209 | 1209 | 0 | 0 | 0 | 0 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
My DxDiag is:
Here’s my DxDiag as well.
Operating System: Windows 10 Pro 64-bit (10.0, Build 19043) (19041.vb_release.191206-1406)
Processor: Intel(R) Core™ i7-7700K CPU @ 4.20GHz (8 CPUs), ~4.2GHz
Card name: NVIDIA GeForce GTX 1080
Display Memory: 16253 MB
Dedicated Memory: 8079 MB
Memory: 16384MB RAM
Available OS Memory: 16348MB RAM
DirectX Version: DirectX 12
Hey there,
It looks like you might be using your own IP address for the “Host” in the WinMTR tool. You’ll want to use the IP of the game server instead:
Central US:
24.105.62.129
Leave that running in the background while playing a match then post the results and we can take a look.
This is what I got
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| www.webgui.nokiawifi - 0 | 1534 | 1534 | 0 | 0 | 6 | 0 |
| 192.0.0.1 - 0 | 1533 | 1533 | 0 | 0 | 11 | 0 |
| 192.0.0.1 - 0 | 1533 | 1533 | 13 | 22 | 290 | 19 |
| No response from host - 100 | 310 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 310 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 310 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 310 | 0 | 0 | 0 | 0 | 0 |
| 10.160.174.169 - 0 | 1533 | 1533 | 14 | 23 | 266 | 23 |
| 10.177.76.65 - 0 | 1534 | 1534 | 23 | 28 | 247 | 32 |
| 10.177.11.119 - 0 | 1533 | 1533 | 19 | 30 | 220 | 26 |
| 10.164.165.115 - 0 | 1533 | 1533 | 19 | 28 | 182 | 25 |
| eqix-da1.blizzard - 0 | 1533 | 1533 | 24 | 34 | 243 | 44 |
| ae1-br01-eqda6.as57976 - 0 | 1533 | 1533 | 44 | 56 | 290 | 54 |
| No response from host - 100 | 310 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe01-eqch2.as57976 - 0 | 1533 | 1533 | 46 | 54 | 278 | 51 |
| 24.105.62.129 - 0 | 1533 | 1533 | 46 | 54 | 259 | 51 |
Are you using wifi? If so that is likely the cause of the problem as Wifi often struggles to achieve high levels of reliability. In this case try to use an enternet connection directly with your router.
You can see from the report that your worst case latency is significantly bigger than your best latency and average. This large fluctuation is what is causing the stutter as every time the latency jumps up to 6-7 times as long for a brief moment the HotS client must pause and wait for the server’s response.
Other games might not be as noticeably affected by this due to them client local latency compensation. Such games with latency compensation include Overwatch, Diablo II/III and World of Warcraft as well as competitors like HoN, LoL and DotA2. In such games with latency compensation these worst case latency spikes result in other characters jumping around or having visually out of place corrections applied to them.
I have an ethernet connection. This issue has been happening since HotS released. I had fiber before and it was happening is well
What ever is the cause seems to be happening in the hop between these two devices. Being a local IP address it seems to be within your local network? I am unsure why both entries have the same IP address, not encountered that before.
Mmmm i’m not quite sure i’m understanding you right. Yeah it’s my home internet that I’m on. The only device connected to the modem is my pc so I wouldn’t know why there’s two devices. No clue then huh? 
It only happens on heroes of the storm. I figured it was something to do with my hardware but I’ve done all the testing I can and I haven’t found anything.
I’m getting a similar issue. My game lags for a second every 10 seconds.
here’s my WinMTR data
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| SAGEMCOM - 0 | 1005 | 1005 | 0 | 2 | 90 | 1 |
| 10.11.0.225 - 1 | 994 | 993 | 4 | 75 | 1770 | 8 |
| No response from host - 100 | 203 | 0 | 0 | 0 | 0 | 0 |
|cr02-toroon2148w_0/2/0/8_lr4.net.bell.ca - 0 | 998 | 998 | 6 | 77 | 1770 | 8 |
|cr02-toroon4772w-bundle-ether5.net.bell.ca - 0 | 998 | 998 | 6 | 77 | 1802 | 10 |
|tcore4-toronto47-bundle-ether48.net.bell.ca - 0 | 998 | 998 | 5 | 78 | 1802 | 30 |
| dis4-toronto47_7-0-0.net.bell.ca - 0 | 998 | 998 | 5 | 75 | 1754 | 8 |
| tcore3-toronto47_1-0-0-3.net.bell.ca - 1 | 990 | 988 | 20 | 87 | 1770 | 23 |
|tcore3-chicagocp_hundredgige0-3-0-0.net.bell.ca - 1 | 994 | 993 | 20 | 92 | 1802 | 21 |
| bx9-chicagodt_ae0-0.net.bell.ca - 0 | 998 | 998 | 17 | 85 | 1770 | 31 |
| lag-101.ear7.Chicago2.Level3.net - 92 | 218 | 18 | 19 | 25 | 109 | 22 |
| ae2.3211.edge7.Paris1.level3.net - 3 | 916 | 895 | 110 | 166 | 1905 | 114 |
| BLIZZARD-EN.edge7.Paris1.Level3.net - 2 | 948 | 935 | 106 | 163 | 1905 | 1227 |
| ae1-br02-eqpa4.as57976.net - 5 | 842 | 803 | 111 | 193 | 4360 | 1845 |
| No response from host - 100 | 203 | 0 | 0 | 0 | 0 | 0 |
| 137.221.65.77 - 5 | 839 | 800 | 111 | 232 | 3968 | 3968 |
| et-0-0-31-pe02-eqam1.as57976.net - 3 | 920 | 900 | 110 | 165 | 2074 | 113 |
| 137.221.66.47 - 2 | 931 | 914 | 110 | 167 | 2016 | 114 |
| 185.60.112.157 - 2 | 928 | 910 | 110 | 164 | 1904 | 114 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Usually it is better to make separate threads
For you the issue seems to be happening between SAGEMCOM and 10.11.0.225. 10.11.0.255 is a private IP address so might relate to your local network infrastructure or how your internet service is being delivered.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.