Warcraft 3 лагает windows 10

Do note there is a small chance this will flag up in Warden and could get you banned. Even though they are genuine signed Microsoft DLLs they are in the wrong location. Additionally there might be other side effects to other running applications due to possible resource conflicts.

d3d9.dll should not be used as WC3 is only D3D8? I doubt it even knows to link to it.

Also I do not see how this should improve performance since those are nothing but wrappers for driver framework. Chances are only specific features have been disabled (eg gamma) due to them conflicting with newer features (calibration).

Damn I am having another (minor) issue with my WE at the moment, sadly not what you described. Got my hopes up for nothing. Useful tutorial though.

Do note there is a small chance this will flag up in Warden and could get you banned. Even though they are genuine signed Microsoft DLLs they are in the wrong location. Additionally there might be other side effects to other running applications.

d3d9.dll should not be used as WC3 is only D3D8?

Also I do not see how this should improve performance since those are nothing but wrappers for driver framework.

You can’t get banned by this, not possible. Since these .dll are also used in Bloom and HDR which I used many times in genuine Battle.Net.

There may be more issues with how Direct X handles Warcraft 3, we may not be aware of the others. Gamma was noticeable while performance related issues could not be so easily noticeable.

Damn I am having another (minor) issue with my WE at the moment, sadly not what you described. Got my hopes up for nothing. Useful tutorial though.

can you please describe your problem? I will be adding all solutions to this thread. Usually running a program as administrator or in compatibility mode (Win7, Vista) fixes the problem. Windows 10 is notorious for having screwed up administrator privileges to TrustedInstaller.

DirectX does not directly deal with anything performance related. It acts as a wrapper for drivers. Direct3D calls translate into graphic driver calls. These are usually handled by the NVidia, AMD or Intel graphic drivers which interact with the hardware.

The performance gains by using Direct3D 12 come from a more efficient interface to the graphic hardware rather than Direct3D 12 doing anything magical.

Nice idea to have this thread. If I find any solutions to weird Win10 glitches with wc3, I’ll let you know.

Approved for now. If anyone has any problems/solutions to share, feel free to contribute!

Can you guys test a thing for me?

In TFT, load up the night elf campaign and play the first cinematic.
Does it play at all or does it move you back to the campaign menu again?

It did play in Windows 7, but as of Windows 10 it seems to have stopped working.

Can you guys test a thing for me?

In TFT, load up the night elf campaign and play the first cinematic.
Does it play at all or does it move you back to the campaign menu again?

It did play in Windows 7, but as of Windows 10 it seems to have stopped working.

Weird. For me it’s just a black screen. I’ll try to find a solution, stay tuned.

Black screen is solved by installing codecs it seems.
http://us.battle.net/en/forum/topic/12203110379

But mine doesn’t even play, it just returns me to the campaign screen.

Do you have a file called «Blizzard.ax» in Warcraft 3 installation folder? Mine was missing for some reason. Now it’s working for me.

Edit: You should always run War3 as administrator.

Not working for me, after copy there dll file, i can’t open the game:

Картинка с сайта: www.hiveworkshop.com

But working in my friend laptop. I don’t know why

can you please describe your problem? I will be adding all solutions to this thread. Usually running a program as administrator or in compatibility mode (Win7, Vista) fixes the problem. Windows 10 is notorious for having screwed up administrator privileges to TrustedInstaller.

The editor generally loading very slowly. For example when you want to specify which effect you want to spawn at a location with triggers. It takes forever before the list loads and you can start browsing. Same goes when changing a unit’s model it takes a lot of time before the list shows up.

Also sometimes I can’t scroll. If I got, let’s say 5 variable and try to scroll down to the one at the bottom, it simply wont work.

The editor generally loading very slowly. For example when you want to specify which effect you want to spawn at a location with triggers. It takes forever before the list loads and you can start browsing. Same goes when changing a unit’s model it takes a lot of time before the list shows up.

