Registered owners of TOAW III may now download version 3.0.0.17 from the Members Area. The change list for this is as below.
It's a large download, as it includes a new set of scenario files, that have had the briefings updated, so that people know which can played against the PO.
Enjoy, and thanks for supporting Matrix Games and TOAD Team.
Change List for v3.0.0.17
1. All scenarios, except those in the “Classic TOAW” folder, have had their briefings edited to
designate which sides, if any, are playable by the PO. A brief caveat is in order here. The
determination of whether a scenario is “playable” by the PO is based on two primary
considerations. First, is whether or not the scenario designer has stated that one, both, or neither
side, have been programmed to be played by the computer. The second, is that lacking a scenario
designer’s stated confirmation, there was a cursory evaluation by the TOAD QA Team, as to
whether there appeared to be any set objective paths, strategic bias settings, orders and emphases
given to the various formations of one or both sides in a scenario. In depth testing of ANY
scenario, as to its particular suitability for PO play is beyond the scope of the QA Team’s mission,
and as it is highly dependent upon the skill level of the player, best left to them to determine
whether or not the designer has done an “adequate” job of programming Elmer.
2. The assumption here, is that all scenarios in the “Classic TOAW” folder have been programmed
for PO play, on both sides, with the exception of Balkans 12, which does not have the Turkish side
programmed for PO play. Thus, none of those briefings were edited and they are in their original
state, as released in the Talonsoft versions of the TOAW: Century of Warfare - the only
conversion, being that necessary to play on the Opart 300 based executable of TOAW III.
3. A new scenario, specifically designed for TOAW III, Gothic Line 1944, by Chuck Kotraba, is
included. It, its BMP file, and associated document, are found in the “WW II – Mediterranean”
folder.
4. A new graphic choice is offered to users, for customizing their graphics. This is at the level of
scenario folder. Thus, a user may insert graphics into their scenario folder, and all scenarios
within that folder will use the modified graphics. The priority that TOAW III uses in determining
what graphics will be used for a scenario is in the following order, from highest priority, to lowest:
AltGraphics\Scenario Name
Graphics\Scenario Name
AltGraphics\Year the scenario occurs (actually, it looks backwards for the first one with
that year, just like sounds)
Graphics\Year the scenario occurs
AltGraphics
Graphics
Thus, Graphics is overridden by AltGraphics, which is overridden by Graphics\Year, and so on, back
up the list.
5. New algorithms are used to speed up the supply determination and reconstitution points of units
during the Automatic Bookkeeping Phase. A marked improvement should be seen in the amount
of time it takes to process this phase, especially on the monster scenarios.
6. Elmer will now repair bridges. Previously, he didn't want to repair them.
7. Elmer should not be as likely to attack when given a defend order.
8. Units will be routed or forced into reorganization less frequently.
9. The sound system on some systems had a stability issue. This has been addressed.
10. Changing the .exe name should not generate a version mismatch error.
11. Low Aircraft subject to Low AA fire are divided by 3.
12. High Aircraft subject to Low AA fire are divided by 3. (no change from the current situation.)
13. Added T-64A in new equipment. This will cause a version error message if playing against
people who have not updated their program to this patch, and is intentional. You should ensure
that your opponent is playing with the same patch as you are!
14. Examines and possibly fixes the following event types. They may have had errors introduced by
TOAW: Century of Warfare while converting from Opart 100 to Opart 300.
WITHDRAW_UNIT_EFFECT
DISBAND_UNIT_EFFECT
WITHDRAW_ARMY_EFFECT
SET_FORMATION_ORDERS_EFFECT
UNIT_DESTROYED_TRIGGER
SET_OBJECTIVE_1_TRACK
If the scenario is changed, a test file is written out to the scenario directory. The scenario must be
saved in order to save the changes.
