Please check the included readme file, as it's not a bug-free solution. The libraries will emulate the graphics APIs used by W:A using modern APIs. Put them all into your W:A installation directory and launch the game. Delete the wkFrontendFix.dll installed previously, and download the windowed mode libraries.If the game or frontend is too slow, proceed to the next step. The frontend's white fields should be fixed, however it does not affect in-game or frontend performance. Download this WormKit module and extract it to the W:A installation directory.A working WormKit setup will be required for the following steps. If you haven't yet, install WormKit or WormKitDS at your choice.Note that you won't be able to maximize properly in-game on 3.6.31.0, so you may want to use the 2nd method if this bugs you. If you're running W:A 3.6.31.0, navigate to the folder in which you installed W:A, open the "Tweaks" directory and import SlowFrontendWorkaround_Off.reg.Locate the file using Explorer, and double-click it.Enter FixWA.reg in the File name field, and save the file.In the Save as type drop-down, select All files.Click File → Save to open the save dialog.Remember to use double backslashes instead of single ones. If you installed W:A in a location different from C:\Team17\Worms Armageddon\, correct the path on the last line."C:\\Team17\\Worms Armageddon\\WA.exe"="$ DWM8And16BitMitigation Layer_ForceDirectDrawEmulation" ![]() Open Notepad, and copy and paste the following:. ![]() There are currently some known methods which should address the issue. 8-bit and 16-bit screen resolutions are emulated in software, and the DirectDraw used in Windows 8 results in unusual behaviour or poor performance in certain older games, including Worms Armageddon. Windows 8 no longer supports screen resolutions with colour depths other than "true colour" (24-bit depth or 16,777,216 colours). It worked on Windows 7! Why doesn't it work properly on Windows 8?
0 Comments
Leave a Reply. |