Worms: Armageddon v3.8.1 Patch

The official patch for Worms Armageddon released on 23 December 2020, which resolves a few issues from the gigantic 3.8.0 release...

Download

Uploading...
Do not refresh or leave this page!

File Description

The official patch for Worms Armageddon built on 8 November 2020, but released on 23 December 2020, which resolves a few issues from the gigantic 3.8.0 release.

Produced by community members Deadcode and CyberShadow under the approval of Team17. This update requires a previous installation of patch v3.0.

Not to be used on Steam and GOG.com copies of the game.

Read More

Download '185461-65995-WA_update-3.8.1_[CD]_Installer.exe' (2.36MB)

About This Version (3.8.1)

Version: 3.8.1

Released: 23rd December 2020 10:12am

Readme
v3.8.1 Update (2020-11-08)

Fixes
•	[DC] Bug in a feature introduced in v3.6.28.0: If a .PNG file with more than 112 non-black colors was loaded in the Map Editor, it could then be resaved (using the "Save" button) without being reduced to 112 colors, resulting in a .PNG file with the W:A-specific chunk that was nevertheless not a valid W:A map.
•	[DC] Bug in a feature introduced in v3.8: If "RubberWorm anti-sink" was enabled, and "RubberWorm bounciness" was not, the anti-sink state would not be saved for instant replays, and thus would result in a desync if anti-sink was actively used during an instant replay.
•	[DC] Bug introduced in v3.6.29.0: In the Offline Multiplayer screen and the Options Menu, if the current scheme was intrinsic or "[ User defined ]" (i.e., "transparent select all" was active, such that typing anything into the scheme name box would clear/overwrite its entire contents), and then a scheme file was loaded, "transparent select all" was not deactivated as it should have been.
•	[DC] Bug in a feature introduced in v3.8: Tweening was completely inactive during playback of replays extracted from network logs (a special kind of replay file that currently only W:A developers can create).
•	[DC] Bug introduced in v3.8: In the Steam edition of the game, the hotkeys to open the Steam overlay (default Shift+Tab) and to take a screenshot (default F12) did not work while in-game. (Note that it is recommended to remap or disable the screenshot key, because F12 is used by W:A in-game, to select weapons in the bottom row of the weapon panel.)
•	[DC] Bug introduced in v3.8: When at least one player in an online game was using v3.6.22.0-v3.7.2.25, and a .PNG map with >96 non-transparent (i.e. non-black, if no tRNS chunk is present) colors was in use (which is supposed to result in the soil texture being fully transparent), and the game was not emulating a logic version earlier than 3.6.22.0, v3.8 would fill the soil texture with the color at palette index 110 of that map (or if the map used fewer colors than that, one color from the background gradient).
•	[DC] Bug introduced in v3.8: If a Super/Aqua Sheep detonated while in flying mode (without switching to falling mode first), or an Aqua Sheep disappeared off the ocean bottom while in swimming mode, then Home Lock (activated by pressing Ctrl+Home) would never work again for that team (but would still work for other teams) for the rest of the round.
•	[DC] The Reset button in Advanced Options (added in v3.6.30.0), and the registry script ResetRegistryOptions.reg (added in v3.6.31.0), did not reset the following:
•	The current pseudo-random number generator Logic Seed
•	The "Export Video" dialog box's remembered parameters (added in v3.8)
•	The "Assisted vertical sync" tuning parameters (added in v3.8)
•	[DC] Bug introduced in v3.8: Any PNG map saved using v3.6.28.0 or later (excluding those converted from LEV or BIT maps), when loaded, would have the cavern status in its W:A metadata ignored, and autodetected instead, as if loading a PNG image lacking W:A metadata. For example, if a regular (non-W:A) PNG image was loaded in W:A's Map Editor, such that W:A autodetected it as an island (with no cavern border), and the user then manually turned on the top cavern border and resaved the map, then this map, when loaded later, would have the cavern border turned off.
•	The Finnish, French, German, Portuguese, Russian, Spanish, and Swedish translations have been updated by Juho Toivanen, LTK, schaf, Kaleu, StepS, OutofOrder, and Olle Settergren, respectively, encompassing all new strings added since v3.8. This also includes some corrections and improvements to existing strings.
•	[DC] A bug in the Spanish translation has been fixed by OutofOrder: The lines "Hold Shift for fine tuning" and "Hold Shift to change the amount" were missing.
•	[CS] Bug in a feature introduced in v3.8: When using the OpenGL (shader) Graphics API with a screen resolution with a width that is not a multiple of four (for example, 1366×768), the video output would appear skewed.
•	[DC] Fixes affecting game logic
•	[DC] An explosion happening anywhere on the map would nullify the horizontal velocity of all Frozen Worm(s), regardless of where they were. (A frozen worm may have horizontal velocity if it was moving in mid-air when another worm on the same team used Freeze.) Now, explosions have no effect on the horizontal velocity of frozen worms, affecting only their vertical velocity; this is indistinguishable from the previous behaviour when they already have zero horizontal velocity.

Changes
•	[DC] With skipwalking facilitation enabled (which was part of TestStuff, and is now an extended scheme option), it is now possible, during retreat time and after the first shot of a Shotgun or Longbow, to skip-walk by right-clicking the mouse (and not only by pressing the up/down/middle arrow keys).
•	[DC] The W:A v3.7.0.0 fix "When W:A is run under Windows 8 for the first time, it will offer to configure Windows compatibility flags which should improve compatibility and performance under Windows 8." was removed in v3.8, but because this compatibility flag is in fact harmful to DirectDraw performance, and may still be enabled if v3.7.0.0 or 3.7.2.x has previously been run under the same Windows installation, W:A will now check for its presence when started, and disable it if it is currently enabled (showing a dialog box to explain that this has been done).
•	[DC] W:A v3.7.0.0 and v3.7.2.1 set the default renderer to DirectDraw (32-bit), and this would be saved in the registry even if the user hadn't altered the setting from its default. However, due to increasingly poor DirectDraw performance in modern Windows versions, and the fixing of various bugs in the Direct3D 9 (shader) renderer, since v3.8 the recommended and default renderer has been the latter, so long as the necessary support is detected. The first time v3.8.1 is launched, W:A will therefore now change the renderer to Direct3D 9 (shader), if it would otherwise normally have chosen that renderer as the default, and if the renderer was already set to DirectDraw (32-bit).

Read More

Comments on this File

There are no comments yet. Be the first!

Share This File
Embed File