Hey there, we have more information about this problem in this thread.
Hey there, we have more information about this problem in this thread.
Hey folks, we’ve addressed this issue on live and we’re working to release a patch to fix the problem. Apologies for the hassle, we very much appreciate the info from you that helped us track down the problem.
Closing this thread, further discussion can take place in the live version of this thread which is here.
Hey Naru, feel free to use this workaround until we patch if you’d like. I’m just trying to give words of caution so others who wouldn’t benefit from this don’t add it in!
For everyone else, thanks for helping us verify. This was difficult for us to reproduce internally because it’s a bug as a result of a certain type of hardware which we don’t actively support or test with.
We’re working on a permanent fix for this, we hope to roll it out tomorrow! Further updates will be here if needed. Thanks everyone!
...Hey there as a workaround if someone who is affected by this issue can add an additional command line argument to their Overwatch startup we want to see if this fixes the issue for you.
Note this is an advanced startup line, you’ll want to clear this line after testing. Changing startup options can lead to odd problems.
To set the command line, in the Blizzard Desktop client with Overwatch selected, choose Options > Game Settings. Find the Overwatch entry in the list, click the Additional command line arguments checkbox. In the textbox there add:
--tank_WorkerThreadCount 1
The file is probably too big to attach to the forums or email directly. Any place you can place it so we’re able to download it will work though.
Emailing the link to [email protected] is the best route to get it over to us instead of posting it here.
Thanks!
Hey there, we’re still investigating this issue internally. A dump of the Overwatch client when it’s in this “stuck” state would be helpful for us to do further investigation.
For anyone who has this specific issue and is comfortable with creating a process dump (Task Manager > Right Click Overwatch > Create Dump File) and can upload it to a location where we’re able to download it (drop box, one drive), this would be extremely helpful for us.
edit: Emailing the link to [email protected] is the best route to get it over to us instead of posting it here.
Thanks!
Hello there!
Are you using an AMD graphics card? If so, could you make sure your drivers are updated, or if that’s not possible, try setting “Refraction Quality” to “Low” in the graphics settings and see if that resolves the issue for you?
Thanks!
Bruce
We do have one shield bash change we are playtesting right now, which is likely to hit the next PTR: Shield Bash no longer going through barriers.
This means it is a lot more tricky to land a clutch stun on an enemy Reinhardt, for example, but you can still use the ability to close distance and land melee hits to trigger Inspire.
Hey there, we’re investigating this. As much detail as you’re able to provide (hardware specs, etc) may help us more quickly identify the problem. Thanks for your patience.
Ana
Brigitte
Doomfist
Hanzo
Junkrat
General
General
Deploy Turret
Torb-Bot
Disclaimer: This is not a complete list of all currently tracked issues affecting this build of Overwatch, rather this is a targeted list of some known specific issues with this release.
General
The Viper
Coach Gun
...
Read moreWe also initiated a background download (aka prepatch) for this 1.30 update late last week. This prepatch allowed for a smaller update today.
Cheers!
Hey there, the patch notes should be live shortly (if not already)! Cheers.
I’m locking this topic as it breaches the Code of Conduct and Forum Guidelines. Users who create topics with the intent to harass their fellow community members will find their accounts suspended.
Thank you.
Thanks for helping us test Ashe & B.O.B.! We are now concluding the 1.30 Public Test. The Public Test Region will not be accessible until we update with new content. You can continue to provide additional feedback and bug reports here if needed. Thank you for … doing something.
The problem we encountered was with the in-game Master Volume sound setting. If you turned down your master volume lower than 100, it would throw off the balance of the audio. 2d sounds would be quiet and 3d sounds would be loud.
We have now turned off the Windows Spatial Audio for this patch. We really appreciate the help testing, and we hope to bring it back to PTR at a later date.
Thanks everyone!