OWMatt-1513

OWMatt-1513



05 Sep

Comment

Hello again! Go to Nvidia’s website, click “Drivers” in the menu bar. Click the “GeForce Experience” link. Click “Download Now”. Once it downloads, install it.

-matt

Comment

Hello! Please update to the latest GeForce Experience application, we believe that will resolve this issue.

-matt

Comment

Hello everyone, it would help us a lot if you could post your dxdiag info in thread. Also, please if one of you could take a screenshot of the error message you’re seeing, that would help us as well.

-Matt


30 Jul

Comment

Hello again everyone. Thanks so much for your help. If you haven’t already, let your battlenet update the Overwatch 2 client to 2.11.1.1.128150.

Comment

Hi again - Thanks for posting your dxdiag’s. Keep them coming! Please, if you could include the full dxdiag file, it will help us to better identify what is going on here.

Comment

Hello, Sorry you are experiencing those issues. Please could you share some details about your system? A dxdiag would be ideal.

Thanks!


24 Jul

Comment

Hello,
If you could, please make sure you’ve updated to the latest OW2 client build in Steam (released today 7/24), which is 2.11.1.1.128150. After you’ve updated, please let me know if you’re still experiencing this issue.
-matt


31 May

Comment

Hello! This is a new file that ships with Overwatch and is intended to be installed.


30 May

Comment

Hello, we just now released a pc client update that should resolve this issue for you. Please make sure you’ve patched to build 125747, give it another shot and let us know if you still see this happening.

Comment

Hi all, this fix was published with today’s client patch. Sorry for the inconvenience.


21 May

Comment

Sorry folks - I was referring to our next client update patch, which is a lot different than today’s hotfix balance update. Expect it to land later next week, but no guarantee on that timing.


17 May

Comment

Hello again. We have a fix for this in our next patch release.


14 May

Comment

Hello! Thanks for this report. We are looking into options for resolving this ASAP.

-matt


03 May

Comment

This should be resolved now, please give it a try! Sorry about that.