Defect Tracking

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…

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…

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: Convoy will not slow down [2006] Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: United We Sail Long Description: Convoy is ordered to stop but ignores order and returns to cruise speed Sequence to reproduce: 1. Order convoy to full stop. 2. Run at 1 min compression 3. Convoy re-starts movement at cruise speed Expected behaviour: Convoy should stop and remained motionless. Observed behaviour: Convoy re-starts on its own accord. Convoy_will_not_slow_down__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: 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: No Standoff attack possible Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Ambush Long Description: Sub group ordered to attack carrier group. Elects to attack the sub in the group with Stand-off weapon. However, Weapons Allocation window is blank. Sequence to reproduce: 1. Run No Standoff attack possible.hp2 2. Order subgroup ZWU to attack AFC submarines with Stand-Off weapon 3. Weapon allocation menu appears with no eligible weapons Expected behaviour: Eligible weapons should appear for selection or else the window should not be called. Observed behaviour: Allocation screen is blank. No_Stand…

Defect Name: Displays incongruent [2006] Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Test Scen, Displays incongruent.SCp Long Description: Information displayed in the Unit Window is often inconsistent. Sequence to reproduce: 1. Start scenario from Blue side and select Arleigh Burke destroyer in the Unit window. 2. Hit the [D]isplay hotkey. Sonar range for SQS-53C shows as 6.5 nm. 3. Then hit the [F]ull display hotkey. Sonar range shows as 9.5 nm. Expected behaviour: Same information should appear on both displays. Observed behaviour: Different information appears on both displays. Displays_…

Defect Name: Launch Limbo [2006] Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Launch Limbo.SCo Long Description: When aircraft are either launching or landing, if the aircraft in the group are destroyed before the group is fully launched/landed, the aircraft that have not yet launched to / already landed from the group are stranded in limbo either as launching or landing. Sequence to reproduce: 1. Play as Blue 2. Order all 61 Cock transports to ferry to the other base. 3. Watch Red destroy the first few aircraft in the group and the remainder are stranded. Expected behaviour: Aircraft should not be stranded …

Defect Name: Have Nap malfunction [2006] Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Have Nap malfunction [2006].SCn Long Description: AGM-142 Have Nap cannot hit the target. This missile has the Command Guidance and Mid-Course Guidance flags. Under manual control, they can hit if the player remains in the area. However, under AI control, the attacking aircraft launch and immediately turn for home base so the missiles always miss. Sequence to reproduce: 1. Play from Red. 2. Set 30 min time compression. 3. Watch Blue aircraft launch, RTB, and then missiles miss. Expected behaviour: Missiles should track to …

Defect Name: Shot down during landing [2005] Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Stage Fright [EC2003 IOPG] User-created Long Description: Air Group BJA consisted of four aircraft. BJA is in the process of landing. Two have already landed. One was shot down. The final aircraft in the group is about to be shot down. When it is shot down, the two aircraft already on the ground will be stranded in limbo and listed as Landing, but they will never move out of that phase and are forever lost to the player/AI. This situation is easily replicable for any DB and is definitely not specific to HCDB. Sequence to r…

Defect Name: Patrol zones centred on wrong position Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Patrol zones centred on wrong position.sc1 Long Description: Formation patrol zones are centred on different positions and not consistent This can cause major problems when trying to add new air or ship patrols. Sequence to reproduce: 1. Change zone size for formation to 1nm, 2nm, 3nm, 4nm. 2. Re-position ships by ordering them to the same zone they occupied before the ranges were changed Patrol zones centred on wrong position [assigned].gif 3. Run at high compression to allow ships to move to patrol zones …

Defect Name: Patrol zones do not match positions Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Patrol zones do not match positions.sc1 Long Description: Graphic circular display in formation editor does not match ship positions. Sequence to reproduce: 1. Change zone size for formation to 1nm, 2nm, 3nm, 4nm. 2. Re-position ships by ordering them to the same zone they occupied before the ranges were changed Patrol zones do not match positions [assigned].gif 3. Run at high compression to allow ships to move to patrol zones 4. Hit Formation editor. Patrol zones do not match positions [actual].gif …

Defect Name: Sub ignores patrol zone Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Sub ignores patrol zone.sc1 Long Description: Sub ignores assigned formation patrol zone. This problem was first identified by Mark Kratzer. Sequence to reproduce: 1. Start Sub ignores patrol zone.SC1 in GIUK battleset from USSR side 2. Select sub group ZPU 3. Order sub group to detach the SSGN Echo from the group and only leave the Victor within the group 4. Run compression at high speed 5. You can see that the Victor has been assigned to the SE quadrant, but it never goes there. 6. The sub runs at 19kts to some imaginary point…

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: SAMs not firing Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: User Test: SAMs not firing.SCe Long Description: Able to fly Backfire strike right into a CVBG with no SAM fire encountered. Vikings with Sidewinders do fire along with AAA from ships, but SAMs will not fire until the Backfire launch first. ECM is not present and is thus not a factor. Sequence to reproduce: 1. Start SAMs not firing.hpe 2. Notice that Backfires are well within the SAM range ring and inside the formation without being engaged. 3. Formation air patrols and AAA will fire if the Backfire get close enough. Therefore, the AI kn…

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

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?