Bug #20462

Civilian FSMs issues

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

Status:Expired Start date:06/18/2011
Priority:Normal Due date:09/18/2011
Assignee:zGuba % Done:


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


There are two major issues with formationC and formationCDanger fsms:

1. They use setUnitPos command instead of setUnitPosWeak, making it impossible to control their stance with user scripts.
2. formationCDanger is executed in loop, making civilians do weird actions all the time they witness threat (like drivers getting out and back in the car).

1. Use two civilian teams. One with a car, the other on bare foot. Don't forget about neutral observer.
2. Set some visible threat to the car equipped team: OPFOR troops, APC or whatever that Civilian would like to shoot if it had any weapon.
3. Add init code

{_x setUnitPos "DOWN"} forEach (units group this)
to one of the other group members, and set move waypoint for it.
4. Observe the behaviour of civilians.

1. Car driver inspects threat and drives away with hurry.
2. Civilians crawl in the ground since they were ordered to do so.

1. Car driver does "stop - get out - inspect threat - get in - drive" for each threat witnessed (this occurs most frequently when mods are used, most notably in multiplayer mission Roadblock Duty http://forums.bistudio.com/showthread.php?t=115906&page=6)
2. Civilians ignore scripted command.

CIT_formationCDanger_weirdness.Takistan.7z - Repro mission (2.3 kB) zGuba, 06/19/2011 11:45

Related issues

related to ARMA2 Community Issue Tracker - Bug #20426: AI FSM performance and FSM defaulting/nesting Feedback 06/15/2011


Updated by zGuba almost 6 years ago

  • File CIT_formationCDanger_weirdness.Takistan.7z added
  • Due date changed from 06/20/2011 to 09/18/2011
  • Status changed from Feedback to Assigned
  • Assignee changed from zGuba to Dwarden
  • I am using some Mods changed from No to Yes
  • I am using set to CO (OA+A2)

Updated by zGuba almost 6 years ago

While repro is not very consistent due to the random nature of civilian AI and target detection, running it multiple times can expose potential causes of civilian AI breakdowns.

Updated by zGuba almost 6 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from Dwarden to zGuba

Must prepare better repro

Updated by zGuba over 5 years ago

  • Status changed from Feedback to Expired
  • Target version set to 1.60.87580

Seems to be partially improved in 1.60. I am not willing to investigate it further.

Updated by kju over 5 years ago

  • Target version deleted (1.60.87580)

Also available in: Atom PDF