Page MenuHomeFeedback Tracker

Broken formation and behaviour
Closed, ResolvedPublic

Description

The spotting of an enemy or a firefight cause the AI team to split itself in 2 files for a time of about 280/300 seconds and the behaviour should be related.
The attached mission test:
After that AI group has killed the opfor man when the area is clear you'll notice that they walk in 2 files instead of a staggered column, to avoid this bug in the second waypoint I've inserted 300 seconds under waypoint timeout min mid and max, in fact I've discovered that this stop resets the AI formation(even behaviour?), otherwise you'll see the column moving in a strange way.
I hope this could help you to fix it soon
{F19663}

Details

Legacy ID
438334154
Severity
None
Resolution
Open
Reproducibility
Always
Category
AI Issues
Additional Information

the AI resets itself after 280/300 seconds, only if no enemies are spotted during this period of time if during the resetting you encounter another enemy the timeout will be cancelled and has to restart.

Event Timeline

Bogart edited Steps To Reproduce. (Show Details)May 30 2013, 6:52 PM
Bogart edited Additional Information. (Show Details)
Bogart set Category to AI Issues.
Bogart set Reproducibility to Always.
Bogart set Severity to None.
Bogart set Resolution to Open.
Bogart set Legacy ID to 438334154.May 7 2016, 2:21 PM
Bohemia added a subscriber: Bogart.May 30 2013, 6:52 PM
ceeeb added a subscriber: ceeeb.May 7 2016, 2:21 PM
ceeeb added a comment.Jun 6 2013, 1:40 AM

"Two files" is a staggered column.
When in safe mode, AI will always move in a single file column, ignoring whatever the group formation is currently set too.

Please see this thread, you'll find some pictures posted by Harzach that makes you better understand the problem http://forums.bistudio.com/showthread.php?155843-Formation-bug
The main issue is: ai takes too much time to be themselves oriented in the travel direction, 280/300 seconds.
Sorry for bad english

MadDogX added a subscriber: MadDogX.May 7 2016, 2:21 PM

Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.

If this issue is still relevant in current dev build, please re-post.