Heavy Gear II

An atrocity caused by the New Earth Concordat (NEC) — the destruction of the Badlands city of Peace River by an antimatter bomb — leads to a formal cease-fire between the Northern and Southern Leagues. A team of elite Special-Ops pilots from across the planet, equipped with advanced prototype Gears and a newly unveiled intersystem assault shuttle, are sent through the interstellar Tannhauser gate to the planet Caprice, the nearest NEC base, to find out more and strike back at the enemy.

Heavy Gear II incorporates third-person and stealth elements.

Development of Heavy Gear II began during the autumn of 1997 with an aggressive 13 month schedule which aimed to ship the game in autumn 1998. The Heavy Gear II team was a newly formed group within Activision, composed of some of the best and brightest employees that the firm had available, each of whom had experience working on several 3D games previously.[5][6] The design team wanted to move away from the larger BattleMech style gears as found in the original Heavy Gear, and to smaller, more agile gears, staying truer the Heavy Gear universe and allowing for faster paced and more diverse gameplay.[6][7]

Work began on a new game engine, named Dark Side, to power the title. Built in C++, the first priority for the engine was stability, with a focus on memory management and leak tracking, allowing developers to spot memory leaks as soon as they occurred, rather than later on in a test cycle. By adopting a modular approach to their engine design, developers could easily switch in and out different systems as they experimented during the development process.[5]

Although there were debates within the team regarding the issue, it was concluded that software rendering was insufficient to deliver on the teams' visual goals, and so support was dropped from the engine, making video cards a necessity to run Heavy Gear II. This allowed the team to focus on delivering a single high quality product, saving the team from having to replicate in-game assets at lower level of details for lower specification machines, cutting time in production and testing.[5] By targeting only video card equipped machines, Heavy Gear II could feature more units on screen and greater environmental detail.[8]

Offloading the visual rendering to dedicated video cards allowed for CPU cycles to be freed up for other uses such as AI systems. The approach to AI was to go for a high level "autopilot" system, whereby non-player characters could decide for themselves what objectives to achieve and how to go about it. This reduced the need for individually scripted actions, and enforced a consistent feel across all missions.[5] Enemy units have a tactical awareness on the battlefield, and will keep track of the successes and failures of different approaches against the player character, varying their tactics depending on the situation. Enemy units may split off into separate fireteams, call upon reinforcements or order artillery strikes against the player.[6]

Multiplayer was an important element in the game, and it was implemented using an internal Activision networking SDK early in development, before even the single-player portion of the game.[5][8] Although co-operative multiplayer was also planned, this feature had to be dropped, as it proved impossible to populate the game with enough enemy units to make the game challenging. The missions designed for the planned co-op mode were, however, saved for the standalone single-player "Historic Missions" in the final game.[8]

Despite the experience of the team, Heavy Gear II did not adhere to the intended schedule. The team underestimated the work needed to produce a demo, and did not factor in costs involved with employee turnover into their original schedule. When the game was released in June 1999, it had missed the intended ship date by approximately nine months. This slippage also had a negative impact on the effectiveness of the marketing campaign.[5] The Dark Side engine would be used again in Activision's Interstate '82, released later that year.[7]

In October 1999, Loki Software was assigned to port Heavy Gear II across to Linux.[9] The Linux port took Loki Software approximately 6 months to complete, and was described by Loki as "their most challenging product to date".[10][11] As Heavy Gear II uses Microsoft's proprietary Direct3D API for graphical rendering, Loki had to port this to OpenGL in order for it to run on Linux.[11] To realise the game's 3D sound on Linux, Loki worked with support from Creative Technology to build an open standard audio API from scratch with a cross-platform free software implementation, named OpenAL.[12] Heavy Gear II was the first Direct3D game to be ported to OpenGL, and was the first to implement OpenAL.[4] The Linux port was released in April 2000, and a demo followed in June.[13]

The game received favourable reviews according to the review aggregation website GameRankings.[14] The game was compared favourably to its predecessor, Heavy Gear, with PC Zone stating that it was a huge improvement over the first game, and GameSpot believing that Activision had redeemed itself for the failures of the original.[28][22]

