Worms Armageddon ReadMe (English)/v22.214.171.124 Beta Update
From Worms Knowledge Base
Revision as of 12:03, 15 March 2013 by ReadmeBot (Automatic Readme conversion (2013-03-15 12:02:29.486000))
v126.96.36.199 Beta Update (2010.11.16)
- [DC] In emulation, /version messages, and Export Log output, W:A v188.8.131.52 incorrectly called the test versions "v184.108.40.206[BattyRope8]" and "v220.127.116.11[TestStuff8]" "v18.104.22.168[BattyRope7]" and "v22.214.171.124[TestStuff7]", respectively. It incorrectly called "v126.96.36.199[BoomRacing]" simply "v188.8.131.52", whereas it incorrectly called "v184.108.40.206" itself an empty string, "".
- [CS] Some features specific to internal testing (alpha) builds were accidentally left in v220.127.116.11.
- [CS] Bug in a feature introduced in v18.104.22.168: The game would sometimes crash during the worm death explosion animation, if the Russian language was selected.
- [CS] Bug in a feature introduced in v22.214.171.124: If, after joining a network game as a client, the user pressed the Escape key in the join lobby but clicked "Cancel", then subsequent clicks of the "Exit" button would display the Quit confirmation dialog box, even though the default behavior of the "Exit" button in that screen is to instantly quit. Alternatively, if, instead of clicking the "Exit" button, the game was started, and sometime during that game round the user quit, then W:A would show a Quit confirmation dialog box after switching back to the front end.
- [CS] Bug introduced in v126.96.36.199: On some systems, there was no sound in the front end. Starting with v188.8.131.52, W:A checks if the sound parameters requested by W:A are supported by the sound card's DirectSound driver. On some systems, the DirectSound driver incorrectly reported the sample rate used by W:A as out of range of its hardware secondary sound buffer sample rate specifications. W:A now does not check if the desired sample rate is within these specifications.
- [CS] Bug introduced in v3.5 Beta 1: If front end audio initialisation failed, minimising and restoring the game in the front end would result in various graphical artefacts, such as a mostly-black screen with white text and missing mouse cursor. This problem appeared for all users affected by the above problem.
- [CS] Despite the v184.108.40.206 fix preventing a momentary switch to 640×480 when launching replay playback, the display mode was still being set twice, redundantly (to the configured resolution both times). W:A now sets the display mode only once, which results in a faster launch on some or most systems. This also fixes the bug in which, on some systems, attempting to export videos from replays at certain resolutions failed with a front end video initialisation error message.
- [CS] Bug in a feature introduced in v220.127.116.11: The Russian file type description for .WAgame files was not being correctly registered.
- [CS] The Hungarian characters introduced in v18.104.22.168 could not be typed in the front end.
- [CS] Bug in a feature introduced in v22.214.171.124: The WormNET news window was being cleared when returning from a game.
- [CS, DC] LAN games hosted by v126.96.36.199 were only joinable via Direct IP due to Game ID checks and the fact that all versions before and including v188.8.131.52 did not send a correct Game ID for LAN games. Both problems have been fixed — v184.108.40.206 LAN hosts are now joinable by v220.127.116.11+ clients, and v18.104.22.168 LAN hosts are now joinable by older (v22.214.171.124 and earlier) clients.
- [CS] Bug in a feature introduced in v126.96.36.199: On some systems, the smooth background gradient was not being rendered properly on very tall maps.
- [CS] Map complexity and randomness
- [CS] Bug introduced in v188.8.131.52: Loading a particular .BIT or .LEV map caused mouse-click terrain generation to iterate through the same sequence of random maps every time that same map was loaded (either by the local user, by another user who downloaded that map, or by the host of an online game which the user joined). This behaviour is now changed — the sequence of generated maps will be different each time the respective W:A screen is opened, regardless of the initial map.
- [CS] Worms Armageddon will no longer store the RNG seed used for map generation and other tasks in the registry. Instead, a new seed is generated on each start, using a cryptographically random buffer. This removes any possibility of persistent effects on a W:A installation's RNG.
- [CS] When trying to connect to a v184.108.40.206+ game with a v220.127.116.11+ client using an incorrect Game ID, W:A will now show an appropriate error message instead of "Max Players".
- [CS] The Italian translation for the "Prod" weapon has been changed from "Pungolo" (in the front end) and "Bastone" (in-game) to "Spintarella".
- [CS] A slider has been added to the map editor, which allows controlling the range of complexity in randomly generated maps. This slider affects map generation outside the map editor as well, but not for Quick CPU and Deathmatch games (which will continue to be generated at maximum complexity). By default, the slider is set to the maximum complexity level, similar to the behaviour in versions v18.104.22.168 to v22.214.171.124.
- [CS] A new registry script, ResetRegistryOptions.reg, has been added. Importing this script will reset all Worms Armageddon options from the Windows registry. The Reset button in Advanced Options (added in v126.96.36.199) also does this, but also clears the options stored in win.ini.
- [DC] The "team (player) forced out by reason" message that is printed in red in the in-game chat, and also printed in Export Log, is now more descriptive in cases where the cause may be a HostingBuddy bug or message injection.