Hello, you might need to repair the game via Steam.
https://help.steampowered.com/en/faqs/view/0C48-FCBD-DA71-93EB
See Let us know if the issue still occurs after the repair.

Hello,
Your downloading an HTML file which automatically opens in browser if you try to open it.
Try right clicking the file and choosing save as/download or once your on the page press CTRL+S or right click to save the page.

Hello we went through your crashlogs and found that your crash is likely caused by another program:
ATOK32TIP!ATOK32TIP [fail:0]
No clue ATOK32TIP is, but try shutting it down before playing Arma and let us know if it resolves the issue.

The issue has happened again today.
Please investigate what happened.

Hello, are you using a USB headset? If so could you see if the issue also occurs with it unplugged/ swapped for a wired headset?

Thank you for taking your time to investigate.

• Here's everything we have at the moment (doesn't mean there were just this much crashes - previous dumps just got deleted), hope it could be useful

• We'll install prof/perf branch and gather more data, thank you

NOOOOOOOOOOOOOOOOOOOOOO

02-44-51 crash says out of memory
13-41-49 is... not sure. Something certainly went wrong there but I cannot see how. If you have more reports of the same crash they might have more info.
Also I'd recommend to run profiling/performance branch, they have lots of bug fixes and are also easier to analyze crashes for me

Checked on stable, works as expected (doesn't fire the EH on glass break)

Understood! Will adjust my missions accordingly, thank you!

It probably worked but not exactly as intended as you weren't able to adjust the score that way. It was always intended to be NAME of VARIABLE that holds the score. Not the score value, as per comment in config/wiki documentation.

Setting the cost_variable to "arty_score" and then adding "arty_score = 150;" to the init.sqf worked, before I was able to do it by just setting "arty_score" to "150" in the description.ext but I suppose that isn't possible anymore? Or else I was dreaming before..

Unable to reproduce the issue, make sure your variable contains number not some other type.

We are still experiencing this behaviour on latest development build. Seems like it has something to do with the updating frequency. Hopefully it's getting fixed soon, as this false behaviour exists since release.

Repair the game via Steam.
https://help.steampowered.com/en/faqs/view/0C48-FCBD-DA71-93EB

acil bakarmısınız hata çözümü bulamıyorum.

I'm running into the exact same issue when trying to host the server in a Docker environment.

This bug is not corrected.

As a workaround, running the Windows server in Wine works just fine.

This command is still broken. See KK's comment (2013!)

can be closed?

are BI missions/game modes still get fixed?

Yep, that did the trick! Thank you!!

I can't open gun 3 !!!!

When delay_max attribute is missing from the main config it defaults to 0, thus instant fire support. Add it with default value of 90 and it should work fine. I will try to fix it for our next update, sorry for the inconvenience.

Can confirm that adding the magazines directly using setPylonLoadout works perfectly fine but in the Master Arm module things gets iffy.

In T166456#2338036, @dedmen wrote:

yes it is, most likely wont fix

UPD: fixed on all branches since 149760

In T166554#2338485, @Bob_Murphy wrote:

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

The radio module is well outside my mission area. As you can see in the video, the rounds drop before the dialogue is finished. The code in the description.ext is the code from above, and it's worked just fine until yesterday. Opening a new mission and putting down a radio module and not customizing the description.ext in any way, of course, works perfectly.

Please note that these weapons have a melee mode as well.
So when no ammunition is visible, you are in that mode and can hit with the buttstock.
This is as designed. :)
Nevertheless, thank you for your ticket.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Please note that we are not in the position to fix issues with mods by 3rd parties.
Hence we unfortunately can not do anything about that.
Please contact the mod creators regarding that.
Thank you very much for your understanding.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Ok, I should i check that.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.

Duplicate of https://feedback.bistudio.com/T166565

I've noticed the same issue, the doors work fine on the UH-1B dustoff though

I've found the same. For me: zeroing the weapon to 300m gives a range of 100m, anything less than 300m and the round will drop short, potentially injuring the player.

Resolved how? It still happens