Widow Bug/Issue Megathread w/ Video Examples (updated? 25 January 2019)

[brokenstyli-1993]

A followup response/turning this into a wiki would be lovely, but I’ve learned not to get my hopes up.

[Ashcrow-21986]

Blizzcon: We have three new heroes all of them are in the stun category, we also nerfed brigitte healing by 10 but now she can cleanse players to help balance the new heroes, Hanzo’ is nerfed removed his leap, but Fixed E lowered the damage of sonic arrows by 10 and his cooldown to 3 seconds but we also lowered sonic arrow to 3 seconds so u can spam it, We also added a new passive for widdowmaker auto regen we thought a 11 second grip is not enough even when getting healed.

[brokenstyli-1993]

I’m not entirely sure what exactly you’re suggesting for Widow.

Regardless, this isn’t at all related to the thread, which is for bug tracking. If you have any reservations with Blizzard, feel free to make your own thread.

[Ashcrow-21986]

just trolling complaining how broken these characters are and will never get fixed

[brokenstyli-1993]

4. Hanzo’s hand shouldn’t be blocking headshots any more and the rest of the hitbox issues should also be resolved.

Is this scheduled for the next PTR update? As of the time of writing this post, the current Live and PTR patches do not have this fixed;

• https://gfycat.com/CoolAnguishedIndianrockpython
• https://gfycat.com/FamousAnchoredClumber

Another example from PTR;
https://gfycat.com/AdmiredRepulsiveAgouti

[Sandity-1715]

Hope you can get widowmakers bugs and whatever other issues with her resolve o /

[TomPowers]

Hi brokenstyli,

You should now be able to edit your list/post as you intended.

Thank you for your patience.

[brokenstyli-1993]

Wait what? No, I didn’t ask to be given Trust Level 3. I asked for this post to be made a wiki.

My post wasn’t a disguised request to get Trust Level 3, I said that specifically to emphasize how much time had passed between me posting the bug list, and getting a response. And how checked out I am after waiting so long that I don’t even want to continue maintaining the bug list and how unreasonably high the requirements for maintaining Trust Level 3 are…

Unless you globally changed the requirements for Trust Level 3, that’s not fair to anyone that has to grind away the read posts count.

[Xaron-1831]

At least now you can make it a wiki

[brokenstyli-1993]

This sets a really bad precedent.

Can anyone check if Trust Level 3’s requirements went down globally? How do you even check that?

[Xaron-1831]

I mean if you find someone who you know for a fact wasn’t level three, you can look at their .json and find out yourself.

But let’s be real; bad precedents have been the name of the game for the last few months.

[brokenstyli-1993]

@Xaron-1831

I mean if you find someone who you know for a fact wasn’t level three, you can look at their .json and find out yourself.

Just checked. It’s not a global change.

This is not okay. I specifically said that I didn’t expect to be a special exception and magically re-unlock Trust Level 3 (in another thread criticizing decay in Trust Level 3.)

@brokenstyli-1993

I mean, I can’t (and don’t) expect to get Trust Level 3 magically unlocked for me by the mods … and I’m no longer involved with Widow anymore, but it should still go on the record that decay is a dumb system.

[TomPowers]

Wait what? No, I didn’t ask to be given Trust Level 3. I asked for this post to be made a wiki.

My post wasn’t a disguised request to get Trust Level 3, I said that specifically to emphasize how much time had passed between me posting the bug list, and getting a response. And how checked out I am after waiting so long that I don’t even want to continue maintaining the bug list and how unreasonably high the requirements for maintaining Trust Level 3 are…

Unless you globally changed the requirements for Trust Level 3, that’s not fair to anyone that has to grind away the read posts count.

Hi Brokenstyli,

I apologize, I misunderstood your intent. I never perceived this topic as a guise for you to gain Trust Level 3. This topic is constructive and beneficial. We love it.

I permitted that Trust Level gain since you specified you were limited to editing your original list/post. The developers and myself can tell that you put a lot of effort and time into that post, that’s why I wanted to make sure you had all the tools to update it with the information/insight the developers provided above, if you wished it. I see you no longer want to maintain this, so I’ll revert your Trust Level. This original post looks like it’s already a Wiki, so we’re set with that request.

Thank you.

[brokenstyli-1993]

@TomPowers

This original post looks like it’s already a Wiki

That was the first thing I did after seeing that I was Trust Level 3.

Thank you for your response. Especially since, for this, you picked up where a retired Community Manager left off and the transition couldn’t have been easy… Despite my sour feelings and disagreements about how Widow is being handled, I really do appreciate the response.

If this is the start of an ongoing dialogue, instead of a one-and-done status report, then maybe it wouldn’t have felt like a waste of 8 months to maintain this list. Not trying to throw shade here, but it’s been really hard not to.

For fear of painting a target on my back, this video clip for TF2 –

What Team Fortress 2 NEEDS

– (timecode 9:35) … sums up my recent feelings with Overwatch right now, at least in regards to Widow, developer communication, and bugfixing.

Community engagement feels like it has dropped off entirely… what happened to the developer update videos?

I’ve said this in multiple threads. Frequent responses… even if the response is literally “Nothing to report at this time, stay tuned”, those responses feel more communicative and transparent than being radio silent.

Can this be the start of an ongoing dialogue? Can we get a roadmap? something I don’t think is too unreasonable to request since other games under the Activision-Blizzard publishing label exactly have a roadmap.

Can we get more responses to followup questions after an initial blue response (below)?

@brokenstyli-1993

@TomPowers

4. Hanzo’s hand shouldn’t be blocking headshots any more and the rest of the hitbox issues should also be resolved.

Is this scheduled for the next PTR update? As of the time of writing this post, the current Live and PTR patches do not have this fixed;

