I’ve this weird issue for a while now. Two, actually.
I noticed that the probability of an ability actually happening is not 100%. In the last match alone, I was trying to cast Furnace Blast (Butcher) at least 5 times without anything happening, but my recent run with Jaina also was quite Blizzard-less. Movement is fairly stuttery as well, so maybe my game is running on guesstimations a lot - about 2 years ago I was complaining about endless reconnection cycles. In that sense, it’s better.
The second, absolutely weird experience is that my game stutters way more when we’re ahead. It’s as conspirational as it gets, and I cannot explain. It is very successful at curbing games, though, ensuring a sub 50% winrate. I highly doubt that the game gets excited or worried about winning, but there must be some communication that is more likely to happen within a winning team - at the bare minimum, it’s late game vision and APM.
Also, vertical sync doesn’t work which may cause overheating and the above consequences.
My old laptop would play at like 30 fps and drop down to 15 regularly when everyone was on screen. That’s the first thing that came to mind with your second issue.
Most likely, they’re both from connection issues.
For past 2-3 days, can’t really play the game either. Some matches I’d constantly reconnect every 10 seconds or so. Weirdly, just in qm, aram worked fine.
Stuttering is usually caused by another player leaving or rejoining the game. If you don’t see a message that it was one of your teammates, it usually means an opponent disconnected (bigger stutter) or reconnected (usually a smaller stutter.) You may notice it more when you’re ahead because an opponent is purposely throwing or possibly AFK for some time and then getting kicked.
I opted for the latter (4 years ago) and while it’s quite potent in many ways and I’m mostly happy with it, a select few games aren’t doing well with it. For example WoW is pretty neat while good old Train Sim Classic performs the same frame rates as my old Nvidia 970. Heroes feels the same. It might be related to DirectX 9/11, not sure.
That can be it sometimes, if only them having mild connection issues.
In my case it’s rather constant micro-stutters. It is definitely one part heating issue, when it happens the FPS also goes down from ~105 to ~75 (screen is 1080p@60). Based on Task Manager values that should be around 90°C (194°F).
Ever since the game came out, I find some heroics or abilities don’t cast with 100% certainty. Stitches Gorge, Kharazim Divine Palm and Brightwings Polymorph come to mind.
I sometimes had to mash the button several times for it to cast.
The issue cannot be replicated in try mode whenever I try it. Only happens on the rare occassion in live matches.
Indirectly related, in the new patch Falstads Hinterland Blast cooldown gets reduced for heroic hits but the ability itself refuses to deal damage. This too does not happen in try mode, only real games.
Definitely sounds like you’re on the right track with it being thermal then. Have you tried setting frame rate limits with Adrenaline? Having a 100+ frame rate with a 60Hz monitor is giving you essentially no benefit, but with significantly more heat output.
I would sort out the fps cap first because there’s a good chance that thermal throttling is causing the other issues.
My brother has a laptop with an RTX 3070M, and he told me it started stuttering really bad in HotS and other games about 4 months ago. He never found a solution that I remember. We were thinking it must be a Window update that did it, because it wasn’t drivers or thermals. He has an older laptop with a GTX 960 and it plays fine.
I noticed in 2020 upon playing cross-continent that casting Rehgar Q got extremely difficult - my assumption being that I give the command but the server verifies it, based on mouse coordinates. Since my target wasn’t there anymore, the ability failed.
However, it shouldn’t affect area cast abilities such as Jaina Blizzard or self-buffs like Butcher explosion. Unless movement can still cancel those.
My setting is “On, unless application specifies”.
I’ve flipped to “Always On” now.
In-game it’s set to On, so it should be no difference.
The setting can function, TSC is at the very least working with it.
Definitely.
Interesting. I don’t exactly remember my timeline but I recall rate limits being functional for a while. (Had to switch to this laptop about 2 years ago.) The stutters, or rather “Reconnecting” state was constant since forever, though. Unfortunately I couldn’t go back to my desktop to check.
This is caused by packets being delayed or dropped between your client and the server. The lockstep system has a small tolerance window for late commands, but once that window closes, the tick proceeds without the missing input, so a command that arrives even slightly too late is the same as one that was never sent. From your perspective, the ability simply didn’t fire. It can happen with any ability or movement command. On your end, the best mitigations are a wired connection if you’re on Wi-Fi, and closing any other apps that hog bandwidth.
I didn’t remember correctly, when I asked him for more details, he said that turning the fans on full does help it. Not fully fixes it, but makes it less frequent, so maybe it is a thermal issue for him.
I have frequently had issues casting Rehgars chain heal without there being like a 0.25s delay. On rare occassions pressing Q did nothing or Rehgar raised his hand as if to cast the spell and nothing happens.
Even with ctrl+alt+f showing very low pings like 30ms.
I think GriM is onto something with the packet loss, because when you open an instance in Try Mode (which afaik, is local on your network) this never happens.
This is checking out your own local and technical problems but I guess you can do the same thing with Blizzard’s server if you find their IP addresses. The numbers I’ve seen are probably no longer accurate because they’re wildly different on each website so you’ll have to look around.
Alrighty. A patch happened and I’ve changed the setting as described.
It may have helped a tiny bit, but not sure.
I ran my last match with frame rate monitors on. In the menus it’s 60. On the loading screen it’s 20. In game it’s 65-130 (highest at the very beginning, no heroes in sight). As soon as the match ends, it goes back to 60. Not sure whether already as focusing the core or showing the MVP voting UI.
It felt a little better though, but it may have been Murky.