Also sometimes I can’t scroll. If I got, let’s say 5 variable and try to scroll down to the one at the bottom, it simply wont work.

Here is a nice tutorial.

Not working for me, after copy there dll file, i can’t open the game:

It may be that you are already running Warcraft 3, try going to task manager and checking if there is a process called War3.exe and close it. The next solution would be two install this. Finally if it still isn’t working, try reinstalling and patching the game using the latest patch.

It is also recommended to contact Blizzard support.

Already done that a long time ago.

It takes forever before the list loads and you can start browsing. Same goes when changing a unit’s model it takes a lot of time before the list shows up.

Check your disk I/O load. That hints of something happening in the background using up disk I/O bandwidth (eg peer to peer update/upgrade sharing).

Here is a nice tutorial.

It may be that you are already running Warcraft 3, try going to task manager and checking if there is a process called War3.exe and close it. The next solution would be two install this. Finally if it still isn’t working, try reinstalling and patching the game using the latest patch.

It is also recommended to contact Blizzard support.

install directx9 and it working for me, thank you very much

Check your disk I/O load. That hints of something happening in the background using up disk I/O bandwidth (eg peer to peer update/upgrade sharing).

Funny thing, wc3 including JNGP is on my SSD so speed should actually be.. well..

I do not know how to track such though. I did some quick googling which lead me to something called «Prestandaövervakaren» in Swedish. Which I’d roughly translate into «Performance Monitor» which I started by pressing Start + R and type «%SystemRoot%\system32\perfmon.msc /s»

edit: Okay I made the program track «Drive — Read Byte/s«, «Drive — Written Byte/s» and «Drive Byte/s«

As you see there are some odd spikes but it did not seem to spike when creating said scenarios in the editor. It spikes either way.

Картинка с сайта: www.hiveworkshop.com

install directx9 and it working for me, thank you very much

Bad idea. Windows 10 needs DirectX 12 which is installed automatically, anything else might corrupt the kernel.

DirectX 12 is backwards compatible with Direct3D 9 and earlier, although how well drivers implement it is another question as the old APIs are now 2 generations deprecated.

Funny thing, wc3 including JNGP is on my SSD so speed should actually be.. well..

In which case disc I/O is clearly not a problem. Unless of course the OS is installed on a mechanical drive in which case it could be dlls loading slowly.

Another possible cause is the new windows manager Windows 10 uses. This might cause some older applications to become more unresponsive or run slower because of how they were implemented. For example alt+tab in Windows 10 is much faster from full screen to windowed mode but it introduces compatibility bugs such as colour calibration not swapping properly in older applications.

Bad idea. Windows 10 needs DirectX 12 which is installed automatically, anything else might corrupt the kernel.

It does not remove DirectX 12, I checked it myself using DirectX Diagnostic Tool.

I’m having the same issue in Wc3..
Espacially when alot of units are coming together and if alot of players have more items, talking about dota..

this pretty much sucks, since my old laptop did its job at 60 fps..

@DrSuperGood..

Did you look into te problem yet?
I have been searching about this issue, with no avail sadly…

I could not find any documented Windows 10 changes to legacy Direct3D support. I am guessing it has something to do with DirectX 8 being old and DirectX 12 being very different from DirectX 11.

The only real solution currently is to use the «-opengl» command line option as OpenGL does not appear to be affected by this.

I could not find any documented Windows 10 changes to legacy Direct3D support. I am guessing it has something to do with DirectX 8 being old and DirectX 12 being very different from DirectX 11.

The only real solution currently is to use the «-opengl» command line option as OpenGL does not appear to be affected by this.

So i have to start the game up with this thicked on?

Картинка с сайта: www.hiveworkshop.com

So i have to start the game up with this thicked on?

No?! You simply change…

«C:\Program Files (x86)\Warcraft III\Frozen Throne.exe»

to…

«C:\Program Files (x86)\Warcraft III\Frozen Throne.exe» -opengl

With the WC3 launcher shortcut.

For example on desktop…