• https://gfycat.com/CoolAnguishedIndianrockpython
• https://gfycat.com/FamousAnchoredClumber

@brokenstyli-1993

Another example from PTR;
https://gfycat.com/AdmiredRepulsiveAgouti

@brokenstyli-1993

@TomPowers

10. We’ve reworked this mobility on the current PTR, where pulling up should be more consistent when possible. Additionally, momentum should be better preserved when not.

This change was in the PTR patch before the current one, and it’s not fully explained, but it forces all wall surfaces (not ledges or floors) to automatically slingshot;

• Even though completely halting momentum is a significant source of frustration when it happens, automatically slinging players for all grapples on non-ledges is not the solution.
  • There are times when you do need to stop all momentum, as continuing momentum may cause you get caught in a boop, Graviton, or some other form of CC.
  • If this does pass through PTR testing please change it to a user-customizable toggle so that players have the choice the same way backwards wallride exists for Lucio as a user toggle.
• Autosling doesn’t work on certain map geometry – Horizon Green Room glass breaks this entirely;
  • https://gfycat.com/UnimportantFreeAsiaticlesserfreshwaterclam
• Autosling doesn’t work on floors. This seems to be intentional (just like Hammond can’t grapple to floors), but it should work on floors – having been done countless times in OWL and Contenders, and cited as a reason by passionate Widow players to be why her recent grapple hook nerf went through, most Widow players have migrated to this technique, with a low grapple auto-aim sensitivity setting.

@TomPowers

11. This should also be resolved on the latest PTR build.

Is this slated for an upcoming PTR update? Or do you mean that it has been resolved on the current PTR patch?

Playing around with the new autosling, I’ve noticed that a lot of short-range grapple hooks have caused way more frequent unintended-direction slingshots.

I unfortunately don’t have footage to show for it.

@TomPowers

14. As noted in point 8, we intend to remedy the auto-aim, which is impacting the animation in instances like these.

How exactly do you plan on remedying auto-aim without slowing down the ability?

Can you elaborate more on this? If there’s nothing to report right now, can you explain it in more detail when you implement those ideas?

@TomPowers

19. Bullet tracers and movement should be synchronized and if the videos are synchronized by that, the view should generally match pretty closely!

I manually edited these clips with each other and could not get bullet tracers and movement to synchronize at any point. The only point of reference I could use to sync were elimination icons, which are in sync with each other, down to an exact timing.

I understand there is some interpolation and networking compensation at play, so the replay system must be using the server’s capture of interpolated inputs instead of a client’s raw input recordings.

However, I’ve also captured a separate video that I posted on the old forums, comparing 2 separate manual recordings of a highlight, with a highlight export.

https://www.youtube.com/watch?v=rfvPsOvUfKE

The above video was made when the Highlights export feature was brand new, but I’m still pretty certain that no two viewings of the same highlight will be synchronized, even to this day.

This is the exact same highlight being replayed multiple times, and each time the inputs don’t match up – they simply aren’t frame perfect with each other.

And because of that, I’m concerned about the false reports that happen because of how unpredictable/unreliable replays are.

Are there any improvements to the highlights that are inbound that might help assuage these concerns? Is there an ETA on the theater mode (full match replays)?

Or is this just going to revert to another 2-3+ month radio silence?

[DråghYem-2703]

Wow,

What an impressive feedback
It’s help me to understand some situations i lived in game.

Thank you for writting such a detailed post

[Animefreak3K-2108]

Anything new here? Which bugs are now really fixed?

[brokenstyli-1993]

Gave up on Widow a long time ago, can’t tell ya…

Last I checked (which was the Busan PTR patch) Hanzo still blocks headshots with his forearm, Grappling Hook autotargeting is still a mess, and enemies still pop in around corners from occlusion culling.

The only thing that seems to have been changed is that now all non-ledge walls slingshot. And maybe hit registry?

Edit - New bug discovered by Reddit user /u/topikcz
Widow clips through floor/ceiling – https://gfycat.com/LargeRecklessFawn

[Animefreak3K-2108]

Would be interesting to know, what happend till the last 2 months.
Maybe a dev can tell us?
But i don’t think so

[Critscan-1138]

idk if anyone else said this, but the double bullet trails are packet loss, that symbol on the top right with the 3 squares pops up immediately as you shoot, indicating packet loss

[brokenstyli-1993]

Would be interesting to know, what happend till the last 2 months.
Maybe a dev can tell us?

Almost everything is still exactly the same as the bugfix patch.

• Grappling Hooks will now automatically slingshot you on every single non-ledge, non-floor cast.
  • Horizon Lunar Colony’s Green Room windows (and some other targets) have not been fixed. They still do not autosling you.
• Grappling Hooks towards ledges will sometimes cause Widow to slide/clip through railings/ledge walls, instead of swinging you up and over, in order to reach her intended destination faster.

idk if anyone else said this, but the double bullet trails are packet loss, that symbol on the top right with the 3 squares pops up immediately as you shoot, indicating packet loss

I’ve had to explain this dozens of times, so let me be clear on this.

The doubleshot/misprediction bug wasn’t packet loss, it was the resending of packets immediately after dropped packets, with incorrect aiming coordinates caused by the camera’s kickback from recoil, causing missed shots.

Floorshots suddenly hit enemies, which never happens on a normal desync/packet loss/no-reg, see this video – https://gfycat.com/PresentForsakenGelding

The game is supposed to resend packets with the same information as fast and as soon as possible, and it wasn’t doing that for the longest time… it resent packets aimed slightly higher than it was supposed to…

This was allegedly fixed in the patch after the bugfix patch. There weren’t any patch notes for it though, and it was already difficult to test to begin with. I have not noticed it since the bugfix patch released, so it might have been fixed?