HarPlonkHQ

Defect Name: VLow SAMs intercept VHigh
Build: HCE 2009.042
Repeatable: Y
Operating System: XP
DB used: HCDB-100308
Scenario used: VLow SAMs intercept VHigh.SCq
Long Description: ManPAD SAMs with low level ceiling are launch against aircraft at VHigh while they are crossing targets

Sequence to reproduce:
1. Run VLow SAMs intercept VHigh.SCq with Show All enabled
2. Launch Foxbat and have it buzz the ManPADS site back and forth slowly at 1:1 compression
3. SA-7b will launch and try to intercept
4. VLow SAMs intercept VHigh.gif

Expected behaviour: Weapons restricted to low level targets should not launch against VHigh targets
Observed behaviour: Weapons restricted to low level targets launch against VHigh targets

Defect Name: ASW ring does not sprint
Build: HCE 2009.036
Repeatable: Y
Operating System: XP
DB used: HCDB-100308
Scenario used: ASW ring does not sprint.SCq
Long Description: Units postioned in the ASW ring of the formation will sprint/drift when they arrive, but will eventually move only at the speed of the formation

Sequence to reproduce:
1. Run ASW ring does not sprint.SCq as Blue
2. Order FF Type 23 CUP to a different ASW patrol position
3. Plot long path for group
4. Once ship arrives, it will sprint/drift for a few evolutions, but will eventually move only at the speed of the formation

Expected behaviour: Units in ASW patrol ring should sprint/drift
Observed behaviour: Units in ASW patrol ring do not sprint/drift

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

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.

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 group.
Observed behaviour: Improper new group formed from survivors of destroyed base group.

This report is very likely related to other reports regarding the inability to attack damaged units.

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

Defect Name: Keyboard commands missing
Build: HCE 2007.000
Repeatable: Y
Operating System: XP
DB used: HCDB-070524
Scenario used: any
Long Description: Many keyboard commands listed in either the in-game help function for GE, the in-game help function for SE, or the manual are missing.

Also, the keyboard commands listed in the manual do not correspond with the ones available from the in-game help function.

Alt+A in SE does not match described function
Alt+___ Special Key commands listed under 15.8 do not function in the SE
Alt+t listed on GE help function does not work
Alt+u listed on SE help function does not work

MarkShot (a.k.a. Mark Kratzer) noticed one anomaly and initiated this process of discovery.

Sequence to reproduce:
1. n/a

Expected behaviour: All keyboard commands should be present and match the manual listings.
Observed behaviour: Keyboard commands are missing and do not match the manual listings.

Defect Name: Launch Limbo [2006]
Build:
Build: HCE 2007.000
Repeatable: Y
Operating System: XP
DB used: HCDB-071223
Scenario used: Launch Limbo [2006].hpo

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.

Defect Name: Missile turns away
Build: HCE 2007.000
Repeatable: Y
Operating System: XP
DB used: HCDB-070524
Scenario used: Saved game: Missile turns away
Long Description: Incoming Phoenix missile turns away on final approach to target.

Sequence to reproduce:
1. Run saved game at 1:5 compression
2. Watch missile approach target yet turn in opposite direct just before it runs out of fuel

Expected behaviour: Missile should continue towards target
Observed behaviour: Missile turns away from target

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.

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
4. Hit Formation editor.
5. Re-order Storm into it's zone (marked in Yellow).
6. Do NOT issue formation orders for any other ships.

Patrol zones centred on wrong position [assigned-again].gif

7. Run at high compression.
8. Storm races ahead and 'out' of the formation.

Patrol zones centred on wrong position - Storm races ahead.gif

Expected behaviour: Ship should move to assigned patrol zone relative to formation
Observed behaviour: Ship do not move to assigned patrol zone relative to formation

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

5. Ships are not in the centre of their assigned zones.

Expected behaviour: Ships should move to their assigned patrol zones
Observed behaviour: Ships do not move to assigned patrol zones

Defect Name: Shot down during landing
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 reproduce:
1. N/A - saved game available.

Expected behaviour: Aircraft already landed should be re-armed and available to player/AI.
Observed behaviour: Aircraft, already landed, are stranded in the Landing Pattern [limbo] if the last aircraft in the group is destroyed.

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 longer be selected for ViConds

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 to the SW. The group icon and the unit icon do not match and get further and further away from one another.
7. Select the Victor in the Unit display window and enable the "Lock" box and watch as the unit display pulls away from the group icon.

Expected behaviour: Unit should move to assigned formation patrol zone.
Observed behaviour: Unit does not move to assigned formation patrol zone.