The command sets combat mode for a group, not individual AI units.
https://community.bistudio.com/wiki/combatMode

This is the intended behaviour. See orange note box at https://community.bistudio.com/wiki/lineIntersectsSurfaces

2019... still having this issue... can you please, please address this? add a delay to it or something, please...

Hello, wanted to ask if you have already recognized something?

hey, first of all thank you very much for your reply.

Hello, please try to go through the steps described here

Hello, would you mind to provide some repro steps to achieve this error message?

I see, your first comment mentioning it's happening in both SP and MP confused me. It could have helped as so far we have reports only from MP that we are not able to reproduce ourselves :(

Can someone please take a look at this?

In T146563#1982920, @razazel wrote:

does this for both SP

Do you by any chance have a SP mission where this issue is easy to reproduce ?

does this for both SP

Hello, are you having trouble while trying to run the game without the mod?

Why is there still no resolution to this 5 years later. Even with Tanks DLC there's no improvement. What the heck Bohemia.

I run 32Bit because the game literally freezes up and sound artifacts occur if i run 64Bit and it's been this way for 2 years now. Which i can't have if im flying in the air and it starts to artifact and freeze up, does this for both SP and MP.

I have tried pretty much all of them so far, no dice. I'd also like to point out I'm not getting this sort of problem with any other game, not sure if that helps narrow down the problems

In T146487#1981920, @razazel wrote:

Hello, does this happen even when running game without any mods ?

Hey, thanks for the suggestion. But it still does not work :( Several new installations of Visual C ++ 2013 and DirectX already tried, server still does not start! What strikes me is this message "unable to get DLC data" once the 3 and 22 Maybe it's because in the 32-bit version, this error does not occur! Of course I can be wrong ..... Attached a log of DirectX (Dedicated Root Server) With best regards{F1356033}

Hello, does this happen even when running game without any mods ?

Hello, please try to go through these suggested steps. Should any of them help, please let me know.

Hello, try to go through these and let me know whether any of them have helped.

I can't check -bepath, but I'm gonna assume thats solved and we can just close this ticket now @Astaroth

Hello, would you mind uploading the RPT as well? Thank you

And fixed in 1.96 hotfix 1.96.146.114
Please don't let it come back until I get my own hands on that ^^

Signatures issue is now fixed

parseSimpleArray fix is confirmed.
boxtruck fix I confirmed last RC.
memory leak fix confirmed (I'll fix that properly once I get my new job :D)
non ascii characters in pbo names confirmed fixed, but only tested on windows client, not on Linux server.

Hello, thank you for the ticket.

Hello, we've updated RC branch just recently and a fix for this should be in, could anyone please confirm ? Thank you

Will be fixed once Stable branch is hotfixed

Assigned to none. This "guy" is the greatest worker at BI. Not very efficient, but so busy. Permanent employee of the month.

Same error here.

@Astaroth, it's resolved (see screenshot).
https://i.imgur.com/pZrad0K.jpg

update, doing it in 32 bit now. going to do a reinstall again. hopefully 4th time is the charm

Hello Bohemia? is there a possibility to change the color? because by changing the setGroupIconParams the color of the hexagon does not change at all? Any suggestions so far? Or do i have to disable the inbuild indicators and build it myself to get the color changed?

Seems to be fixed on RC. Confirm?

So it's 2019 and this request from 2013/2015 is still relevant.
This should still be a consideration for implementation in my opinion as milsim and vanilla players alike would benefit from this like crazy.
It's somewhat annoying if I'm honest that an Alien DLC takes precedent over something so small but yet so big for the wider community, this feature would effect how people interact with your product ArmA 3 for the better and I think it's crazy that feedback that goes as far back as 2013 when the game was in Alpha still is overlooked.

It has pretty much been confirmed that this bug is caused by having your original TeamLeader killed before the shooting range is secured. The next-in-line TL managed to inherit the waypoints leading to the final extraction point but only the original TL can trigger the AAF reinforcement event.

startLoadingScreen does that.

Yes except that we can't tell it how much time the scheduler now has for each frame, it's fixed at 50ms which is too much. Also it's not a valid solution for clients with interface.

startLoadingScreen does that.
Cannot really do this. We can't just have a script command that lower fps for everyone.

Hi,
thanks for the report. We will look on it.

Could you please attach your logs?
Guide how to do it is here: https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/

Please make ipv6 happen.