1. Right click «Frozen Throne» shortcut.
2. Select (press) «Properties».
3. Select the field «Target:».
4. Change it from «…» to «…» -opengl where «…» is a path to the installed version of Warcraft III. An example of such a path was provided earlier in this post (for English UK 64bit Windows).

No?! You simply change…

to…

With the WC3 launcher shortcut.

For example on desktop…

1. Right click «Frozen Throne» shortcut.
2. Select (press) «Properties».
3. Select the field «Target:».
4. Change it from «…» to «…» -opengl where «…» is a path to the installed version of Warcraft III. An example of such a path was provided earlier in this post (for English UK 64bit Windows).

Tried this, but the same is happening.

Ohwell.

Tried this, but the same is happening.

Works fine for me… Maybe you are not doing it right as you appear to be using a hacked version of WC3 started by a third party launcher.

Works fine for me… Maybe you are not doing it right as you appear to be using a hacked version of WC3 started by a third party launcher.

Its not a hacked version.

I bought the golden edition on G2A.
Why do i use a third party program you might think…
Well, for dota stats and GPROXY in order to reconnect to the game..

Картинка с сайта: www.hiveworkshop.com

As long as you start the game with that shortcut it should work, I just re-tested and Gamma as well as frame rate works normally on Windows 10 when starting WC3 with that shortcut.

As long as you start the game with that shortcut it should work, I just re-tested and Gamma as well as frame rate works normally on Windows 10 when starting WC3 with that shortcut.

Good day sir, I have tried the openlgl and it works but my problem is I play WC3 using GARENA or RGC and I tried to run the game but it seems the opengl was lost or not working, the gamma was set back again to default when using these apps but when I just run the game from the shortcut itself it works with no problem, any idea to this issue?

Good day sir, I have tried the openlgl and it works but my problem is I play WC3 using GARENA or RGC and I tried to run the game but it seems the opengl was lost or not working, the gamma was set back again to default when using these apps but when I just run the game from the shortcut itself it works with no problem, any idea to this issue?

I recommend contacting the maintainers of those third party programs. I only use BattleNet.

What must be happening is when they start the game they are not using the -opengl flag. I would imagine their program allows you to toggle that flag on or off before starting the game through their program or at least allows you to specify command line flags to send to the game when starting.

I recommend contacting the maintainers of those third party programs. I only use BattleNet.

What must be happening is when they start the game they are not using the -opengl flag. I would imagine their program allows you to toggle that flag on or off before starting the game through their program or at least allows you to specify command line flags to send to the game when starting.

Thank you for maintaining this thread, lately my activity has diminished.

I see..thanks for the advice, I kinda thought that may have been the case.. too bad the dll also didnt work for me because it seems RGC doesnt allow any modification to the wc3 folder, it automatically deletes it when I hit the start WC3 button. guess I’m stuck with this for now

I see..thanks for the advice, I kinda thought that may have been the case.. too bad the dll also didnt work for me because it seems RGC doesnt allow any modification to the wc3 folder, it automatically deletes it when I hit the start WC3 button. guess I’m stuck with this for now

Move the .dll and in the properties select «Read Only». It will prevent it from being deleted by other programs.

Move the .dll and in the properties select «Read Only». It will prevent it from being deleted by other programs.

just tried this out and I get this error msg when starting wc3, also tried to set it at hidden but same thing..

[ERROR] Failed to clean up: C:\Program Files (x86)\Warcraft III\ :: d3d8.dll
[ERROR] Your game directory contains modifications and RGC was unable to remove them. Your game cannot be started.

damn no luck at all thanks for the tip though

Thank you for this tutorial, Void! When I upgraded to Windows 10, I got a noticable FPS drop when playing WC3. However, after installing the .dll files you provided, it has returned to normal

I still would recommend OpenGL mode instead of some third party work around.

the dll methods worked for me !! I just copy the 2 dll into w3 folders, restarted with the installer, 1 min and it worked ! thanks so much ^

