Does this happen during a specific MP mission?

thank you for the feedback, we will look into this.

Unfortunately this seems to be an issue of the mod rather than the game.
You might need to contact the author of this mod to look into this

thank you for your feedback.

please try to provide your Troublshooting Report.

thank you for the feedback.

thank you for your feedback.

To learn more about the parameters, please check out this page
Arma 3 Startup Params

Could you please try to switch to the RC branch to see whether you will be experiencing the same issue?

Do you experience same issues when running vanilla (no mods) game?

Could you please upload the report files generated from running the RC branch?

Similar issue appeared in this ticket T123534
User was able to resolve the issue by deleting yourprofilename.vars.Arma3Profile
Before doing that, please backup the file first and only then remove it from your profile folder.

@Catsy Well the RC branch is a soon to be a stable version so it will soon be available as a normal branch update.

If you really don't feel like switching branches, even to a profiling (contains various performance and crash fixes but is still usable to play MP on stable/current main branch), than waiting for the new update it is I guess.

That is most odd, perhaps some unnoticed driver or OS updated that might have caused the issue, when the dumps you provided are properly processed by the devs we will know more.

Zues entity is a virtual entity, when simply said it's and invisible and invincible soldier, you can have the Zeus module set for regular unit but this way, you need to keep that unit from harm (which is not desired in some scenarios and is a more elegant solution than setting a unit to be invincible and stuck in some corner of a map).

Thank you for the feedback.

Basic setup in editor would go like this:

this is actually not a bug.

Similar issue appeared in this ticket T123534
User was able to resolve the issue by deleting yourprofilename.vars.Arma3Profile
Before doing that, please backup the file first and only then remove it from your profile folder.

I have checked the attached files but you uploaded only bidmp file, are rpt and mdmp also available?
If so, please upload them as well

Also, would you mind trying to switch to an RC version to see whether the situation gets better?
RC Branch
This version is soon-to-be Stable/Main branch and contains fixes that are going to be used in the next update. It also provides a x64 platform switch possibility that might help. Should you encounter same issue there, please provide your crashdumps from that version.

would you mind trying to switch to an RC version to see whether the situation gets better?
RC Branch
This version is soon-to-be Stable/Main branch and contains fixes that are going to be used in the next update. It also provides a x64 platform switch possibility that might help. Should you encounter same issue there, please provide your crashdumps from that version.

please try to unsubscribe all the mods you are currently using and verify integrity of the game cache.

Here is a reddit thread where a user was dealing with the similar issue
https://www.reddit.com/r/armadev/comments/3yg2i2/arma_3_unusual_exit_code_0x0000409c_status_stack/

@ARKAAZZ The dump gathering tool is actually part of the launcher, if the game crashes, it automatically offers to gather the dumps. Are you running the game with the launcher?

@SONAFBLUE twelve sounds about right, are there any mdmp and bidmp files present as well?

Thank you very much :)

Should be already fixed in Dev branch.

thank you for your feedback.

thank you for the feedback.

Thanks for the feedback, we will look into that

thank you for the info.

Please upload your crashdump files so we can look into those.

Yes but I guess you were not trying to run the game with only the integrated graphics running, so the GeForce one should have been initialized.

unfortunately in this case, the only thing we can advise is to try contacting a server admin of the KotH server you were playing on.

I suspected the issue might be somewhere else (drivers perhaps) as you are reporting a GT 750M however your RPT shows that game was detecting a Intel HD Graphics 4600

Should be fixed in the Dev already and also in RC/Main branch with the next update.

At the moment, he can't, that was just me thinking out loud :D

One thing could solve this, and that is if the Command Menu was not forced so player can disable it, that should be much better.

See alarms have been raised, but not sure if there is anything we might be able to do about this.

But it is not a bug, its how it works, the Command Menu has the focus of the scrolling, you wouldn't be able to zoom in and out them map if you have a subordinate selected and have the Command Menu open to give him an order.

Thank you for the info, should you come across something that might lead to some repro for this issue, please let me know :)

thank you for your feedback.

thank you for your feedback.

since the RC branch is currently available (branch that is soon to become a stable and contains various crash fixes), would you mind giving it a shot to see whether it gets better?

unfortunately communication with devs on this tracker is possible in only in English.
If you can, please translate your feedback into English.

thank you for the feedback.

this is actually not a bug, while not ideal, when you get inside the chopper you have to select the unload position through radio, so when you open the map, its the Command Menu that has focus of the scrolling not the map

thank you for the feedback.
Unfortunately I am unable to download the mission as the link seems to be expired.

thank you for the feedback.
The crash report you have uploaded however does not contain the crash report files but some custom scenario files.

Thank you very much :)

thanks for the info.

sorry for the trouble. This is most odd, we are testing the game on multiple NVIDIA cards, including the 1060, we have not encountered this issue however.

@DrSova Thanks for the heads up

Should be fixed in one of the next RC branch updates, and later in Stable/Main one.

In T123238#1574457, @DanielNL wrote:

3fps.txt54 KBDownload

Arma3Launcher_Log_20170214T155004_Daniel.zip1 MBDownload

In T123238#1574535, @nich10solo wrote:

Thanks, Razazel. If there's anything more specific that the devs need, let us know so we can try to get it. This bug has been like a plague to my group, pretty much making a lot of our play nights untenable, so we are all hands to try to get this fixed.

Please check out the latest Dev as the issue was fixed there.

The only thing I know is that number of possible culprits was narrowed down, my knowledge in this is unfortunately limited so that's as much as I could understand.

Thanks for the info :)

@Lex should be fixed one of the next Steam Dev updates (tommorow most likely) ;)

This issue should be already fixed in Dev branch and will be fixed in the upcoming Main/Stable branch update as well.

One important question for you guys.