V for Victory: D-Day Utah Beach

From Wikipedia, the free encyclopedia
  (Redirected from V for Victory)
Jump to: navigation, search
V for Victory: D-Day Utah Beach
Developer(s) Atomic Games
Publisher(s) Three-Sixty Pacific
Series V for Victory
Platform(s) MS-DOS, Macintosh
Release date(s)
Genre(s) Historic turn-based strategy[1]
Mode(s) Single-player

V for Victory: D-Day Utah Beach is a turn-based strategy wargame for the Macintosh and MS-DOS developed by Atomic Games in 1991 and distributed by Three-Sixty Pacific. Its success led to three further games in the V for Victory series, and then the similar World at War series published by Avalon Hill.

The game simulates the D-Day invasion on the area surrounding Utah Beach and the greater Cotentin Peninsula area. The player takes the role of overall commander of the US forces or the German forces opposing them. The game includes six scenarios to play as either side, one of which covers the entire invasion area up to the period just prior to Operation Cobra.


V for Victory: D-Day Utah Beach is a battle simulation war game based upon the Normandy invasion of World War II. The player may participate as either an American or German commander.[2]

There are six scenarios, the first five of which are individual battles. In the first scenario (which is also the tutorial scenario), the player leads the 9th Infantry Division in its attempt to clean out all German resistance behind American lines. In the second scenario, the 101st Airborne must take Carentan within three days. In the third scenario, the player faces an SS Panzergrenadier Division counterattack attempting to recapture Carentan. In the fourth scenario, the player assaults Cherbourg using four divisions, and in the fifth scenario the player attempts to permanently isolate Cherbourg. The sixth scenario is a total campaign game which will require hours of play to finish.[2]

The game also allowed the player to select a number of optional adjustments that influenced the battle. This included the ability to adjust the relative air strength of the two sides, from the default overwhelming advantage that the Allies had historically, to the unlikely event that the Germans might have slight air superiority - the manual stated that the events would not have taken place had the Germans maintained any major superiority in the air. Changing these settings has a dramatic effect on the amount of supplies flowing to the two sides; under the normal settings with complete Allied superiority, the Germans are constantly starved for supplies. The game also allowed the player to select the original airborne plan, which dropped the 82nd Airborne Division much further west; this plan had been changed just before D-Day after the discovery of new German units in the area. Additional German units, historically available but not committed to the battle, could also be brought into play.

Much of the battle follows historical lines, with the US slowly expanding their beachhead in the face of German troops entrenched in the bocage. Eventually their numerical superiority becomes overwhelming and the German forces are unable to cover all the gaps in the front line facing them. The slow movements through the bocages makes breakouts and encirclements difficult. Playing the Germans is significantly easier, consisting of a series of short movements to new defensive lines as the US forces destroy the German units piecemeal.

Games are "scored" by capturing and holding strategic locations on the map. These vary from mission to mission, and the points that are scored in one mission may or may not appear in others. Generally speaking, the game rewarded fast advances toward major strategic locations, like Cherbourg. Points were also awarded for minimizing losses and maximizing enemy casualties, and removed for using limited resources like battleship fire.


The game was played on a top-down 2D hex based map, with numerous terrain types. Each combat scenario has two phases. During the Planning phase, the player clicks on the unit icons to drag them to new locations. In the Execution phase, the player's battle plans are carried out.[2]

The game engine included many features that could not be simulated in traditional board games in order to eliminate drudgery. For instance, each unit individually tracked its supply status and local reserve. New supplies were delivered at night, using a system that simulated flow from one of a number of "supply points", the beach area for the US, or roads to the south for the Germans. Cutting a supply route would cause the supplies to be re-routed onto other roads, which might lead to choking. Artillery fire could also be used to delay the flow. All of these effects were simulated, added to the on-hand supply level, and then displayed to the user as a series of optional colorings that indicated current status. Reduced supply levels dramatically reduced the combat and movement capabilities of the units, and represented the majority of the effects on fighting strength of the armies as a whole. Straying too far from a source of supply would render a unit impotent, while surrounding one would quickly lead to its elimination. In the same manner, the game tracked fatigue levels, unit cohesion, level of command, casualties and other effects for every unit on the map. Even weather became important, as it changed the supply deliveries and interdiction.

The amount of information held by the system might be overwhelming, but the majority of it was hidden and automated. Supply level, for instance, only became visible if the player selected an option to show it. In this case, it would be displayed as a colored outline around the units, from green (combat ready) to black (out of supplies). The player could generally ignore these details and leave it to the computer AI to handle these issues. This went as far as allowing the computer to plot artillery fire missions for supply interdiction. In most cases, the player was tasked with the movement of units and direct artillery support for attacks. Even these could be automated if desired, and were for the non-player side.

Many aspects of the game were designed to improve playability, especially for non-hardcore war gamers. For instance, the game used small icons of men or tanks to indicate unit types, instead of the more opaque NATO unit markers that are commonly used in the wargame field. On the Macintosh platform, existing UI guidelines were used for all operations. The game eschewed the traditional highly-modal interfaces of most games, using Mac menus, mouse commands and dialogs boxes for most interaction. For instance, giving commands to a unit to move was handled simply by clicking on the unit and then dragging it to the desired location, stacks of units could be moved with a shift-drag. This UI element has since become common.

Development and production[edit]

The cover art for the Utah Beach edition of the V for Victory series was created by Marc Ericksen.


The Macintosh version of the game was reviewed in 1992 in Dragon #180 by Hartley, Patricia, and Kirk Lesser in "The Role of Computers" column. The reviewers gave the game 5 out of 5 stars, and noted "There is little doubt in our minds that this game is probably the best war simulation ever produced for any computer."[2] Computer Gaming World in 1992 similarly praised the Macintosh version, stating that Three-Sixty Pacific "appears to have come closest to a perfect synthesis of the board and computer formats". The reviewer described the game as among the "'must-haves' ... a wargame designed by wargamers for wargamers".[3] That year the magazine named it one of 1992's best wargames.[4] A 1993 survey of wargames gave by a second reviewer the game four stars out of five, describing it as "perhaps the smoothest conversion of a boardgame-style wargame to computer format ever done". He gave V for Victory II: Velikiye Luki and V for Victory III: Market Garden three-plus and four stars, respectively.[5] A third reviewer criticized Velikiye Luki and Market Garden as buggy and flawed. While praising V for Victory: Gold-Juno-Sword's documentation and SVGA graphics, he stated that the fourth game "succeeds only a technological level, bereft of soul" and compared the series to "a line of books without an editor". The reviewer concluded that "Three-Sixty's reputation in the hobby has suffered a major blow".[6]


  1. ^ a b V for Victory: D-Day Utah Beach at GameFAQs
  2. ^ a b c d Lesser, Hartley; Lesser, Patricia & Lesser, Kirk (April 1992). "The Role of Computers". Dragon (180): 57–61. 
  3. ^ Vanore, John J. (May 1992). "An Answer for Bored Boardgamers". Computer Gaming World. p. 86. Retrieved 24 November 2013. 
  4. ^ "CGW Salutes The Games of the Year". Computer Gaming World. November 1992. p. 110. Retrieved 4 July 2014. 
  5. ^ Brooks, M. Evan (October 1993). "Brooks' Book Of Wargames: 1900-1950, R-Z". Computer Gaming World. pp. 144–148. Retrieved 26 March 2016. 
  6. ^ Coleman, Terry (December 1993). "It Was the Best of Times, It Was the Worst of Times". Computer Gaming World. pp. 244,246. Retrieved 31 March 2016. 

External links[edit]