Revert or Restart seems not acceptable to me, although my problem was solved by this way, plz fix this.

Can confirm that this doesn't happen when slotting a Virtual Spectator slot from the lobby. @Wulf

Thank you for the report. Have you tried the possible solution posted here?

Latest RPT is available here

Unfortunately I don't have that RPT file anymore due to the automatic log rotation.

I'd like to point out again, that an exact description of the (likely) source of the bug is given in https://forums.bohemia.net/forums/topic/185591-end-game-spectator-feedback/?page=2&tab=comments#comment-3261564
and that ACE3 have fixed that exact same bug in their copy of the EG spectator system here a year ago: https://github.com/acemod/ACE3/pull/5868.

Gametag is meatwad8430

singleplayer,multiplayer have the same problem.

This should be fixed.

Did you play singleplayer or multiplayer when the crash occured?

Thank you for the report. Your upload lacks some files. Could you please upload your Arma report? Here is how to do that.

Thank you for the report. What exactly are you doing when the game crashes? Are you trying to play Singleplayer, Multiplayer, Editor?

@DarkElements Hello. Please create a separate report and upload your Arma report there.

Thank you for the report. These errors are usually raised when some DLLs are corrupted or missing or when they are replaced with an incompatible version. It may also happen that you placed a DLL file in the game folder that is loaded instead of the genuine one. Possible solutions:

I am glad that it has been 'fixed' for you. Since you whacked it, I would LIKE TO THINK it was defragment on your end. I know I keep my traditional HDD's defragged often like about every 3 months. As an IT tech with 35+ years of doing this for a career, I would HIGHLY recommend you do the same UNLESS you had a SSD, then do NOT defrag!

{F373189}same crash errorcode,no mod,Reproducibility 100%,After running for a while crash,graphics driver updated 3 versions,game reinstall 1 time,system:windows 10

Not really sure how to decode that log, but I can theorize that with a longer play session you could have had a memory leak, especially if there were periods of high intensity cpu usage.

I can also vouch that this sometimes happens where uniforms disappear randomly. Sometimes its getting in and out of vehicles, sometimes its when someone is in an arsenal, and sometimes its when someone get something in their inventory via a scripted method such as an exile shop.

Thanks z80cpu but before I saw this I decided screw it im wiping my hard drive, so I did. Now it works. Not really sure what the actual solution was but that was one.

As someone who has had this before, read and TRY my 'work-around'. It typically DOES WORK!

is there any way of solving this issue as im having it now and its is a pain in the rear

Here is the latest report from the game crashing after I updates my motherboard bios. Also I am able to change the graphic settings.

Realized this is a duplicate of T83382

@Alwin I take it this isn't going to ever be implemented? Would be quite useful for a lot of mods. CBA managed to find a workaround but there are other mods that aren't able to assign mouse buttons as inputs.

grrrr also happens on spawned AI if they spawned on clients in dedicated environment.... i hate arma updates!

It is Singleplayer missions. Any mission that I try it crashes a few minutes in or crashed when it’s starting up the mission. Also freezes when ever I try to change the graphic settings.

Im short on time today but tomorrow I will reproduce the issue and get logs/try to find all the logs that represent this issue.

I noticed some old threads from 2016 that seemed to have a similar issue.
https://feedback.bistudio.com/T120817
https://feedback.bistudio.com/T66415

Sorry if this was a little hard to follow, there is just so much about this kicking issue and I was pulling fragments of information from my mind from different times, so it was as disorganized as it was in my head.

I would appreciate this too, having the event fire even when the link is not valid would be perfect for triggering other scripted events from custom dialog or htmlLoad.

Does nobody on the development team care in the slightest that this bug, which could probably be quite easily fixed, completely ruins scripted sound effects?

still not fixed :I

Thank you for the report. We will have a look at it. But from what I can tell it seems that there is some audio problem, we will see.

Thank you for the report. Which mission are you refering to? Is it a Singleplayer mission in the campaign or a Multiplayer mission. Please let us know.

It is not suppose to. I am quoting this from the Forums for the dev branch

Thank you for the confirmation we will have a look at it.

Thank you for the report. Please upload your Arma report here. Here is how to do that.

In T131963#1740405, @Wulf wrote:

Hello.

Does this happen even without mods/with mods disabled?

Thanks :)

I think I fix it myself; but I want to test it for a few days.
I uninstalled the game and re-installed it and now it works. (in the 2 games I have been in, it worked)
It may have been something in the script of the updates which didn't mesh with the original programs or updates.
Uninstalling allowed the program to pull and place items in order to allow the "Tanoa" map to load.
Just a guess, but I know of many others who have the same problem.
But, thank you for your time and efforts on the problem mate.
Cheers
Greg Fincher
aka- Gijoe 1LD

Thanks for the pointer. It's an absurd exception, flying in the face of KK's prior comment, but after two years of constant development with this mess I've come to expect so little from SQF that such an exception seems to comfort me in some strange way.

try like this

Probably an initialization sequence where 0 == 0
See: https://community.bistudio.com/wiki/Initialization_Order

Thank you for the report. Regarding the Mk41 not working with the artillery module, that is intended. It is controlled via a UAV terminal.

This should be fixed in the next update, you can check out the fix in our Dev Branch build.