That said it now uses D3D9 so the previously pointless D3D9 stuff now applies. Warcraft III no longer uses D3D8 hence the D3D8 related stuff now does nothing. 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. 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. 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). 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. The big question is what is different with it to be causing the problems.Ĭlick to expand.It ever worked in Windowed mode? Not even in OpenGL mode does gamma work in Windowed mode. I tried substituting back in the one used by Windows 7 (from the same folder) but the dll is incompatible with Windows 10 (WC3 throws DirectX not installed error).Īs such d3d8.dll in Windows 10 is different from Windows 7. ![]() The d3d8.dll used comes from the SysWOW64 folder (System 32 only if using 32bit Windows 10). I am not sure your d3d8.dll is safe? It is from some Russian site and claims it is a wrapper for d3d9 and it created a batch file in the WC3 installation folder. Further more WC3 behaves as intended when running d3d8.dll you provided but breaks with the d3d8.dll Windows 10 comes with. WC3 does not use d3d9.dll so you should not bundle it with. I am guessing the game is being run in some sort of pseudo Windowed Full Screen mode for resource sharing as part of the DX12 API and the new windowing frame work. It often spikes to "62 FPS" instead of anchoring at 60-59.9 FPS. ![]() It would be interesting to know why this is happening. I am also getting bad performance in game with WC3 in Windows 10 as other people have reported. ![]() Click to expand.The installer should not be able to run as it was never designed for Windows 10.
0 Comments
Leave a Reply. |