Tracers have a burn out time, they don't stay lit forever. I don't know what values would be correct, however.

And yet ...

Brand new PC with a 7800x3d, 32gb ram, 5070 Ti card and I am having this same problem. Game becomes absolutely unplayable after 20 minutes or so.

Just experienced this bug again on vanilla

I reuploaded the video clips to use H.264 codec instead of H.265 because I realize its support is very limited even on modern browsers, so my apologies if they weren't previously watchable on your browser. Please let me know if anyone has issues with viewing the videos.

Resolved for one of the future updates

Hello,
this has been resolved internally and will be changed for future updates.
Regards,
Geez

The same situation also occurs in extreme off-road driving and collisions with obstacles.

Had this happen again yesterday. New round of Confict, literally 2nd base captured, placed 5 machinegunner groups, 0 soldiers appeared, 100% of limit used up! Wish I recorded that.

@JimBeam
There are 3 or more posts on the RPG spam already. You don't need to dedicate your spare time worrying about it.

Wanna bet 99,999% of those kills is RPG?

Not to mention it's insane how accurate it is!

rpgs have a minimum arm distance, you are too close to the wall

This issue needs to be assigned. I have sent dozens of FULL logs to you about this crash.

Nitrado doesn’t know what they are doing.

I want to add to this… mainly because I can’t create a new inquiry. I saw this and thought it was related to server performance. I saw some ramblings that Arma was running on Nitrado, and finally did an IP lookup and confirmed that indeed official servers are running on Nitrado. (at least some of them).

I tried to repro it myself by forcing packet loss but couldn't. Just had this happen again but I had very stable connection, group placed, no soldiers appeared, limit used up. No idea how, but the bug is indeed there.

I was able to reproduce the RPG bug on vanilla, please see attached.

Confirmed fixed in last stable

Nice thx,

Did you check Options -> Controllers -> Head tracking - Sensitivity. The sensitivity scaling seems to be set wrong (or at least weirdly), you need to set it 10x the value for it to read right.

So bottom line even developpers have no idea what the hell these errors are, we are just pushing all the buttons and wonder if something works. I got one more bullet left. Im gonna hard format my pc and try again. If it wont work, i have to request a refund and write a negative review, farewell my good sirs.

Correction to the previous one, its working on 1.4.0.45, but not good as at Experimental version (the head tracking is allmost unnoticed)

why cant you switch gunner seats in mi8 when on xbox legacy controls? when you try to switch it snaps player view back to front.

Ohh sorry i thought these were battleeye errors

What violation does battleye see? can you send a screenshot?

Hello.
Unfortunately there is not much else we can suggest. The issue does not appear to be with game code or the engine.
The last thing you could try to do is disable your antivirus software though we believe it will probably not make a difference.
Regards,
Geez

It has to be with game code or the engine, i completely cleared my pc, there is nothing left, only microsoft software but i presume battleeye is catching something from original microsoft files or services, do these error codes mean nothing? Also i already disabled all security softwares.