Re: Running WC3 on Windows 10

I have a new computer with windows 10 and have installed and played Warcraft 3 with no problem at all. Only thing I do is run as admin and no gamma or graphics problems nor any lag related so might be an issue with your graphics on your computer or something else. I believe I am even using Direct X 12 currently and have experienced zero problems…

I have a new computer with windows 10 and have installed and played Warcraft 3 with no problem at all. Only thing I do is run as admin and no gamma or graphics problems nor any lag related so might be an issue with your graphics on your computer or something else. I believe I am even using Direct X 12 currently and have experienced zero problems…

The only problem is that Gamma cannot be set in Direct3D mode, moving the slider does nothing. There are no other problems and gamma may never need to be set if you are happy with its current setting. There is even no need to run the game in compatibility mode or as an administrator and I would advise against doing that for security reasons.

I’m getting this error.

I have 20 gb of hard drive space left, and if I uninstall and re-install it works fine again.

I’m getting this error.

I have 20 gb of hard drive space left, and if I uninstall and re-install it works fine again.

See if it works if you run it as admin.

See if it works if you run it as admin.

Thanks, seems to have worked.

I swear i tried that.

Running in administrator in the long run is asking for problems. One malicious map with an undisclosed exploit and your computer could be toast.

Zhall I am guessing your install folder does not have write permission with your user account. You should be able to fix this like all permission problems by finding the folder, right clicking, going to properties and then modifying permissions in there. You need to make sure your user account has full control over the Warcraft III folder and all sub folders and files.

Well I believe the only reason I run in admin or have to is that it is in my progam files (x86) folder. Im sure that placing it somewhere else will work better.

Well I believe the only reason I run in admin or have to is that it is in my progam files (x86) folder. Im sure that placing it somewhere else will work better.

Mine is also in that folder. So that is not a problem. Once again, you just need to make sure that single folder (Warcraft III) has full control permission for your user account.

This is now obsolete with the release of todays patch. Warcraft III no longer needs to be run in OpenGL mode or use some hacky DLL.

I would advise people remove the DLL. There is a good chance it could trigger anti-hack detection in Warcraft III as it causes a dependency to not match a signed system dll like it expects.

A reasonably correct gamma setting is 2.2 (setting 44?). Gamma is not brightness/darkness as the option hints but rather color correction since darkest and brightest colors are not affected by gamma.

This is now obsolete with the release of todays patch. Warcraft III no longer needs to be run in OpenGL mode or use some hacky DLL.

I would advise people remove the DLL. There is a good chance it could trigger anti-hack detection in Warcraft III as it causes a dependency to not match a signed system dll like it expects.

A reasonably correct gamma setting is 2.2 (setting 44?). Gamma is not brightness/darkness as the option hints but rather color correction since darkest and brightest colors are not affected by gamma.

You failed to mention that gamma is not fixed in windows mode. Besides, this thread is about giving support for Windows 10 not about gamma alone.

I will still be using this solution, because Blizzard’s one is still crap compared to this.

You failed to mention that gamma is not fixed in windows mode.

It ever worked in Windowed mode? Not even in OpenGL mode does gamma work in Windowed mode.

The reason for this is that the gamma is applied by the GPU to display output in a separate color profile stage completely unrelated to how the display image was composed. If running in windowed mode the game is forced to use the desktop color profile, which by default assumes the pixel values are sRGB so does not perform any correction (stuck at gamma 1.0). If the option did work it would raise the gamma of the entire desktop and break any loaded color profiles which is something worse than just not working.

The fix requires a programmable pixel shader be used to add a gamma correction stage to the composed images independent of the display color profile.

EDIT:
Warcraft III no longer uses D3D8 hence the D3D8 related stuff now does nothing. That said it now uses D3D9 so the previously pointless D3D9 stuff now applies. As far as I am aware the D3D9 implementation of Windows 10 is not buggy in the way the D3D8 one is so I am not sure if there is a reason to do this anymore.