doesn’t matter war3champions has it’s own rust based launcher, their multiplayer works by creating a custom game on their flowbot servers scattered all over the world. Best ping server is selected, MMR is matched and matching making proceeds.
If we find a fix for the BlizzardBrowser problem the whole thing might work. And for example if you run the BlizzardBrowser in Vista comp mode it ALMOST works. I found some threads stating that BlizzardBrowser under certain circumstances (our case) doesn’t use the dedicated GPU which might cause the UI to fail. For NVIDIA (or older AMD drivers) it might work to fix it by forcing it to use the GPU
I might try that later
At least we generated enough views here so that obviously some employee took notice if it wasn’t some kind of autodelete so mb it’s not a complete timewaste
ahhaah so true… you did great work! Is win10 an option? perhaps that could work for you and the rest of the community ?
1 Like
I have no idea. All i have seen is that some win10 users reported the same behaviour that we get on win7 with the dxvk files (black screen + failure to load UI) and some were able to fix it…
Edit: i spent enough time today for this… but next time i will try to use an older AMD driver software to force BB.exe to use the gpu
I did some tests. Using -graphicsapi Direct3D9, I can join multiplayer custom games (but the graphics are problematic). Therefore, I understand that windows 7 possibly does not have a server access problem.
I wonder how did the client work on W7 before patch 2.0 if game menu is using chromium web app which no longer supports W7. I’m using Supermium browser which is a fork of Chromium for this exact reason.
I guess this is a more technical question for the developers but it just makes no damn sense.
3 Likes
Because it’s chromium version 83.0.4103.106 (released 2020) maybe
Anyways, the BlizzardBrowser-logs are full of errors (mostly gpu related but some could also be outdated root certificates etc.) with version 2.0 regardless of graphicsapi/dll’s etc. Not too unlikely that the game or at least the BlizzardBrowser.exe now relies on too many services which aren’t supported anymore for win 7 → gg for win 7 users
1 Like
You forget that many people with Windows 10 also have the problem. Some have even tested Windows 10 specifically in this thread.
Warcraft 3 works on my main PC with Windows 11. On my notebook with Windows 10 I get exactly the error described here.
5 Likes
Forgive my tardiness, I couldn’t reply earlier because I was silenced for daring an infraction!
Reporting back, got my hands on a win7 machine with an intel HD3000 integrated gfx, and a Radeon 6770m. However discrete GPU is possibly dead keeps BSOD. Anyway switched to Intel HD 3000.
Running war3 through battlenet on default results in blizzard error
Next tried all iterations with command line arguments and with alternate dlls ( v1.10.3)
Error “Unable to initialize graphics. Please ensure your operating system and display drivers are up to date.”
Common Problems
* Cannot start Warcraft III on MacOS
- Error “Unable to initialize graphics. Please ensure your operating system and display drivers are up to date.”
PC:
The error indicates that your computer does not meet the minimum system requirements to play Warcraft III or the Operating System and Graphical Drives need to be updated. Since patch 1.31 in May 2019, Warcraft III requires a 64 bit operative system.
MAC:
This error indicates that your Mac computer does not meet the minimum system requirements to play Warcraft III. Since patch 1.31 in May 2019, Warcraft III requires a 64 bit operative system and Metal graphic API.
Meaning, all GPUs lacking support for Dx12 are being deprecated as of W3R 2.0
4 Likes
Hi Tenrai. Small note. I am running windows 7 64 bit and warcraft does not work. So, its probably not the process data the source of the problem. (I can run Warcraft 3 on a more recent PC with windows 11)
I wonder if 2.0 only supports DirectX 12. On World of Warcraft, they created a patch to make DirectX 12 run on windows 7.
3 Likes
Hi Tenrai, i wrote you some of my findings on the bnet app
what’s the GPU on your newer PC ?
intel uhd 620. its a laptop
1 Like
I have GTX 1070 and GeForce 10 series supports DX12 unless they updated API to DX12 Ultimate, is there any way to verify this? I think this being GPU related is unlikely since it would throw out a DirectX related error.
I asked friend of mine to launch the game with default settings / no launch commands with MSI Afterburner on his Windows 11 machine and it reports in OSD that API is D3D11. If they indeed updated API to DX12 then OSD would correctly show other version.
If somehow game is now really running on DX12 despite the above then Blizzard would need to add compatibility layer for Windows 7 introduced by Microsoft few years ago which emulates DX12 on W7 and supports older GPUs that don’t have it natively e.g. Nvidia Kepler series albeit with some missing DX12 features, like FrozenSkull mentioned they seem to have done exactly this for WoW.
Edit: Here’s a screenshot (https://i.imgur.com/UAkAYLs.png) of game running under DX11 on Windows 11 so it’s definitely not GPU related and any card from last 15 or so years shouldn’t have any issue unless this OSD data is somehow incorrect.
3 Likes
Thank you for reporting back, nothing is official yet so we don’t really know what’s Blizzard’s stance on Win7 with legacy hardware. Minimum requirement includes GTS 450 and that supports Dx12. Yes, like you and others have suggested, they could do a dx12 to dx11 translation layer for win7 like they did for WoW.
So far however, Win7 machines have been unable to run w3R at least with the hardware we have tried it on. Me and Samuro tested various .dlls. I tried running war3R on a WIn7 machine with HD3000 gfx card it is compatible with Dx11 however running w3R results in blizzard’s default error “application has encountered an unexpected error”
I am adamant this is a GPU related setback, because I tried running w3R on win7 machine with intel HD 3000 error logs show GPU isn’t being initialized. D3D10 api is being used. If instead I tried forcing dxvk-1.10.3 D3D11 dlls it results in “unable to initialize graphics” confirming my doubts.
If MSI on screen display isn’t showing Dx12 and if they are indeed still using dx11 api then there has to another common denominator we’re missing. It could be chromium based blizzard browser, failing to initialize the GPU.
Samuro managed to run a custom game through commanline arguments on his windows 7 machine. However, UI was glitchy because of blizzard browser running chromium. Game ran fine, with normal FPS
2 Likes
Your integrated gpu runs DX10 natively but has so called “feature level 11” for DX11 so it doesn’t fully support it and game is most likely using some component that isn’t available for your card hence why I mentioned Nvidia Kepler series just for comparison, it supports DX12 but only on this feature level. In fact I have GTX 660 at hand and I can give a test just to clear any doubts, client will just crash to common error we’re all seeing nothing gpu related.
About Web UI part, like Samuro confirmed the game does work on W7 so I still think it’s something about Chromium, like I mentioned few posts above old Reforged worked fine so the only thing I can think of is that they simply updated Chromium version to one that no longer supports W7. I don’t know which version this is but on Chrome last W7 version was 109.
1 Like