Thanks for looking into it! :) Also got my new i5 6600k today, am really excited how many more fps it will get me than my old i7 2600k @ 4.5 GHz! :)

I experience this issue often. It's extremely frustrating and at times removes all sense of consistency from the game.

thank you for the feedback.

@Mrcreep24019, try verifying the integrity of the game cache and upload a troubleshooting report for the developers to see.

first of all please try to verify integrity of the game cache via Steam.
Steam > right-click Arma 3 > Properties > Local Files tab > Verify Integrity of Game Cache

thanks for the feedback.

thank you for the feedback.

Are you by any chance using AVG, or BitDefender antivirus software?

thank you for the feedback.

Project Argo works.

Somehow good suggestion, but reducing burtst size to 2-3 rounds will be perfect solution, so why select fix in 50% when we can choose 100% solution?

Would you mind to provide a video of the issue.

Hello,
sorry about the issue. Please try to restart your computer, Steam functions are not correctly initialized and they fail then Launcher uses them.

This was suppose to be in Project Argo, not ARMA 3. -_-

Demo mission:

My system:
Model : Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
Display device : GeForce GTX 1050 Ti on GP107-A GPU
Display driver : 375.70
BIOS : 86.07.22.00.30
GUID : VEN_10DE&DEV_1C82&SUBSYS_145419DA&REV_A1&BUS_1&DEV_0&FN_0
Multi-GPU role : master
Registry key : \Registry\Machine\System\CurrentControlSet\Control\Video\{665693EE-F90F-4D5A-8170-793112655296}\0000
VDDC controller : Display driver

"InventoryOpened" now returns second connected container

"InventoryOpened" now returns second connected container

"InventoryOpened" now returns second connected container

suggestion: Put a delay in the AI's retargeting procedure, so it keeps its crosshair on the target until a burst is complete. While this does not solve the "issue" (which comes due to the fact that AI bursts are implemented as long mechanical burst, which means all rounds will complete no matter what), it solves the issue of AI shooting unintentionally at friendlies or into the environment, after their target has been killed.

another issue that relates to "invulnerable" infantry / inconsistent damage to infantry comes from the way the dependencies in the hitpoint systems are defined. https://feedback.bistudio.com/T120765

The problem is with this:

Then decouple the updating from setHit and give us a script command that enforces an update to the hitpoints, so the hitpoints we read with getHit match the internal values, and also trigger hardcoded game functionality (death, handshaking, limping, vehicle engine damage, etc) in case a child hitpoint was damaged enough to trigger the parent.

Yeah I've tried many times with no results

Did you try disabling it then running the game?
All the users who reported that disabling the AV have worked also reported they did not have these issues before.

I use Avast and I've never had issues before

This should be resolved for a while, could you please give it a try and re-open this issue if that is not the case?
Thanks!

I am able to complete the main objective by destroying the truck at the first enemy compound then destroying the lighthouse. Would you be able to give it a try and re-open if that is not the case?
Thanks!

I am unable to repro this issue both on internal and default steam branch. Would you be able to give it another go by reverting campaign to this mission and report back?
Thanks!

While the syntax is not great, it's something we will have to live with.

You can also use

So only on dedicated server, not on direct. Will look into that some more but so far no luck :(

You will need to unlock it with the actual legacy branch beta password
In this case it would be
Arma3Legacy162

I'm pretty sure this is normal floating-point imprecision which can't really be fixed.
2.6 * 7 - 0.2 isn't exactly 18, but something a little less.

I went to change over to the legacy branch, but I don't even see the legacy branch as an option anymore?!

No problem!

Flying a jet around, got shot down, had a slow reload respawn, had a error text ingame, pressed F12 to screenshot, client crashed{F41436}

Even easier to call this bug this way and _very_ easy to replicate under any conditions. Arsenal is the culprit here.
Create a new backpack using this simple config;

Recreation, on a hill 800 meters away looking around with thermals on, alt+tab worked to resolve; 10sec came back no crash alt+tab worked again zoomed in again came back; got shot froze than taskmanager->quit->

The developer of a mission and the administrator of the server don't know how to resolve an issue with damage of the equipment from bushes.
Arma3 developers don't know how bushes receive properties not peculiar to bushes.
Control of a mission has no parameter - the level of damage of cars.
The mission (video of demonstration of a problem from a mission) doesn't reproduce a problem on a host server.
The mission reproduces a problem on the dedicated server.
Who can explain emergence of a problem on the dedicated server?

problem remains after verifying the cache.

Drats! That was simple. I'm annoyed I didn't think of that but that fixed the problem. It now opens correctly.

Are you by any chance using AVG, or BitDefender antivirus software?

Interesting, thank you very much for the heads up. Any chance you could find out what exactly seemed to be a problem for the bitdefender (which Arma 3 file or perhaps BattlEye file seemed to be causing the trouble)

Hello I tried to disabled every DLC, put once per once and nothing happend