BillWarnecke

BillWarnecke



19 Jul

Comment

Originally posted by BillWarnecke

Hey everyone, we're aware of the reports for this and we're actively working on it now. Sorry for the disruption, we'll work to get a fix out with urgency, though I don't have a specific ETA yet.

edit: As an update for everyone we have an update that's going into certification for this issue and we will release the patch as soon as that is complete. Depending on our turn around we're hoping to have the update out on Monday at the latest, but we're trying very hard to get it out tomorrow if possible. Thanks again for your patience while we fixed this up.

edit: Details aren't final but we're targeting the update for today on both console platforms. We'll post once it's out (or if there is a delay). Thanks again for being so patient.

edit: The bug fix patch is live for all platforms now. PC players should be on 1.38.0.2.60417, PS4 and XB1 users will be on 1.38.0.2.60360. Have a great weekend!

Hey console folks, details aren't final but we're targeting the update for today on both console platforms. We'll post once it's out (or if there is a delay).

Comment

Hey everyone, for PC players who are still experiencing an issue please double check that your Overwatch client has updated to the fixed version. You can do this by looking next to the Play button in the Blizzard Desktop app, the fixed version is 1.38.0.2.60417.

I checked our debug data for a few people in this thread who were reporting problems still and in every case they were still on the previous unpatched version.

This isn’t a forced update so it can take a bit for the Blizzard launcher to notice that you need to patch. If you want to ensure you’ve updated you can check for a new version via the “Options” menu in the launcher.

If you’re having performance issues that are not specifically related to the communication wheel / chat box - please make a separate thread. Any posts in this thread that are not related to this issue are likely to be missed.

For console players, details aren’t finalized yet, but we’re expecting the update to go out today for b...

Read more

18 Jul

Comment

Hey folks we have a fix for this issue now and we’re working on the schedule for rolling it out. For console players the update is in certification and we hope to release it on Monday at the latest, if things go well it’s possible we’ll have the update tomorrow. For PC players we’re trying to release later today. We greatly prefer to update all platforms at the same time but given the impact of this bug we’re going to roll this update out as soon as it is ready for each platform.

Comment

Originally posted by BillWarnecke

Hey everyone, we're aware of the reports for this and we're actively working on it now. Sorry for the disruption, we'll work to get a fix out with urgency, though I don't have a specific ETA yet.

edit: As an update for console players we have an update that's going into certification for this issue and we will release the patch as soon as that is complete. Depending on our turn around we're hoping to have the update out on Monday at the latest, but we're trying very hard to get it out tomorrow if possible. Thanks again for your patience while we fixed this up. For PC players we're targeting today for a release. In general we prefer to release updates at the same time on all platforms but due to the impact of this bug we're going out immediately as platforms are ready to be updated.

edit: The bug fix patch is live for all platforms now. PC players should be on 1.38.0.2.60417, PS4 and XB1 users will be on 1.38.0.2.60360. Have a great weekend!

As an update for console players we have an update that's going into certification for this issue and we will release the patch as soon as that is complete. Depending on our turn around we're hoping to have the update out on Monday at the latest, but we're trying very hard to get it out tomorrow if possible. Thanks again for your patience while we fixed this up. For PC players we're targeting today for a release. In general we prefer to release updates at the same time on all platforms but due to the impact of this bug we're going out immediately as platforms are ready to be updated.

Comment

Originally posted by BillWarnecke

Hey everyone, we're aware of the reports for this and we're actively working on it now. Sorry for the disruption, we'll work to get a fix out with urgency, though I don't have a specific ETA yet.

edit: As an update for everyone we have an update that's going into certification for this issue and we will release the patch as soon as that is complete. Depending on our turn around we're hoping to have the update out on Monday at the latest, but we're trying very hard to get it out tomorrow if possible. Thanks again for your patience while we fixed this up.

edit: Details aren't final but we're targeting the update for today on both console platforms. We'll post once it's out (or if there is a delay). Thanks again for being so patient.

edit: The bug fix patch is live for all platforms now. PC players should be on 1.38.0.2.60417, PS4 and XB1 users will be on 1.38.0.2.60360. Have a great weekend!

As an update for everyone we have an update that's going into certification for this issue and we will release the patch as soon as that is complete. Depending on our turn around we're hoping to have the update out on Monday at the latest, but we're trying very hard to get it out tomorrow if possible. Thanks again for your patience while we fixed this up.


16 Jul

Comment

Hey everyone, we're aware of the reports for this and we're actively working on it now. Sorry for the disruption, we'll work to get a fix out with urgency, though I don't have a specific ETA yet.

edit: As an update for console players we have an update that's going into certification for this issue and we will release the patch as soon as that is complete. Depending on our turn around we're hoping to have the update out on Monday at the latest, but we're trying very hard to get it out tomorrow if possible. Thanks again for your patience while we fixed this up. For PC players we're targeting today for a release. In general we prefer to release updates at the same time on all platforms but due to the impact of this bug we're going out immediately as platforms are ready to be updated.

