Bug #23301

AI is unable to pointpoint sound source (well)

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

Status:Duplicate Start date:08/10/2011
Priority:Normal Due date:11/01/2011
Assignee:Dwarden % 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:OA only BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

Obs
1. When AI hears an unit fire a bullet for the first time (unit not known to the AI):

It notices the sound. However it estimates the threat position almost always quite off.
Both in distance and degree/angle.
Overall it unit is not directly visible and therefore the AI cannot see it even while turning,
it relies on a very wrong estimated position.

2. When the AI is already aware of the threat, it seems to no longer react to bullet fire at all.

You can fire from any position, angle and distance - as long as your are not visible to the AI,
it will not update the estimated position.

Exp
1. The AI, especially with 100% unit skills, should be able to pinpoint the source source a lot better.
Especially on close distance, but also in general.
As (good) (aware) player you can almost always estimate the direction and angle quite closely.

2. It should react to further bullet fire sound events after the unit has become known.

Note
These might be two different issues, but they seem closely connected.

Repro
  1. Launch the attached mission in the editor
  2. Lay down behind the metal tubes
  3. Fire a bullet north
  4. Your waypoint and the red sphere show the estimated position
  5. Notice how the AI assumes you south of the oiltower area or at times east of your position in the open
  1. Back to the editor
  2. Move yourself to the position of the disabled AI
  3. Fire a bullet again into the north
  4. The AI assumes now a given position
  5. Now move around the area without the AI seeing you or hearing your movement (when close use walk)
  6. Fire bullets and see the AI never updates your estimated position again

arma2oa_2011-08-10_12-12-53-85.jpg (153 kB) kju, 08/10/2011 10:31

AIunableToPinpointSoundSource.Desert_E.7z (1.6 kB) kju, 08/10/2011 10:31

23301.avi (9.3 MB) kju, 08/10/2011 10:51

AICombatScenario.utes.7z (1.3 kB) kju, 08/10/2011 11:57


Related issues

related to ARMA2 Community Issue Tracker - Bug #23300: AI can even hear slow movement Assigned 08/10/2011 11/01/2011
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 - Feature #23250: Generate DCFire danger FSM events also when the unit is i... Assigned 08/08/2011
related to ARMA2 Community Issue Tracker - Bug #23160: DCFire is added to the _queue of the danger FSM for sever... Closed 08/05/2011 12/01/2011
related to ARMA2 Community Issue Tracker - Bug #25544: AI infantry does not react properly on being under fire f... Assigned 10/16/2011 01/16/2012
related to ARMA2 Community Issue Tracker - Bug #23516: AI immediately tries to get into cover when first set to ... Assigned 08/16/2011
related to ARMA2 Community Issue Tracker - Bug #5785: AI view not obstructed by grass layer Closed 11/11/2009
duplicates ARMA2 Community Issue Tracker - Bug #28022: AI fixates on perceived source of gunshot, does not adjus... Assigned 01/20/2012
duplicated by ARMA2 Community Issue Tracker - Bug #31289: AI occasionally does not react to nearby impacts and enemy Duplicate 05/12/2012

History

Updated by kju over 3 years ago

Updated by kju over 3 years ago

One could assume it is related to the change of #23160 (no more DCFire when in danger mode).
From what I can tell it was even an issue already before that change.

Testing with 1.59 full shows that it was an issue before.

Updated by kju over 3 years ago

This more complex demo mission often show the problem too:

The AI gets under fire, even hit, while not having seen the threat.
It does not react to it nor does the bullet fire make it estimate
the threat's position.

One needs to run it a couple of times as it never plays exactly the same.
Use 4x acceleration and radio trigger for AI view (internal/gunner).

Updated by Fireball over 3 years ago

  • Status changed from New to Assigned

Updated by fabrizioT over 3 years ago

One could assume it is related to the change of #23160 (no more DCFire when in danger mode).
From what I can tell it was even an issue already before that chis issue ange.
Testing with 1.59 full shows that it was an issue before.

I recall this being a minor issue way before the build 83500 DCFire fixes.
After AI heard the first shot its detection of threat was usually quite off in terms or angle (don't know about distance).
That was a minor problem since further shots triggered more DCfire events and usually 2-3 heard shots were enough for AI to pinpoint even a far threat.
Speculation: Probably this is now a more serious issue since no further DCFire events are triggered after AI enters combat mode, not allowing it to improve its initial perception ?

Updated by Fireball over 3 years ago

  • Status changed from Assigned to Duplicate

Also available in: Atom PDF