The program would wrongly display information for unspotted obstacles and minefields if the user right clicked on the map at the location of a currently unspotted (invisible) obstacle or minefield.
The constant for number of items in the Network menu was too high by one number. Effect on program unknown but believed to be harmless.
The up and down arrow keys failed to scroll the map when the Artillery Support Window or the Air Support Window were open.
"Armored" was misspelled in the unit type name for "M9 Armored Combat Earthmover".
"Inflatable" was misspelled in the unit type names for "Boat, Inflatable" and "Boat, Inflatable + Motor". Bug fix to Map231c dat file. The UTM grid coordinates were displayed incorrectly on Map231c. Bug fix to Map240c dat file. The UTM grid coordinates were displayed incorrectly on Map240c. Incremented Map version to 301.
The Windows version wrongly inflated the cargo weight capacity for units with very large capacities such as landing craft.
In a few scenarios with Red defending, where certain units were coded as mobile security forces, the program always failed to order those units to fall back to alternate positions after contact.
If OPFOR was allowed to have thermal sights and if an OPFOR unit was added (via an options menu item) to game play after turn one it would intermittently not actually receive thermal sights unless and until the player visited the preferences settings window or unless and until the game engine visited the preferences settings internally (which happens automatically during many scenario editing and network activities)- even though the info window might show that unit to have thermal sights. This bug would only appear if OPFOR units were added to game play after turn on and only then if the preferences settings were never visited thereafter either intentionally by the player or coincidentally by the game engine.
The engineering object design windows used in creating minefields, entrenchments, obstacles, bridges, and landing zones were misleading in that the "location known to" check boxes wrongly appeared to suggest that one of these objects could be created so that its location was not known to the force color that built it. The location of these objects is in fact always known to the force color that built them. The "location known to" check box that matches the building force color is now disabled so that it can not be unchecked.
