Difference between revisions of "Getting W:A to work on Windows 8"

From Worms Knowledge Base

Jump to: navigation, search
(creation)
 
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{ParentArticle|[[Troubleshooting FAQ]]}}
 
{{ParentArticle|[[Troubleshooting FAQ]]}}
  
If you're on this page, it means that you're running Windows 8 and trying to make the [[Beta_updates_(Worms_Armageddon)|W:A {{LatestBeta}}]] to work.
+
{{Languages|en|Getting_W:A_to_work_on_Windows_8|ru|Исправление совместимости W:A с Windows 8}}
  
== It worked on Windows 7! Why doesn't it work properly on Windows 8? ==
+
This page describes getting [[Beta_updates_(Worms_Armageddon)|W:A 3.6.31.0]] working on Windows 8.
Well, the Microsoft is to blame. In Windows 8, they have implemented an emulation of the 8-bit (256-colour) and 16-bit applications in a 32-bit window, most likely to prevent any of the colour issues. As a result, some games which were made a long time ago without knowing about Windows 8, can behave unusually inside that 32-bit window. WA is an example.
+
  
== Methods to solve ==
+
For 3.7.0.0 and higher, a simple solution is to either enable '''Direct3D 9''' from the Advanced Settings screen as the graphics renderer or to set a compatibility flag for DirectDraw (not recommended).
We need to know how deep does the problem touch you. It may be possible that graphic drivers could get an update to better support the aforementioned technology, but for now it's all how we see it.
+
 
 +
== It worked on Windows 7! Why doesn't it work properly on Windows 8? ==
 +
Windows 8 no longer supports screen resolutions with colour depths other than "true colour" (24-bit depth or 16,777,216 colours). 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.
  
#If you haven't yet, install [[WormKit]] or [[WormKitDS]] at your choice. This will be needed for the further steps.
+
== Solution ==
#Download [https://dl.dropbox.com/u/48532592/wa/wk/wkFrontendFix.rar this] WormKit module and extract it to your W:A folder. The frontend's white fields should be fixed, but nothing is done to the in-game, and nothing is done to the speed of frontend. If you see that the game is lagging so much that it's unplayable, proceed to the next step.
+
There are currently some known methods which should address the issue.
#Delete the ''wkFrontendFix.dll'' installed previously, and download the [https://dl.dropbox.com/u/48532592/wa/wk/windowmode.rar windowed mode] libraries. Put them all into your W:A folder, and launch the game. This windowed mode adds its own rendering to replace the one used by Windows 8 to improve performance. Please consult the readme, as it's not bug-free! If everything in-game is fine for you, you may stop here. Otherwise, proceed to the next step.
+
#Download and install [http://px.worms2d.info Project X]. Follow the instructions on the site. Assuming you have an average modern PC, there should be no problems during the game for you (the system requirements in Project X are higher than the default ones). [[Project X]] adds DirectX-9 rendering during the game, which completely bypasses all the crappy methodics of Windows 8. Combined with the windowed mode mentioned above, it gives the best effect.
+
  
For now these are the only methods known to resolve the performance and frontend issues on Windows 8, except [[Emulating_Worms_Armageddon|emulating W:A]]. If you have anything to add, feel free to discuss on the [[Talk:Getting_W:A_to_work_on_Windows_8|talk page]].
+
=== Method 1 ===
 +
* Open Notepad, and copy and paste the following:
 +
Windows Registry Editor Version 5.00
 +
 +
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
 +
"C:\\Team17\\Worms Armageddon\\WA.exe"="$ DWM8And16BitMitigation Layer_ForceDirectDrawEmulation"
 +
* If you installed W:A in a location different from <tt>C:\Team17\Worms Armageddon\</tt>, correct the path on the last line. Remember to use double backslashes instead of single ones.
 +
* Click '''File''' &rarr; '''Save''' to open the save dialog.
 +
* In the '''Save as type''' drop-down, select '''All files'''.
 +
* Enter '''FixWA.reg''' in the '''File name''' field, and save the file.
 +
* Locate the file using Explorer, and double-click it. Confirm Registry Editor's warning.
 +
