Bug #23150

DCEnemyDetected is triggered multiple times per threat despite AI still in combat behavior

Added by kju over 3 years ago. Updated over 3 years ago.

Status:Expired Start date:08/05/2011
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:AI Issues
Target version:-
Affected ArmA II version:1.60 BETA First affected build:
Reproduced by another DH user:No First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

DCEnemyDetected (0)
The first enemy detected. Never generated again while already in Combat behaviour.

Note
The seen behavior might not be a bug. Maybe it is only a misunderstanding of the provided description.

Obs
The AI notices a threat and switches to combat behavior.
The AI can no longer see the threat after it has moved.
The AI now hears the same threat moving
(for the AI it could be a new/different threat though).

This triggers a new DCEnemyDetected event despite the AI
still being in combat behavior (as seen by its stance).

When the threat stops and moves again to generate a new
noise, a new DCEnemyDetected event is created each time for the AI.

Exp
As per the description I would expect max one DCEnemyDetected
event as long as the AI is in combat behavior.

Only once it leaves the combat behavior, a new threat is to trigger
a new one.

That said without this info from a behavior perspective the seen
behavior makes sense - each new threat first spotted triggers it.

Repro
  1. Load the addon along for danger FSM event analysis
  2. Load the attached demo mission in the editor
  3. Walk sideways to right side for the AI to see you
  4. Walk left again behind the wall so that the AI no longer sees you
  5. Stop your movement
  6. Now do a sidestep and notice a new DCEnemyDetected event getting triggered

The AI is considered as in combat behavior as long as it does not return
to the relaxed stance.

DCEnemyDetected.Desert_E.7z (693 Bytes) kju, 08/05/2011 15:19

danger_fsm_logger_by_kju.pbo (27.4 kB) kju, 08/05/2011 15:19

picture006.jpg (207.9 kB) kju, 08/05/2011 15:36

picture007.jpg (221.5 kB) kju, 08/05/2011 15:36

picture001.jpg (170 kB) kju, 08/05/2011 15:36

picture002.jpg (214.1 kB) kju, 08/05/2011 15:36

picture003.jpg (203.5 kB) kju, 08/05/2011 15:36

picture004.jpg (208.8 kB) kju, 08/05/2011 15:36

picture005.jpg (218.5 kB) kju, 08/05/2011 15:36

22935.utes.7z (1.3 kB) kju, 08/08/2011 08:08


Related issues

related to ARMA2 Community Issue Tracker - Feature #18956: Improve perceived position design for AI infantry Assigned 04/16/2011
related to ARMA2 Community Issue Tracker - Bug #23238: DCDeadBody can be triggered twice per body Assigned 08/08/2011 11/01/2011

History

Updated by kju over 3 years ago

Repro video: http://www.youtube.com/watch?v=zvdGgfpuv-I

Or see attached screenshots

Updated by Fireball over 3 years ago

  • Status changed from New to Assigned
  • Reproduced by another DH user changed from No to Yes

Updated by Fireball over 3 years ago

  • Reproduced by another DH user changed from Yes to No

Updated by kju over 3 years ago

Here is another demo mission.

The reasons here might be different, yet it shows also that the AI
identifies once threat multiple times via DCEnemyDetected.

Repro
  1. Load the addon along for danger FSM event analysis
  2. Run attached mission in the editor
  3. Follow the AI or use radio trigger ALPHA or BRAVO for AI view
  4. Notice how DCEnemyDetected is triggered several times per threat

Updated by Suma over 3 years ago

Now do a sidestep and notice a new DCEnemyDetected event getting triggered

Strange. I cannot see this problem on my end. To me the DCEnemyDetected is never sent again to the same unit unless I wait long enough for the enemy AI to stand up (return to Aware behaviour), which takes about 5 minutes.

Notes:
- Problem is not seen with 83496
- Problem confirmed with 83359

Updated by Suma over 3 years ago

  • Status changed from Assigned to Expired

The issue was caused by #23097

Still, the documentation of DCEnemyDetected is inaccurate and I am updating it - see http://community.bistudio.com/wiki/Arma_2:_FSM_Danger_Causes#DCEnemyDetected_.280.29.

I think once you read the new description it will be clear what was hapenning.

Updated by kju over 3 years ago

Thanks a lot!

Edit: confirmed fixed/working as expected now with 83500.

Also available in: Atom PDF