Defect Name: Double Dip

Build: HCE 2009.004

Repeatable: Yes

Operating System: Vista SP1

DB used: HCDB_080712

Scenario used: Saved game "Double Dip" for EC2003 GIUK

Long Description: ASA and WAD show up twice during the same attack.

 

Steps to reproduce:

1) Load and run saved game "Double Dip" in EC2003 GIUK.

2) Order Blue AEA to Attack Red ZXH. ASA asks if you want to attack. Answer Yes. (Screenshot: 01) In range)

3) The WAD allocates 2 AMRAAMs to target, leaving 2 on the racks. (Screenshot: 02) First WAD)

4) ASA says "The effective attack range fo these aircratf is 40NM. Target range is 38NM. Should we close and attack?". Answer Yes. (Screenshot: 03) SA again)

5) The WAD allocates 2 AMRAAMs to target, still leaving 2 on the racks. (Screenshot: 04) Second WAD)

6) AUD shows that Blue has no LR missiles left. (Screenshot: 05) Blue Atmament)

 

Expected Behavior: ASA and WAD should only appear for the original attack.

Observed behavior: ASA and WAD appear a second time, before original attack is completed; WAD miscounts the missiles available.

 

Additional information: This seems to have appeared with 2009.001.

Double_Dip.zip

Defect Name: Double Dip

Build: HCE 2009.004

Repeatable: Yes

Operating System: Vista SP1

DB used: HCDB_080712

Scenario used: Saved game "Double Dip" for EC2003 GIUK

Long Description: ASA and WAD show up twice during the same attack.

 

Steps to reproduce:

1) Load and run saved game "Double Dip" in EC2003 GIUK.

2) Order Blue AEA to Attack Red ZXH. ASA asks if you want to attack. Answer Yes. (Screenshot: 01) In range)

3) The WAD allocates 2 AMRAAMs to target, leaving 2 on the racks. (Screenshot: 02) First WAD)

4) ASA says "The effective attack range fo these aircratf is 40NM. Target range is 38NM. Should we close and attack?". Answer Yes. (Screenshot: 03) SA again)

5) The WAD allocates 2 AMRAAMs to target, still leaving 2 on the racks. (Screenshot: 04) Second WAD)

6) AUD shows that Blue has no LR missiles left. (Screenshot: 05) Blue Atmament)

 

Expected Behavior: ASA and WAD should only appear for the original attack.

Observed behavior: ASA and WAD appear a second time, before original attack is completed; WAD miscounts the missiles available.

 

Additional information: This seems to have appeared with 2009.001.

 

I ran this several times, with basically the following results.

 

After loading the saved game, the Blue A/C is carrying 2 AMRAAMs and 4 Pythons, indicating 2 AMRAAMs have been expended somewhere.

 

The helo is detected, followed by the usual Intercept Dialog, and is shot down using the 2 AMRAAMs.

 

A second Helo is then detected, and the Intercept Dialog plays out , folowed by the downing of the Helo by 2 Pythons.

 

If I load and run the Scenario from its start, the Blue A/C launches carrying 4 AMRAAMs and 4 Pythons.

 

Subsequent play is pretty much the same, except the 2 Helos are shot down using 2 AMRAAMs apiece.

 

A check of Game Status when the Saved Game is loaded indicates a Red Helo has been killed, which probably explains the 2 expended AMRAAMs.

 

I don't know if this helps or not, but it's what I have.

 

Buddha

I can confirm this one.

Are you confirming that it's broke or that it ain't broke?

Please re-test with 2009.007, the unwanted double-prompting should be gone.

The double prompting is indeed gone with .007. However, so is the Staff Assistant. The Attack order just results in a message "Closing to next AAM range" without the SA asking for confirmation.

That is the proper response according to an earlier defect workaround.

This would mean that Herman's Issue 41 in the issue (bug) tracker is a non-issue.

That's for discussion in the Issue Tracker then. fwiw I think his issue 41 is still valid since it is giving the closing message in the wrong situation (if I'm reading it all correctly).

fwiw I think his issue 41 is still valid since it is giving the closing message in the wrong situation (if I'm reading it all correctly).

You read it correctly and that is the reason why I posted it as a bug.