" I have been unable to play the game for quite some time now."

Do you know which file has invalid format? I can't see that from the dwi.

Your ArmaReport_Log already contains crash dumps and RPT no need to upload duplicates.
Please don't put RPT content into your message.

A Ticket was created and we will see what the programmers can do about if it is indeed a problem in the game or somewhere else. It can take some time.

Darter and Tayran, military AR-2 UAV, should have NV on the pilot's camera. Ticket closed, the issue is not resolved. ???

In T126801#1648086, @Wulf wrote:

"OK, so I did over 100 tests I think"

And you managed to do it around 6x times If I counted correctly. We are aware of the problem, but it is really rare with no 100% repro.

I as well tried to recreate this issue but most of the time the vehicle either does not explode or explodes right away. So it is really tricky to trigger.

We might get to tweaking the AI, but I can't promise you anything.

Crate and Vehicle loadouts could be used for Zeus, so instead of spending 10 mins setting up a custom arsenal, just pop in, select a preset and load it. Same with vehicles(if the module ever exists to do so), that way the zeus won't have to manually swap stuff inside via proxy units.

"OK, so I did over 100 tests I think"

I was not able to reproduce the issues that you described could you please create a video of these issues and either upload it here or post a link with the video? Thank you. :)

I have the same issue DWI attached.

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

@Wulf Did you manage to check it?

Wipeout should be tougher than other planes and we were able to shoot them down with no problem. There is a slight issue that Wipeouts individual parts like the engine, controls etc. are more resistant than they should, but we will have a look at that.

Were Tan Combat Goggles intentional on Green balaclava? Since this wasn't fixed in previous patches.

Probably got fixed in one of the previous patches.

And it's problem not only with arma 3 .And same solution to other games.Thx

Thank you for the report we will have a look at the map. :)

Just before you open arma in steam, delete "GameOverlayRenderer64.dll" from steam directory.One way to start Arma 3 64 bit that i now know

The fix would be Steam fixing their GameOverlayRenderer64.dll. I didn't check if it got an update yet.
This is essentially a Steam Bug not Arma.

I see that in some of your rpts you have mods enabled normally disabling some of the mods should fix the issue however if the crash occurs even after disabling mods, you might want to look at this reddit thread where a user was dealing with a similar issue
https://www.reddit.com/r/armadev/comments/3yg2i2/arma_3_unusual_exit_code_0x0000409c_status_stack/

What are you doing when the crash occurs are you playing multiplayer or doing something else?

I fixed it by deleting the GameOverlayRenderer64.dll in the Steam folder, then creating an empty file with same name and making it read-only. That fixed this crash for me. This ticket is resolved.

Could you please send us your Arma report?

Does the issue still occur? Or were you able to fix it?

Send us your Arma report and we will have a look at it.

@shukari It seems that we are talking about different things. I do not see any relationship. I'm talking only about ability of interruption the treatment action.

This error is very generic. It may be caused by many issues, such as a hardware malfunction, a virus in the computer, but also an error in the game itself. Possible solutions:

That's alright. Main thing is that it works. :)

@tiagofmorais777 Don't post here. And upload your report log https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/
@AlcoNerd Your report doesn't contain any crashdumps. Do you still have the issue?

Hi, I wanted to check in as I have been unable to play the game for quite some time now.

hello, i heave this problem my arma3, status-acess-violation.

I'm still seeing the warning message in the arma3server*.rpt file as of version 1.76.142872.

disableChannels settings cease to work when leaving/rejoining mission in version 1.76.142872.

hm?

There are 0 crash dumps in your report. Your RPT says your game ran just fine today. And then suddenly stopped. As in being killed by Windows.

Real file is https://feedback.bistudio.com/F83540

Actually also quite easy to do. Because the textures are really just hiddenSelectionTextures usually.
The problem is detecting that an item has different variants. I guess you could go through every config class. And all items with the exact same model but different hiddenSelectionTextures...

Looks like steam overlay crash.

Your crash report is a empty 0 byte file.

Please use search before opening new issues.
Duplicate of https://feedback.bistudio.com/T126819

Guess this can be closed now thanks

FYI : I checked and the AI Skill level is set to 70 in my settings.

but thx!

steam make a new files in thit way :D

The problem is not Arma. It's Steam.
Steam will try to repair that file if it detects that it is missing. It is probably doing that while you start Arma. Even though overlay is disabled and it shouldn't do that Steam still does it.
They pushed a update to that file 3 days ago. Shortly before the crashes started to appear everywere.
you could create a dummy file with the same name and write-protect it so that Steam cannot overwrite it.

one thing.If i start the game with settings "start the game 32 bit" game will start well.What the problem can be with 64 bit version?

how can i disable overlay without delete or rename file(coz it is not work, if i make it right)?

Without the crash log your report is useless. https://feedback.bistudio.com/w/ft_a3_howto/general/ Please upload that file.

Steam overlay crash. Duplicate
https://feedback.bistudio.com/T126841
https://feedback.bistudio.com/T126847

Steam overlay crash. Duplicate
https://feedback.bistudio.com/T126841
https://feedback.bistudio.com/T126845

@stani Steam overlay is still active. And is still causing the crash. Disable Steam overlay. And delete the file like I said. Then try again.
@koriaba Exactly the same.

yep2{F83378}

yep{F83370}

Can you upload the Report for the new crash?

Nope.Still same error.

Confirmed. Delete/rename GameOverlayRenderer64.dll from Steam directory.

Upload crashdump: https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/ Otherwise this report is useless.