Difference between revisions of "Worms Armageddon ReadMe (English)/v3.6.21.2 Beta Update"
From Worms Knowledge Base
m |
(3.8 readme export) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <!-- DO NOT EDIT! This page was automatically generated by a program - your edits will be overwritten. Discuss changes on the talk page instead. --> | |
| − | + | {{ParentArticle|[[{{WAreadmepage}}]]}} | |
| − | + | {{Languages/3.6.21.2}} | |
| − | ! | + | |
| − | | | + | |
| − | + | ||
| − | * The first fix in the list | + | ===Fixes=== |
| − | * When a player tries to Teleport to a spot that is partially blocked, the cursor is nudged to the nearest available spot and a spangle flashes in the new spot. But in a game with v3.6.21.1 as the logic version (i.e., no emulation) this would only look correct on the local end, while a game was being played. To remote players in a network game, and during playback, the cursor nudge and spangle would not show up. | + | * The first fix in the list of v3.6.21.1 Fixes was actually a regression for some people not running Windows XP.<br /> |
| − | * The message "''Game will take advantage of the latest n.n.n.n features and bug fixes''" will now display the game logic version rather than the exe version. | + | * When a player tries to Teleport to a spot that is partially blocked, the cursor is nudged to the nearest available spot and a spangle flashes in the new spot. But in a game with v3.6.21.1 as the logic version (i.e., no emulation) this would only look correct on the local end, while a game was being played. To remote players in a network game, and during playback, the cursor nudge and spangle would not show up.<br /> |
| − | + | * Bug in a feature introduced in v3.6.19.7: The message "'''Game will take advantage of the latest ''n.n.n.n'' features and bug fixes'''" will now display the game logic version rather than the exe version.<br /> | |
| − | * Speed / update rate | + | * Speed / update rate<br /> |
| − | ** A check was inadvertently disabled, the purpose of which was to prevent the clock from ticking more than 1/4 second during a chunk of "screen lag". It is now re-enabled. | + | ** Bug introduced in v3.6.21.1: A check was inadvertently disabled, the purpose of which was to prevent the clock from ticking more than 1/4 second during a chunk of "screen lag". It is now re-enabled.<br /> |
| − | ** During an instant replay, a fast-forward that was fast enough to drop frames could overshoot the end of the turn, eating into the turn time of the next Worm. | + | ** Bug in a feature introduced in v3.6.19.7: During an instant replay, a fast-forward that was fast enough to drop frames could overshoot the end of the turn, eating into the turn time of the next Worm.<br /> |
| − | ** | + | ** v3.6.21.1 restricted the rendering rate from dropping below 10 fps. This was too arbitrary. The frame drop threshold is now calculated as a point of diminishing returns, where further frame dropping would not boost the speed by more than 10%. When fast-forwarding, this is often well above 10 fps, especially on faster computers (this should also make screen lag more tolerable). Additionally, slow computers may sometimes need to drop below 10 fps (for example, when a lot of fire is being thrown around).<br /> |
| − | ** In-game palette fading is smoother now. This is | + | ** In-game palette fading is smoother now. This is accomplished by two changes: streamlining the way fading is done (previously, each fade increment was done separately for objects, water and terrain), and making external applications unaware of the game's palette adjustments. (The latter is a workaround for that fact that, regarding palettes, DirectDraw does not give exclusive treatment to full-screen apps.)<br /> |
| − | * Volume adjustments | + | * Volume adjustments (introduced in v3.6.19.7)<br /> |
| − | ** When the volume was adjusted in the front end, and a game was started within the same session, the adjustment would be forgotten. | + | ** When the volume was adjusted in the front end, and a game was started within the same session, the adjustment would be forgotten.<br /> |
| − | ** Volume adjustments in the front end are now instantly applied to the ambient "menu loop". | + | ** Volume adjustments in the front end are now instantly applied to the ambient "menu loop".<br /> |
| − | ** The volume setting was not being applied to the "loading tick" sound effect (made each time the pie chart fills by an extra 4%) | + | ** The volume setting was not being applied to the "loading tick" sound effect (made each time the pie chart fills by an extra 4%)<br /> |
| − | + | ===Changes=== | |
| − | |} | + | * For readability, the Extract Log feature now uses "'''•••'''" to denote game events rather than "'''****'''" as before.<br /> |
| + | |||
| + | {{WA_VersionHistory|en}} | ||
Latest revision as of 20:43, 25 August 2020
Fixes
- The first fix in the list of v3.6.21.1 Fixes was actually a regression for some people not running Windows XP.
- When a player tries to Teleport to a spot that is partially blocked, the cursor is nudged to the nearest available spot and a spangle flashes in the new spot. But in a game with v3.6.21.1 as the logic version (i.e., no emulation) this would only look correct on the local end, while a game was being played. To remote players in a network game, and during playback, the cursor nudge and spangle would not show up.
- Bug in a feature introduced in v3.6.19.7: The message "Game will take advantage of the latest n.n.n.n features and bug fixes" will now display the game logic version rather than the exe version.
- Speed / update rate
- Bug introduced in v3.6.21.1: A check was inadvertently disabled, the purpose of which was to prevent the clock from ticking more than 1/4 second during a chunk of "screen lag". It is now re-enabled.
- Bug in a feature introduced in v3.6.19.7: During an instant replay, a fast-forward that was fast enough to drop frames could overshoot the end of the turn, eating into the turn time of the next Worm.
- v3.6.21.1 restricted the rendering rate from dropping below 10 fps. This was too arbitrary. The frame drop threshold is now calculated as a point of diminishing returns, where further frame dropping would not boost the speed by more than 10%. When fast-forwarding, this is often well above 10 fps, especially on faster computers (this should also make screen lag more tolerable). Additionally, slow computers may sometimes need to drop below 10 fps (for example, when a lot of fire is being thrown around).
- In-game palette fading is smoother now. This is accomplished by two changes: streamlining the way fading is done (previously, each fade increment was done separately for objects, water and terrain), and making external applications unaware of the game's palette adjustments. (The latter is a workaround for that fact that, regarding palettes, DirectDraw does not give exclusive treatment to full-screen apps.)
- Bug introduced in v3.6.21.1: A check was inadvertently disabled, the purpose of which was to prevent the clock from ticking more than 1/4 second during a chunk of "screen lag". It is now re-enabled.
- Volume adjustments (introduced in v3.6.19.7)
- When the volume was adjusted in the front end, and a game was started within the same session, the adjustment would be forgotten.
- Volume adjustments in the front end are now instantly applied to the ambient "menu loop".
- The volume setting was not being applied to the "loading tick" sound effect (made each time the pie chart fills by an extra 4%)
- When the volume was adjusted in the front end, and a game was started within the same session, the adjustment would be forgotten.
Changes
- For readability, the Extract Log feature now uses "•••" to denote game events rather than "****" as before.
