ARMA 2: OA 1.62 (Release Candidate #1) build 95168

[@ST]

You should´ve checked if it upgraded to RC 1.62 or just the beta 1.62;
in the latter case (which I think SU is upgrading to) it would´ve been sufficient to erase beta folder and install beta 94700 manually

[Xeno]

AT gunner just runs around Shilka not firing.

I've tried multiple times and not once the AT gunner was running around the Shilka and not firing (that was with 1.62 RC1).

Xeno

[metalcraze]

I've tried multiple times and not once the AT gunner was running around the Shilka and not firing (that was with 1.62 RC1).

Xeno

Did you order him to target and engage the shilka?
Because I have 1.62 RC1 installed (over 1.60) and then beta 95208 in addition to that and the behavior is just as awful as it was.

[colossus]

Can't reproduce this either. I used build 95208 (non-RC) with different factions and AT launcher types.
Vehicle is spotted, AI gets commanded to engage target, he pulls out his launcher, he goes backwards a few steps, then he fires.

I'll attempt the same with the RC version, but nothing would suggest it's any different. I'll check either way.

[metalcraze]

I dunno man. Here's the video I've made with 95208

http://www.youtube.com/watch?v=PTEOc...ature=youtu.be

[Danil-ch]

I got the same result as metalcraze. 95208

[Placebo]

???

Whats so hard to make a second copy of your ArmA II install and rename the directory to "ArmA II.160" before you apply any RC candidate? Thats how I do it.../KC

That's how I did it as well, except just moved it to a different hard drive

[colossus]

I still can't reproduce this. Neither with pure 1.62 RC#1, nor with 95208 included. If anything, it could be ArmA's infamous AI pathfinding at works. Which is rather Capt. Obvious, I guess.

[metalcraze]

I did a totally clean reinstall (as in deleted everything). Then installed beta 95208 over 1.60 (no RC).

The issue is still there. He still rans off without firing.

So I decided to launch ArmA2 vanilla (1.11). In ArmA2 vanilla AI behaves normally. Not as optimal as simply coming up to a tank without "engage" order - but correctly.

[colossus]

After a couple of more attempts, I've found it too. It's the pathfinding I think. The AI attempts to engage the target from the side you came from. If it fails, simply by not having a clear shot, it tries another direction - this time behind the vehicle. If that fails the AI will try to swim to the location where he would shoot the vehicle from the other side. The problem, I think, lies in that he doesn't recognize it's water.

It's a very hard location for the AI you've picked, though.

EDIT: FYI, this is not a beta problem. This actually exist in 1.60 too. And might I add: it's like I said, very hard location for the AI. Steep hill where you start, trees behind the tank, and a even steeper angle with rock objects on the right hand side of the vehicle, along with more rock objects in front of it.