Original Post — Direct link

I've been told the dev that implemented this is stuck on keeping it around pretty adamantly. I've hoped it would go away every single time a patch comes out but every time it's still there.

Voice lines should only say what they are written as. I'm also very tired of Ping - In World randomly placing pings from the wheel, such as "Defending Here", "Fall Back", and most confusingly, Countdown.

The new communication system has so much potential that is being squandered by stubbornness and lack of maintenance. Can we get it polished up, please?

External link →
about 1 year ago - /u/blizz_winter - Direct link

Hey all, in the mid-season patch we're adding a new setting that will control whether contextual pings for Group Up and Need Healing would be used when aiming at an allied hero. The default will be "Off".

Contextual pings were a feature OW1, but as someone with thousands of hours in OW1 I didn't know this until players in the OW2 beta started pointing out that they weren't getting their intended "I'm with you" prompts anymore when aiming their Group Up comms at allies. When I reimplemented this feature for OW2 just before launch I made some mistakes, like letting this ping type pass through walls and letting it go an effectively infinite distance. This meant that before Season 4 we had that happening way too often.

Those bugs are all fixed now, but I realized a few months ago (because of reddit posts like these) that the number of players that wanted this feature is likely much smaller than the number of players that do not want this feature, hence why we've taken the time to make it a setting. You can read the post history of my account if you'd like to know more about this topic.

With regards to general concerns about Ping - In World placing the wrong pings from the wheel, I suspect these are mostly commonly cases where the default setting of Ping Wheel Press Delay (found in Options -> Controls -> Communication -> Ping Options) is too low for some players. Increasing it from the .18 second default to a higher value (like .3) should prevent any cases of this occurring.

This was a really hard number to tune, because the higher this number is the less responsive the system feels, but the lower it is the more frequently we get these accidental pings from the wheel. Other posters in this thread mention the movement-based shortcut we had when OW2 launched being a potential problem. This was removed last season, so it shouldn't be the cause anymore.

In the specific case the OP is describing though (based on their comments in this thread), it sounds like we may have a bug. The last person I helped solve this problem had a faulty mouse, but several months ago it was possible for Ping - In World to fire an unintended type of ping under some very specific circumstances. We fixed that bug, but if there's another like it I wouldn't be surprised. If you have any video of this or any other undesirable behavior from the ping/comms wheel occurring that would be very helpful!

Another highly upvoted comment in this thread mentions the "Come to me for healing" prompt being used when aiming at injured allies near an objective. You can reduce the likelihood of this occurring by reducing the Injured Ally Ping Sensitivity setting in Options -> Controls -> Communication -> Ping Options -> Advanced. This is really a question of priority though, and our objective pings have the lowest priority of all ping types. It sounds like this setting probably isn't handling this issue well enough, so I'll be thinking about future solutions for this one.

about 1 year ago - /u/blizz_winter - Direct link

Originally posted by Stoppablemurph

My wife actually had to completely disable the ping wheel because even when the hold duration is increased to the maximum, if you move the mouse while holding the button, it still brings up the wheel instantly. The wheel coming up also means it's "stealing" the player input. In a lot of situations it's not a big deal, but it becomes more of a problem as things get hectic and you're trying to ping an ulting Genji and protect your healers.

She ended up binding a more specific "enemy here" ping option to a button instead, since that doesn't trigger the wheel, but now she can't do certain contextual point options like pinging the objective, or more importantly pinging whoever just killed her.

It would be nice if there were an option to bind the ping wheel and the generic ping button separately.

We disabled that movement based shortcut in season 3 for mouse and keyboard, so she might have more luck trying it again today.

about 1 year ago - /u/blizz_winter - Direct link

Originally posted by WitheredBarry

First off, I'm ecstatic to see that this issue is being taken seriously! Thank you for the detailed response.

As for the accidental incorrect pings, u/aurens singled out the problem and I have recreated it repeatedly. For your reference, I am on PS4 but the issue also occurs on PC, according to aurens. The ping wheel delay function works fine if the ping button is held and the player doesn't move. HOWEVER, if the player makes any directional input at all for their POV (aka mouse movement or right thumbstick movement) , the delay is overridden and the wheel pops up instantly.

In the heat of battle this results in players repeatedly quick pressing Ping - In World only to have the ping wheel flash onto the screen for a millisecond as a specific ping is chosen by accident because they were moving. This is unavoidable unless you are inputting absolutely nothing into your POV controls, and as we all know, an unmoving player gets a hole in their head.

Fixing this should be simple, by just making the Ping Wheel Press Delay setting absolute; the ping wheel will NOT come up NO MATTER WHAT until the delay is has passed.

Again, thank you for the response and I hope this thread and hopefully this post have provided the feedback you need to resolve this issue!

Thanks for the description. We removed this shortcut feature for mouse and keyboard last season, but I see now that it was not removed when using a controller. My apologies for that oversight.

I can't make any promises with regards to the timing of removing this feature for controller, but I will work on removing it there too.