* 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'''. 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.
  
== I can't start the game! An error "Unable to set desired video mode" pops up! ==
+
=== Method 2 ===
This is because your Windows 8 failed to install some compatibility manifests (during installation?), so you will have to set them up yourself.
+
#If you haven't yet, install [[WormKit]] or [[WormKitDS]] at your choice. A working WormKit setup will be required for the following steps.
 +
#Download [http://myfiles.my1.ru/wa/wk/wkFrontendFix.rar this] WormKit module and extract it to the W:A installation directory. The frontend's white fields should be fixed, however it does not affect in-game or frontend performance. If the game or frontend is too slow, proceed to the next step.
 +
#Delete the ''wkFrontendFix.dll'' installed previously, and download the [http://myfiles.my1.ru/wa/wk/windowmode.rar windowed mode] libraries. Put them all into your W:A installation directory and launch the game. The libraries will emulate the graphics APIs used by W:A using modern APIs. Please check the included readme file, as it's not a bug-free solution. If everything in-game is fine for you, you may stop here. Otherwise, proceed to the next step.
 +
#'''Only for W:A 3.6.31.0:''' Download and install [http://px.worms2d.info Project X]. Follow the instructions on the site. Assuming you have an average modern PC, there should be no problems during the game for you (the system requirements in Project X are higher than the default ones). [[Project X]] replaces W:A's in-game graphics code with a modern (DirectX 9) true color graphics API, which does not interfere with Windows 8's compatibility layers. Combined with the windowed mode libraries mentioned above, it should result in the best performance.
  
Make a .reg file with the content below. This can be done by unhiding the file extensions in the "Folder Properties" settings, and then creating a text file, renaming its extension to .reg.
 
  
<table class="toccolours"><tr><td style="font-size: 140%; font-family: monospace;">Windows Registry Editor Version 5.00<br/>
+
For the moment, these are the known methods which resolve performance and frontend issues on Windows 8, except [[Emulating_Worms_Armageddon|emulating W:A]]. If you have anything to add, feel free to discuss on the [[Talk:Getting_W:A_to_work_on_Windows_8|talk page]].
<br/>
+
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]<br/>
+
"C:\\Team17\\Worms Armageddon\\WA.exe"="$ DWM8And16BitMitigation"<br/>
+
</td></tr></table>
+
  
Where the default path is C:\Team17\Worms Armageddon\WA.exe.
+
== The error "Unable to set desired video mode" pops up when attempting to start the game ==
 +
For some reason, Windows 8 identified W:A as an application targeting Windows 8, which forbids using non-24-bit screen modes.
  
If you want to specify another path, replace the words accordingly. Note that there have to be two slashes instead of one, since we edit the registry by text. This is for both 32-bit and 64-bit systems.
+
See the [[Getting_W:A_to_work_on_Windows_8#Method_1|fix method #1]] to correct the problem.
  
Note: if your [[Troubleshooting_FAQ#.22Graphics_subsystem_error_-_Unable_to_set_desired_video_mode.22|system]] doesn't support the 640x480 resolution, this method may not help.
+
Note: if your system doesn't support the 640x480 resolution, you will need windowed mode (see above).
  
Another way to set this manifest is by enabling "256-color mode" in the WA.exe settings' Compatibility tab, launching the game, and then removing the "256-color mode" checkbox. (The system doesn't become 256-colored because of what is said above).
+
Another way to set this manifest is by enabling '''256-colour mode''' in WA.exe properties' Compatibility tab, launching the game, and then removing the '''256-color mode''' checkbox. (The system doesn't become 256-coloured because of what is said above).
  
== When I go into settings, there are no resolutions in the drop-down list! ==
+
== There are no resolutions listed in the drop-down on the WA's settings screen ==
 
See the previous paragraph.
 
See the previous paragraph.
  
== Links ==
+
== External links ==
[http://forum.team17.com/showthread.php?t=57661 Team17 forum thread about Release Preview]
+
[http://forum.team17.com/showthread.php?t=57661 Has anyone gotten Worms Armageddon to work on Windows 8? - Team17 forum]

Latest revision as of 16:32, 19 December 2012

In other languages: English (en) • русский (ru) • +/-

This page describes getting W:A 3.6.31.0 working on Windows 8.

For 3.7.0.0 and higher, a simple solution is to either enable Direct3D 9 from the Advanced Settings screen as the graphics renderer or to set a compatibility flag for DirectDraw (not recommended).

It worked on Windows 7! Why doesn't it work properly on Windows 8?

Windows 8 no longer supports screen resolutions with colour depths other than "true colour" (24-bit depth or 16,777,216 colours). 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.

Solution

There are currently some known methods which should address the issue.

Method 1

  • Open Notepad, and copy and paste the following:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Team17\\Worms Armageddon\\WA.exe"="$ DWM8And16BitMitigation Layer_ForceDirectDrawEmulation"
  • If you installed W:A in a location different from C:\Team17\Worms Armageddon\, correct the path on the last line. Remember to use double backslashes instead of single ones.
  • Click FileSave to open the save dialog.
  • In the Save as type drop-down, select All files.
  • Enter FixWA.reg in the File name field, and save the file.
  • Locate the file using Explorer, and double-click it. Confirm Registry Editor's warning.
  • 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. 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.

Method 2

  1. If you haven't yet, install WormKit or WormKitDS at your choice. A working WormKit setup will be required for the following steps.
  2. Download this WormKit module and extract it to the W:A installation directory. The frontend's white fields should be fixed, however it does not affect in-game or frontend performance. If the game or frontend is too slow, proceed to the next step.
  3. Delete the wkFrontendFix.dll installed previously, and download the windowed mode libraries. Put them all into your W:A installation directory and launch the game. The libraries will emulate the graphics APIs used by W:A using modern APIs. Please check the included readme file, as it's not a bug-free solution. If everything in-game is fine for you, you may stop here. Otherwise, proceed to the next step.
  4. Only for W:A 3.6.31.0: Download and install Project X. Follow the instructions on the site. Assuming you have an average modern PC, there should be no problems during the game for you (the system requirements in Project X are higher than the default ones). Project X replaces W:A's in-game graphics code with a modern (DirectX 9) true color graphics API, which does not interfere with Windows 8's compatibility layers. Combined with the windowed mode libraries mentioned above, it should result in the best performance.


For the moment, these are the known methods which resolve performance and frontend issues on Windows 8, except emulating W:A. If you have anything to add, feel free to discuss on the talk page.

The error "Unable to set desired video mode" pops up when attempting to start the game

For some reason, Windows 8 identified W:A as an application targeting Windows 8, which forbids using non-24-bit screen modes.

See the fix method #1 to correct the problem.

Note: if your system doesn't support the 640x480 resolution, you will need windowed mode (see above).

Another way to set this manifest is by enabling 256-colour mode in WA.exe properties' Compatibility tab, launching the game, and then removing the 256-color mode checkbox. (The system doesn't become 256-coloured because of what is said above).

There are no resolutions listed in the drop-down on the WA's settings screen

See the previous paragraph.

External links

Has anyone gotten Worms Armageddon to work on Windows 8? - Team17 forum

Personal tools