I’m pretty sure i found a fix or at least a workaround. I’m logged into multiplayer right now, the UI generation completes without -graphicsapi Direct3D9, the game itself renders normally, the mouse pointer is visible and no glitches or artifacts.
4 Likes
Can you show us how? Also, very important, the Editor works with your new workaround?
I’m not sure yet what i can do with this… but i’m pretty confident now, that it’s very possible to find a config that works pretty well for online play
Edit: Especially because of what i said, that the only goal seems to be to get through the UI because the game itself is unaffected
1 Like
Sure if you can test GTX 660 with and without -graphicsapi Direct3D9 arugment perhaps we shall find a common denominator. The more permutations we have the better, Samuro found a way to by pass chromium based UI generation. However, this should only work on machines that can at least launch W3R with -graphicsapi Direct3D9
Unlike this Win7 machine I am testing, -graphicsapi Direct3D9 results in “unable to initialize graphics” error. It’s the same with DXVK d3d11.dll
I even tried installing supermium (Version 126.0.6478.256), a fork of chromium. Still the same. This has happened time and time again, every time there is a new patch there is a score of users that get culled off. Apparently UI (blizzard browser) is some how interfering with GPU initialization.
Feomatar reported WR3 didn’t work with a gts 250 on win10. He then upgraded to a 5700xt on win10 and game runs fine.
3 Likes
may i ask for the workaround?
(i follow this thread for week now and have the “no mouse pointer / graphic glitches” stuff when i start with -graphicsapi Direct3D9)
4 Likes
Just wanted to let you know, unfortunately I won’t be able to test and post results until end of the week due to work so Friday is earliest I can do.
3 Likes
No worries, happy Thanksgiving!
1 Like
So how to make it work?
3 Likes
Do you have some Updates?
This is still very much a live issue. Can any Dev give a real response? unlike the copy-pasted garbage that was disrespectfully thrown at us a few weeks ago? Can someone at least say definitively either:
- We acknowledge this issue, and are working to resolve it.
or - We intentionally changed V 2.0 to not be compatible with Windows 7, too bad for all Win7 users.
We just want an answer that’s more than a 10-second copy paste from you Blizz.
4 Likes
it’s not just win7, it’s legacy hardware as well…
I haven’t been watching the Win7 issue since the Macs were able to play again.
So, what is the current Win7 issue? Doesn’t launch? Can’t log in? Bad FPS? Crashes? Error popups?
Has it changed from one issue to another over time? Or has it been the same issue the whole time?
Does not launch.
What does it do when trying to launch? Any error messages?
After clicking Play, I get the following error: The application encountered an unexpected error
I don’t know how to interpret the crash file or War3Log. Let me know if that would help.
(game opens with -graphicsapi Direct3D9 but the cursor is invisible and there are many graphical bugs. I can join a multiplayer game so its probably not a server access problem)
I’m just curious on how it unfolds. I’m putting something together to give Bliz about it.
They likely know, but I can at least prod them a little.
1 Like
-graphicsapi Direct3D9 only takes me to the lion gate screen. Game remains frozen there and doesn’t even start.
still doesn’t work on windows 7?
I’ve updated the PTR and it works well on Windows 7. I hope to see this new patch go live soon.
2 Likes
Yeah, looks like their hoping to fiz the Win 7 issue with this patch.
1 Like