Defect Tracking

Defect Name: Unable to complete intercept of base Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Unable to complete intercept of base.hph Long Description: Air group ARa is ordered to attack base ZWa. Proper intercept procedure is followed and group is ordered to close to 60nm to attack. However, the message, "Group ARA completed intercept of enemy units and is loitering in the area." appears immediately and group does not move towards the base. Manual interception is required. Weapons function normally. Sequence to reproduce: 1. Order ARa to attack base ZWa surface units 2. Message, "Group ARA completed interce…

Defect Name: Group survivors form improper group Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: saved game Group survivors form improper group.hph Long Description: Airfield ACb is destroyed. Ground units grouped with the base now form a group called "DL". Two letter designation for a group is improper. All units should have 3 characters. Also, when DL is selected and all units are detached to a new group, EQr is formed (a proper group). Sequence to reproduce: 1. Select DL and detach all units with F8 2. EQr is formed Expected behaviour: Proper new group should be formed from survivors of destroyed base…

Defect Name: Manual interception required Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Manual interception required.hpn Long Description: When ordered to attack a ship with an air group, the message "Close to attack with cannon fire?" is displayed. However, if the air group is already in range of the target, the weapons allocation window will appear normally. Manual interception is required. Sequence to reproduce: 1. Order ARa to attack YEs. 2. Cannon fire message appears 3. Move ARa next to YEs then repeat attack order. 4. Weapon allocation window appears normally. Expected behaviour: When ordered to atta…

Defect Name: Ineligible target type Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Ineligible target type.hph Long Description: When ordered to attack a surface group known to contain ships, subs, and aircraft, only subs and aircraft are offered as target types. Sequence to reproduce: 1. Order DOa to attack ZRc. 2. Only Submarine and Aircraft show up as eligible targets Expected behaviour: All three platform types should show up on selection menu Observed behaviour: Only two platform types show up on selection menu Ineligible_target_type.zip

Defect Name: Runway too short for Harrier Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Runway too short for Harrier.hph Long Description: Beachhead Charlie, AAp, allows some versions of the AV-8 Harrier to land on it yet prevents other Harriers. I think that all Harriers should be the same type of aircraft utilizting the same landing restrictions/requirements. Sequence to reproduce: 1. Attempt to ferry Harriers from ship group AIs to AAp Expected behaviour: All Harriers should have the same landing requirements. Observed behaviour: Harriers have different landing requirements. Runway_too_short_for_Harrier.zi…

Start a new WestPac mission with Game Options all to Yes except for Full Ordnance. Side: BLUE. Then choose the last mission, "The Backyard", hit New Game - and for me it usually crashes at this point. It seems to have something to do with mission settings, because when I set all Game Options to Yes, it launches just fine. OS: XP Ver: HCE, the latest relase, meaning 2007.000, I guess. DB: Standard one that goes with this release.

Defect Name: Phantom air group attempts landing Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Phantom air group attempts landing.hpe Long Description: "Select Group for landing" window appears for unspecified air group. Only two air groups are airborne. Nothing happens regardless of the landing field selected. Sequence to reproduce: 1. Run until window for selecting landing field appears Expected behaviour: "Select Group for landing" window should not appear Observed behaviour: "Select Group for landing" window appears Phantom_air_group_attempts_landing.zip

Defect Name: Barges in harbour cannot be torpedoed Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Barges in harbour cannot be torpedoed.hpe Long Description: Barges grouped with land facilities cannot be attacked by torpedo even though the vessels are clearly in open water. Attack is possible by SLCM. Sequence to reproduce: 1. ADu cannot attack ZIp with torpedoes Expected behaviour: Ships in port should be open to attack from torpedoes Observed behaviour: Ships in port cannot be attacked with torpedoes Barges_in_harbour_cannot_be_torpedoed.zip

Defect Name: Aircraft Grouping Not Logical Build: 2007.000 (Aug 12 2007 Release) Repeatable: Y Operating System: XP Database: I have no idea - the standard thing that goes with HDSC 10.0 Scenario: grouping_problem.zip Long Description: I'm used (HC 2002) to the fact that aircraft flying in one group are in a tight formation that causes them to appear as one icon both on Group Map and Unit Map. In HCE it seems to be different. In the attached scenario, I have launched an attack group comprised of two SEAD A-6s, one SEAD F-18 and two F-14s for AA cover. Unforutnately, HCE for some reason decided that the SEAD aircraft should fly some considerable distance in front …

Defect Name: Damage display corrupted [2006] Build: Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Damage display corrupted [2006].hpi Long Description: After base is damaged by missiles, the Unit display is corrupted. Sequence to reproduce: 1. Run saved game Expected behaviour: Display should not be corrupted. Observed behaviour: Display is corrupted. Damage_display_corrupted__2006_.zip

