@RueLight its raining so smokescreens cant really build up

thrown just 4 smoke grenades for cover... ehmm yes... ai had good laugh.

1. already fixed.

Still no fix for this? We are coming up on 1 year and the new DLC is nice and all but useless if we can't use it.

I fixed it: https://www.youtube.com/watch?v=YMLc5hHC0tQ
Have a BI dev contact me and I'll walk him through the necessary changes. It's really very easy. It is not as performance friendly as I'd like (Only work is being done once at game start. no runtime difference)
but that's because of the decision to put the groups into the magazines array which wasn't mine.

Hello! I confirm it. Arma uses all my phys and pagefile memory, memsize flag does nothing.
Also my pagefile placed on ssd.
https://gyazo.com/a60cad483a8e8803455951d081e6014b

Hello! I confirm it. Arma uses all my phys and pagefile memory, memsize flag does nothing.
https://gyazo.com/a60cad483a8e8803455951d081e6014b

Just tested it. magazineGroup is working just fine in the backend.

Please delete this bug report.

Thanks @Lex, but if this mod completely disables the chat for ai-subordinates, then this is not suitable for me, because it deprives at least some feeling of realism.

There is a further issue of addAction not working when the player is >15 metres of object centre regardless of selection position and radius.
https://feedback.bistudio.com/T126959

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

Sorry i posted it Wrongfully

@Matosh Complete Arsenal rewrite.

In T126923#1649585, @dedmen wrote:

ACE3 to the rescue!

DayZ != Arma 3. No it won't be added to Arma 3.

It reads the servername and password from it so.... I'm quite confident it reads the config instead of my mind.

Tried it, but it makes no difference, unfortunately.

As happy as I am to finally have had something said about it, it took them far too long to even comment on it. Running a server is stressful as it is, chasing the producer of the game certainly doesn't help this.

Hi,
this crash should be fixed in next update of dev version on Steam.

We also have some more information regarding a BattlEye mass-kicking, which happened to some communities over these past few months. It seems we finally found a potential solution to this problem with our senior programming staff working on it as we speak. However, it might still take us some time, because the changes require low-level and potentially risky netcode changes. For this reason the implementation and testing needs to be handled with extreme care. It means we don't have a specific date yet, but we hope to release the change in one of the upcoming Main Branch updates. Please bear with us!

@Dwarden hey cucklord, any response?

I am using -config=serverconfig/server.cfg so it's in a subfolder. No problem here. Can you try if a subfolder works?

maybe one day

Soon™