User Details
- User Since
- May 28 2013, 2:21 AM (609 w, 2 d)
May 10 2016
Now that I think of it, I only had one unit left also. It happened all the time becuase I had 3 playables, and I usually switched late in battle leaving the other one dead and one left. That would also explain why it sometimes worked. Thanks EDcase.
Thanks supercereal I appreciate the info. I will close the thread.
A tank!? That's awesome. But even with other less powerful guns it seems as if they just fainted except it lasts forever. Im not too familiar with this engines capabilities, but I have modded bullet impact force in other games just for laughs, and in most cases it is fairly simple. But like I said, I don't know if that's the case for ArmA.
Yes, I was talking about the .50 cal. I can understand that it would move through a guy like butter but the other guns have the same problem.
@plutoto74 - I don't think its used, but it is technically possible. ArmA 3 does take place in the near future, so its not out of the question entirely.
@AD2001 - The smoke charges would be used if you didn't want to make a big scene with you as the immediate suspect. You could wait for the helicopter to gain altitude before setting off the charges to buy some time before they realize they were attacked. Or, with other vehicles, maybe you want the vehicle in working order to use for yourself.
Ok, I uploaded two more pictures. The ones I uploaded are from the first time it happened, before I duplicated.
Ok. It only seems to be a problem with the new ones. The MH-9 and all of the old ones appear to be okay. If anyone else finds different, then by all means say something.
Ok, I will try some more.
Not sure that it matters, I am using Windows 7, not Vista.
Here is a video of the civilian Quadski:
It's not lag. I have always played with settings maxed out and never had any problems. It only happened that once and it's never happened since.
No, sorry. I don't have any idea what would've caused it.
If it helps any, I was on the airport runway, close to the end of the north end when it happened.
May 9 2016
I just had the same thing happen to me. Playing on the .58 update.