edit: The bug fix patch is live for all platforms now. PC players should be on 1.38.0.2.60417, PS4 and XB1 users will be on 1.38.0.2.60360. Have a great weekend!

Comment

Hey everyone, we're aware of the reports for this and we're actively working on it now. Sorry for the disruption, we'll work to get a fix out with urgency, though I don't have a specific ETA yet.

edit: As an update for everyone we have an update that's going into certification for this issue and we will release the patch as soon as that is complete. Depending on our turn around we're hoping to have the update out on Monday at the latest, but we're trying very hard to get it out tomorrow if possible. Thanks again for your patience while we fixed this up.

edit: Details aren't final but we're targeting the update for today on both console platforms. We'll post once it's out (or if there is a delay). Thanks again for being so patient.

edit: The bug fix patch is live for all platforms now. PC players should be on 1.38.0.2.60417, PS4 and XB1 users will be on 1.38.0.2.60360. Have a great weekend!


04 Jul

Comment

Originally posted by WyomingMyst

Hey Bill, this is a long shot in the dark, but I assume this is NOT related to symptoms I have seen on the official forums and here on Reddit such as...

  • Insanely fast queue times for Competitive (like within 5 seconds) (This may be intended, but it is different than past seasons.)
  • Competitive Matches not filling up with enough players and going into "Waiting for Players" mode
  • Players attempting to cancel a Competitive queue getting penalized with leaver penalties.

I will note, I am seeing this mostly in Americas region reports obviously. I have been trying to investigate this for a couple of days now seeing if something changed since season 17 started. So if there is any information you have, it would be awesome.

The issue here was just failing hardware. This wouldn’t be related to anything like you described. I’ll pass your notes on to our server team to look into if they’re not already. Thx

Comment

Hey everyone, sorry for the hassle. There was a server in a bad state, it's cleaned up now. Cheers


26 Jun

Comment

Hey there, our compatibility team investigated this report and was unable to reproduce the issue with the same model headset you specified. Our best guess for follow up was to check your drivers and make sure they're the newest provided by the vendor.

Cheers


25 Jun

Comment

Originally posted by Apexe

Baptiste's Amp Matrix bug where healing doesn't get boosted still there, no?

We have a fix for this bug in testing and hope to roll it out in a 1.37 bug fix patch (PTR is 1.38).


24 Jun

Comment

Hey there, the bug fix patch for XB1 is going live now. We're going to wait a little bit for folks to get patched and then we'll enable Wrecking Ball again. Also we've fixed up the Moira ult audio in this build as well.

Cheers

Comment

We fully support the #savewreckingball movement. The XB1 patch is going live now, we're going to give it some time for everyone to get patched and then we'll be turning him back on.

Cheers!


22 Jun

Comment

Originally posted by fudge_sundae

Is there any word on if the Moria ultimate audio bug will be fix in this patch as well?

Yes that’s fixed in the patch on Monday as well. Cheers


21 Jun

Comment

Hey there, we have a fix headed into certification for this bug and we're targeting Monday for a bug fix release. Sorry for this one.

Comment

Hey there, we’re sorry Wrecking Ball has been MIA on XB1. We have a fix going into certification now and we’re targeting Monday to have him back.

Thanks for being so patient while we working through this one, it was a gnarly one.

Cheers

Comment

Originally posted by BillWarnecke

Hey everyone thanks for all the information in this post. We’re looking into this. Any specific details you can remember for when you hit this please continue to post them if you’re able to. It helps us a lot as we investigate.

Apologies for the disruption while we sort this out.

edit: We're disabling Wrecking Ball temporarily while we continue to investigate the issue. Thanks again for all the info in this thread.

edit2: We've found the issue and have a fix going into certification. We're targeting Monday for the patch. We're very sorry this one took so long, it was really rowdy.

Posting my edit as a reply as well for visibility.

We've found the issue and have a fix going into certification. We're targeting Monday for the patch. We're very sorry this one took so long, it was really rowdy.

Comment

Hey there, apologies for the delay getting Wrecking Ball back in the lineup. We care a great deal about all of our players, including folks on console. This has been our top priority since the bug was discovered, the experts for the systems involved in the issue dedicated 100% of their time working on a fix.

Fortunately we have a fix in testing now, we're working on getting it through certification. Right now we're expecting to release a bug fix patch on Monday.

Thanks again for being so patient, we're sorry this one was gnarly.


19 Jun

Comment

We’ve made a change to fix this issue, please let us know here if you’re still having problems. Thanks and sorry for the inconvenience.

Comment

Hey everyone thanks for all the information in this post. We’re looking into this. Any specific details you can remember for when you hit this please continue to post them if you’re able to. It helps us a lot as we investigate.

Apologies for the disruption while we sort this out.

edit: We're disabling Wrecking Ball temporarily while we continue to investigate the issue. Thanks again for all the info in this thread.

edit2: We've found the issue and have a fix going into certification. We're targeting Monday for the patch. We're very sorry this one took so long, it was really rowdy.