Defect Name: Specific Class not possible in ViConds Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Specific Class not possible in ViConds.scm Long Description: Unable to select the Class category for any type of Victory Condition. Consequently, scenario designers are no longer able to specify individual bases for ViConds. Sequence to reproduce: 1. Attempt to modify/add ViCond to scenario 2. No combination of selections will allow the user to specify destruction of Keflavik [only] as a ViCond Expected behaviour: ViConds should allow for more specific conditions Observed behaviour: Individual bases can no l…

Defect Name: Ghost of Scorpio Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Saved game - Ghost of Scorpio.hpi Long Description: Scorpio ship unit ZC04 does not appear to be susceptible to attack. Two attacks were made against group ZCs with 15+ Harpoon allocated to Scorpio on both occasions. No hits and now the player is unable to select the ship group for attack. This scenario was played before and I *think* that I was able to kill the ship, but I cannot be certain. Sequence to reproduce: 1. ZC04 cannot be attack. Player cannot even launch group against ZCs. 2. Note that the oddly discoloured icon for Scorpio …

Defect Name: Text wrapped around Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Text wrapped around.SCn Long Description: Text name for ships in formation editor wraps around onto next line. Sequence to reproduce: 1. Select formation ZDS and hit Formation Editor 2. Name of Tarantul wraps onto next line Expected behaviour: Names should be only on one line Observed behaviour: Names wrap around onto following lines Text_wrapped_around.zip

Defect Name: Air patrol runs out of gas Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Saved game - Air patrol runs out of gas.hpi Long Description: Formation air patrol AA29 runs out of gas on its own. Sequence to reproduce: 1. Run saved game for about 10min. High compression is okay. Expected behaviour: Formation air patrols should never run out of gas Observed behaviour: Formation air patrol runs out of gas. Air_patrol_runs_out_of_gas.zip

Defect Name: Cannon fire only Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: saved game Cannon fire only.hpi Long Description: When ordered to intercept with Sidewinders and Phoenix, Tomcats show the "Should we attack with only cannon fire?" message. The targets are well within Phoenix range. Even if target is inside the minimum range of Phoenix and _outside_ maximum range of Sidewinder, Staff Assistance should ask to engage and use the shorter-ranged Sidewinder as the basis and display a message like, "Effective range is 10nm. Target range is 15nm. Shall we close to intercept?" Sequence to reproduce: 1. Immediate…

Defect Name: AS-4 attacking submarines Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: saved game AS-4 attacking submarines.hpi Long Description: AS-4 anti-ship missiles have been fired at submarines and attempt to engage them. SSNs were never eligible targets in the first place and were never on the surface. Sequence to reproduce: 1. Run scen and watch as AS-4s attempt to intercept SSNs Expected behaviour: AS-4 missiles should not attack submarines Observed behaviour: AS-4 missiles try to attack submarines AS_4_attacking_submarines.zip

Defect Name: Double request for target type Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: saved game Double request for target type.hpi Long Description: When attempting to launch an air strike against an enemy surface group, the game will ask for the target type twice. Sequence to reproduce: 1. Order AAC to launch an air strike of 2 Corsair vs. ZXC 2. Double request for target type 1.gif appears right away 3. After Corsairs have been allocated and strike begins to launch, the second request appears 4. Double request for target type 2.gif appears Expected behaviour: Game should remember strike mi…

Is this behaviour going to cause any problems when the a/c have more than one type of weapon? i.e. a plane with both ARMs and bombs/AShMs? Will the release of one type cause the a/c to return to base? Conversely, will the non-release of one type (i.e. ARMs) cause the plane to continue even though it should probably RTB once the AShMs are fired?

Just playing a user scenario, and saw a flanker being shot down by a green pakistani ship. I saved it, and then the 2nd plane gets shot down as well. The game tells me I've shot down the plane. It seems logical enough that green has shot down the red plane, but my question is this supposed to happen? And would the green ships attack my planes? Should I sink green ships that threaten my forces? I remember one scenario which has a green ship which looks like a merchant cargo ship, but has a nuclear weapon in it's loadout. pakiflanker.zip

Defect Name: Extraordinary sonar range Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: User scen - ROURKE.SCm Long Description: Extraordinary sonar range from DDG Burke and other vessels; sometimes in excess of 200nm CZs for even fairly quiet subs like Oscar and Victor III. This scenario was originally built for EC2000. For the re-building process, the editor changed the suffix from SCi to SCm and then ensured that all the units were proper. No idea if this is a contributing factor for this behaviour. Sequence to reproduce: 1. Run scen at high compression from Blue side 2. Sub contacts will just materializ…