Critics praised the gameplay. NextGen described the game as "a big, splendid mech sim, with lots of depth and excellent balance between action and strategy".[25] PC Zone echoed similar sentiments, calling it "a commendable stab at creating a balanced blend of strategy and all-out bot-blasting action".[28] IGN highlighted the diversity on offer, stating that the "variety in environments, variety in Gear loadout and variety in gameplay" was above and beyond that offered by others in the genre.[23]

The Dark Side powered graphics were well received. GameSpot described the graphics as being "very impressive, with detailed, heavily articulated gears and vehicles, natural-looking fauna [and] vivid landscapes".[22] Maximum PC described the engine as "gorgeous", praising it for providing "sharply rendered mechs and terrain details, as well as eye-popping explosions that light up the landscape" and other graphical effects. It did note, however, that there were "a few clipping and polygon-collision-detection glitches", similar detractions were noted by Linux Journal and IGN.[24][29][23] Performance wise, PC Gamer UK found it ran surprisingly well, even below the minimum requirements, while Maximum PC noted that the game maintained a consistent 30 fps on their test machine.[30][24] IGN warned, however, that they encountered several crash bugs on the instant action and historical mission modes.[23]

Critics enjoyed the Gear customisation options. IGN, NextGen and Linux Journal all highlighted the sheer number of options available.[23][25][29] Although GameSpot felt that the "threat level" limitation was artificial, it praised the flexibility it offered.[22] PC Zone stated it was "a joy to give birth to these new creations and see them succeed in the task they were created for", in regards to the Gear customisation process.[28]

Response to the AI was mixed. GameSpot praised the AI as challenging, and PC Zone described the enemy AI as being "clued-up on battle tactics", able to "dodge and weave all over the place" as well as seek reinforcements.[22][28] PC Gamer UK disagreed, accusing the AI of being "absolutely, hilariously terrible", a view shared with Linux Journal, who described the AI as being "basically pathetic", both critics cited examples of poor pathfinding.[30][29]

Critics reacted favourably to the multiplayer options. PC Zone described it as being "well-conceived and well-supported", highlighting the various modes of multiplayer gameplay and the "thriving clan structure".[28] While IGN felt that there was nothing particularly new or innovative in the multiplayer game, and Maximum PC felt that it was not as strong as the single player experience, both critics still felt the multiplayer experience to be worthwhile.[23][24] GameSpot compared the multiplayer element favourably to that of rival mecha game, MechWarrior 3, but, like Linux Journal, found the lack of co-operative multiplayer a disappointment.[22][29]

Some critics pointed out difficulty in adapting to the controls. PC Zone found the controls frustrating, warning readers about the "virtually insurmountable learning curves".[28] The control system was described as the most notable flaw in the game by IGN, with the critic having to resort to using a printed controls reference card included with the game.[23] Linux Journal looked at it from the other direction though, pointing out that once mastered, "the payoff, however, is extraordinary; the level of control a player has in HG2 is amazing".[29]

The game was commercially unsuccessful.[31] In the United States, it sold 15,000 units by the end of July 1999, according to PC Data. Mark Asher of CNET Gamecenter called these figures "pretty awful" and remarked that it "has to be a major disappointment for Activision".[32] The game's sales in the United States rose to 28,598 copies by the end of 1999.[33] Daily Radar's Andrew S. Bub named it the most unfairly overlooked simulation title of the year.[31]

The game was nominated for Computer Gaming World's 1999 "Science Fiction Simulator of the Year" award, which went to Freespace 2.[34] It was also nominated for PC PowerPlay's "Best Fantasy Sim" award, which went to MechWarrior 3.[35]

Although a sequel was reported to be in production at Savage Entertainment, this was ultimately cancelled. Activision would discontinue development on the Heavy Gear franchise in 2002, believing that strictly PC games such as Heavy Gear II did not have a viable future with the launch and growth of sixth generation consoles.[36][37] No further news of Heavy Gear video games appeared until 2012, when Dream Pod 9 announced that Stompy Bot Productions were to produce a new game.[38] In 2013, Stompy Bot launched a crowdfunding campaign, aiming to raise $900,000 towards the development of Heavy Gear Assault. Though the Kickstarter element of the campaign failed, development of the game is still ongoing.[39][40]

• Official website at the Wayback Machine (archive index)
• Heavy Gear II at MobyGames