over 5 years ago - BillWarnecke - Direct link

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.

over 5 years ago - BillWarnecke - Direct link

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!

over 5 years ago - BillWarnecke - Direct link

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!

over 5 years ago - BillWarnecke - Direct link

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
over 5 years ago - BillWarnecke - Direct link

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!