i noticed that when AI are NOT in combat, the AI hardly move and this makes stealth missions LONG! lol
Description
Details
- Legacy ID
- 821403302
- Severity
- None
- Resolution
- Open
- Reproducibility
- Random
- Category
- AI Control / Commanding
go to editor
place a group (F2)
make waypoint 700 odd meters away on STEALTH mode
most of the time the AI hardly moves except stay prone
try and be squad leader
even if it was imoplemented WITHIN the stealth combat mode so when the AI were not in combat they would speed up a tiny knotch and when in combat they would be more stealthy like :)
Event Timeline
But that would negate the STEALTH bit. If you want to move faster just issue them to be 'Aware' or 'Combat', move the desired distance, and reissue the 'Stealth'. Wont that do the same thing?
but what if you needed to whisper?
either way it would be used quite alot regardless :)
i think it would be useful even if the AI knew when to pick up the pace but still have that stealthy actions and sounds...
This ticket would make more sense:
http://feedback.arma3.com/view.php?id=11521
It's about giving the order "loud or silent". This way you could continue to use "aware", "combat" etc. Otherwise I would second what KardasLT wrote. Set to "hold fire" and "aware".
What's the use? They made the 'Combat' mode, which is more like 'Please-Get-Shot' mode. Then there's Stealth mode which is just makes AI crawl or STAND UP AND RUN AND GET US ALL SHOT.
Now they're gonna make another AI behavior that magically works?
The use is to improve the game. It's in beta, it's not going to be perfect. It's the communities job to find and report these problems
OHHHHHH it's in beta! Thanks for clearing that up for me :P
I was having flashbacks to the last game that wasn't in beta and had these same issues - you know the ones you just found...
But maybe I'm missing the point. I'm just trying to think of a time where the AI needs to be both in STEALTH and COMBAT mode. Because I think of stealth as trying not be detected at all.
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.