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.

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

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

Yep, that did the trick! Thank you!!

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 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.

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.

What's your module editor setup?

Bumping as this is still an issue

Hey Neuromancer,
Thank you again for the feedback.

Hi!!
I have made some more tests to try to help you with the diagnosis.
Please have in mind you have to be very patient to reproduce it. 90% of the time everything goes well, and then it happens. Sometimes it happens the first time you touchdown, sometimes it takes 30 minutes and dozens of touchdowns to see it happen.
I have spent more than one hour testing the helicopter in different terrains, and I have managed to see it happen in Gia Lam airbase (Cam Lao Nam), in the Altis airport, and in Tanoa. When in Tanoa, it happened on grass terrain.
So it doesn´t seem to depend on the type of terrain or the scenario. I would say it´s the helicopter itself.

Hello Georg,

Hello Nivek,

Hello Nivek,

due to our team not being able to reproduce this issue, we will close this ticket.
It seems to be the "typical Arma case" in which a killed AI ragdolls into an object and then knocking it over.
If you have additional information and/or in the unfortunate event that (part of) the issue persists, please open a new ticket and include a link to this one.

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.

due to not being able to reproduce this issue, we will close this ticket.
If you have additional information and/or in the unfortunate event that (part of) the issue persists, please open a new ticket and include a link to this one.