Bug #2417

wounded AI gain a CONSTANT value of "knowledge" about shooter ignoring class, concealement, stance and weapon (+ Dead ai still gains knowasbout).

Added by fabrizioT almost 6 years ago. Updated over 5 years ago.

Status:Closed Start date:06/30/2009
Priority:Normal Due date:08/23/2009
Assignee:fabrizioT % Done:

0%

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

Description

REPRO

1) Load the attached mission

2) go prone, hide behind near bushes and hit the specnaz far in front of you. After you've hit him you'll see in the looping chat message that his knowsabout of you is raised to 1.5.

4) Restart mission, go very near to the victim (remaining undisclosed) and hit him from standing stance. After you've hit him you'll see his knowsabout of you is 1.5.

5) Test again, hit the victim from different stance / distance and with different weapons. Swap player unit class too. You will always see that knowsabout will raise to 1.4 or 1.5.

EXPECTED RESULT

An AI unit being hit should gain a degree of knowledge about the shooter strictly related to visibility and audibility, so in short knowsabout should not be constant: it should take in account at very least:

1) shooter visibility (shooter class, stance, concealement, movement, distance)

2) shooter audibility (shooter class, movement, weapon type)

SIDENOTE

While testing this i noticed another weird thing: a unit that is dead still gains knowledege (knowsabout) about the killer.
This is again a major issue, don't know if it's eventually related to: http://dev-heaven.net/issues/show/2067 or not.
Let me know if a different ticket is needed.

check_AI_hit_awareness_a.Chernarus.zip (1.5 kB) fabrizioT, 06/30/2009 16:56

check_AI_hit_awareness_b.Chernarus.zip (1.5 kB) fabrizioT, 07/10/2009 14:58


Related issues

related to ARMA2 Community Issue Tracker - Bug #2067: Killing a UNAWARE AI unit instantly gives knowledge of th... Closed 06/14/2009

History

Updated by kju almost 6 years ago

  • Status changed from New to Assigned
  • Priority changed from High to Normal

Updated by kju almost 6 years ago

Related to #2067 in the way of the new ticket Suma requested.

Updated by Suma almost 6 years ago

  • Status changed from Assigned to Feedback
  • Assignee set to fabrizioT

knowsAbout is not very good metrics of AI knowledge. The fact I am hit really gives me some knowledge there is some enemy around. It does not give me a lot of knowledge about type of enemy and almost no information about its position (other than it is probably somewhere close).

Therefore I cannot accept the fact "his knowsabout of you is 1.5" as a bug.

You should either check target information using nearTargets to demonstrate AI gets impossibly precise knowledge of the enemy, or show some behaviour which demonstrates this (like AI returning precision fire to player who hit him, without AI actually seeing the player)

Note: the issue described in sidenote about dead unit is exactly what should have already been fixed in the fix of #2067.

Updated by alef almost 6 years ago

For info: nearTargets was used in #1626 "AI Slow turning/ Slow Aiming".

Updated by alef almost 6 years ago

  • Due date set to 07/20/2009

Updated by fabrizioT almost 6 years ago

Ok thank you Suma, here you go:

Example of unaware AI unit returning precision fire on prone player, after being hit from behind by a single shot fired through a suppressed weapon from 150m ...

See attached mission.

REPRO

  • go prone (lower objects detail so grass won't clutter your view)
  • shoot some bullets in the sky just to be sure that the OPFOR "victim" that is 150m. in front of you CAN'T HEAR your gunfire ...
  • fire a sigle shot on him. Don't move, Stand still.

RESULT

  • 2 tries out of 3 in average the victim just turns 120-130° and fires on you. Notice how his perception of your position (= "NEARTARGETS" position ) is accurate.

MISC OBSERVATIONS:

Somebody will eventually say something like:

"maybe the victim is turning and looking in your GENERAL direction and then just spots you with his peripheral vision ...".

Ok let's check it out.
  • Just open the "main.sqf" file and add the line: "sleep(6); _victim lookAt position player;" just under the line reading "_victim setunitpos 'UP';".
  • Save and load the mission.
  • On load quickly go prone and then stay still.
  • Can the victim see you when turning and looking towards your exact position ? No (and this is by itself another strange issue!).

However, for the sake of our case, if enemy can't see you when looking towards your exact position then he won't be able to spot you when turning towards your "general" direction, right ?

So what is telling him where you exactly are ? How can he pinpoint you so easily ?

Updated by fabrizioT almost 6 years ago

Hi,

kju i gave feedback on this one, what i am supposed to do now ?
The only option i have as STATUS change is "Closed".
Or should i reassign the issue to somebody ?

Let me know, regards.

Updated by kju almost 6 years ago

Alef should set it back to assigned I think.
Or you become a CIT manager yourself and take care of it yourself. ;)

Updated by alef almost 6 years ago

  • Due date changed from 07/20/2009 to 10/13/2009
  • Status changed from Feedback to Assigned

Updated by Fireball almost 6 years ago

More evidence:

http://www.youtube.com/watch?v=8UzpTXZVKI8

Don't have a repro mission myself yet, this is out of the campaign. I think this is fairly easy to reproduce tho.

EDIT: pasted wrong link first

Updated by Squelch over 5 years ago

  • Due date changed from 10/13/2009 to 08/20/2009
  • Status changed from Assigned to Feedback

Addressed in 1.03 Fixed: Prevent killed AI units reporting who killed them.

Feedback please

Updated by alef over 5 years ago

  • Due date changed from 08/20/2009 to 08/23/2009
  • Status changed from Feedback to Resolved
  • Target version set to 1.03.58627

Tested with repro b. No issues.

Updated by Fireball over 5 years ago

  • Status changed from Resolved to Closed

Double confirmation and due date expired.

Also available in: Atom PDF