devtrackers.gg
We're really sorry about this.
Apparently we experienced a network outage for a short time that affected our PS4 players as well as some of our EU players.
The issue should be resolved now.
We're really sorry about this.
Apparently we experienced a network outage for a short time that affected our PS4 players as well as some of our EU players.
The issue should be resolved now.
Was I right with the off by 1 comment I made?
Hey there, the bug was not an off by one. The issue was introduced while making optimizations for lower spec hardware. In some cases sound occlusion wasn’t recalculated when it needed to be.
Cheers
hey /u/BillWarnecke not sure if you're still seeking examples of this missing sound bug, but i have one for you.
here is a clip from a live game where a tracer's ult line does not play:
https://gfycat.com/shadowyclumsyalaskanhusky (idk how familiar you are with gfycat but the sound is not on by default)
and here is a clip of the same moment in the replay where the ult line plays correctly:
https://gfycat.com/impressivemindlessamericanlobster
it seems like tracer plays a grunt that blocks the ult voiceline in the live version whereas the replay doesn't have the grunt for some reason.
This is fixed in the next patch, thanks for taking the time to report details here though, it is much appreciated. Cheers
Oooo an official!! I have a question: My game does not find me any competative games at all and the weekly rewards always say 1min left. Is there a way to fix thisnor could you input a word to look into this? (I play on switch and live in australia but all thr custom games are in korean I think so not sure what server am on). Also could there possibly be a way to change which server (e.g south america, europe...)
Hey there if you can send me a private message with your name as it shows up in game I can look into this.
For Nintendo Switch we matchmake players to where you get the best ping. It’s possible in your area or due to the times you play the best games are in the Korean data center.
Cheers, sorry for the hassle.
Hold up you’re the real blizzard in our console threads?! You care about us console players?!?
Of course! I post here pretty regularly :) cheers
Hey there, we had issues with our servers in South America earlier. We’ve resolved the problem, sorry for the hassle.
Hey there, we're looking into this issue. While we work on fixing the problem you may end up in games in other datacenters outside of SA, sorry for the hassle.
Servers are coming back up in the SAE1 site now, sorry again for the disruption. Cheers
Hey there, we're looking into this issue. While we work on fixing the problem you may end up in games in other datacenters outside of SA, sorry for the hassle.
Why not label it 1.44.1 ? Why the extra zero ? Is there more important stuff coming ?
I tend to manage our branches, in this case Overwatch League will be using “1.44.1.0”. It was intentional that they were downstream of all 1.44 live changes.
The final digit in our branches is used when we have a patch that is not protocol/data compatible with what is already released. That was the case for this mid cycle bug fix and balance update, so it became “1.44.0.1”.
In practice, because we do a “major” revision about once a month, we don’t end up having too many cases where we need the last 2 digits for the branch. When we do have cases like this it’s sort of confusing for the team (for people who don’t look at branch details every day).
We could probably be more clever but we have a pretty significant build infrastructure built around this convention, so for now it’s not changing. :)
Cheers
Hey there I sent this post over to QA to dig into. Thanks for the report, anyone who has additional video or details please share in the comments if possible.
Sorry for the hassle, cheers.
the game should only be cancelled if someone on the enemy team did not engage in combat. sometimes players do not realize that there is someone on the other team AFK back in the spawn room and that is the reason the match is being cancelled.
if you think there is a bug and want us to look at the replay, please post your battletag (and possibly the time/date you were playing) and we'll try to find the match. or if you have a video of the match, we can track it down.
[deleted]
Tomorrow is the eta. Cheers
Congrats on the Victory!
For folks who stumble upon this thread, the network icons that appear on the left give the clues to what is happening here. We have some detail about what they mean in a support article.
Hopefully things cleared up naturally, but if not, head over to our tech forums and hopefully we can help out.
Cheers
[deleted]
This bug requires a matching client and server update, we’re hoping to release it late this week. For a bug fix release where we do both client and server it’s important we get all major issues resolved for the update because of how the console certification process works.
Sorry this one isn’t as fast as we’d like to turn it around. Cheers.
Hey there, Overwatch 2 will ship on all platforms that we already ship Overwatch on. No need to worry. Cheers
Any feedback about the endorment level gone for a lot of players? Also a message, yes we know it's fine. Dead silence right now. I just lost my lv3-4, people with lv 5 are probably mad about it. And of course it happened during the event, so no free lootboxes. I already know nobody is going to get it back, but say something.
Hey there sorry we haven’t communicated out about this bug yet. We’re working on a fix for the bug and working to repair accounts that were affected. No eta but we’re actively working on it.
...big fix or bug fix? I don't want to get too excited.
Also on the off chance you reply to this, is there a reason Sombra's hack colors are inconsistent?
Bug fix, my bad. Can you post examples of what is inconsistent and I’ll look it over with QA. Thanks
Hey there we have a fix for this we’re hoping to get out in an upcoming bug fix patch. Sorry for the hassle. Cheers
Hey there we’re testing a fix for this and hope to get it out in an upcoming bug fix patch. Cheers
Hey there sorry about this bug. We’re testing a fix internally and hope to get it out in an upcoming bug fix patch. Cheers