In T165117#2315512, @LSValmont wrote:

In T165117#2314845, @Leopard20 wrote:

In T165117#2314110, @LSValmont wrote:

Having this would be awesome, another one is "[Feature Request] Forcing unit ragdoll despite it is playing an animation". You know when a unit playing a custom animation gets shot and killed but he still plays the animation even thou it is already dead.

That's related to poor animation setup. It's not a game bug. Whoever made the animation can fix it themselves.

It is the default BIS animations, for example "Acts_CrouchingCoveringRifle01":

[_flashBangVictim,"Acts_CrouchingCoveringRifle01"]remoteExec["switchMove",0,true];

If the Ai unit is killed before the the animation is done then it will just continue playing the animation as if it was alive.
To prevent this you need to add a MPKilled EH with "_unit switchMove "";" (No need to remote exec this time because MPKilled runs on all clients.

It is weird that a "Killed" event doesn't just over ride all and any animation the unit is playing at the moment and just goes into ragdoll like any other game.

In T165117#2314110, @LSValmont wrote:

Having this would be awesome, another one is "[Feature Request] Forcing unit ragdoll despite it is playing an animation". You know when a unit playing a custom animation gets shot and killed but he still plays the animation even thou it is already dead.

In T164521#2307664, @BIS_fnc_KK wrote:

An alternate syntax for the existing allGroups

not possible, nulars can have only 1 syntax

Mission is unavailable

Sorry. Uploaded the mission on FT.

In T164321#2300081, @AMark wrote:

I didn't see anything on that page that can help.

So did you make sure you have installed DirectX 11 and VC++ 2013 Redist packages, and verified the game data via Steam?

Where could I find a list of all the required drivers?

You just need the normal drivers needed for running a game. The GPU and Audio drivers are probably all you need.

Your new Windows is probably missing some software needed to launch the game.
Make sure you have installed all drivers (GPU, etc.), DirectX and VC++ 2013 Redist package.

In T164110#2296504, @dedmen wrote:

That's behavior not combat mode...

Not in engine.

In T164110#2296495, @dedmen wrote:

It only triggers if the Combat Mode changes automatically. It doesn't trigger if you do it via commanding menu or scripting commands (e.g grp setCombatMode "BLUE" or grp setCombatMode "RED" doesn't trigger)

setCombatMode doesn't set the combat mode, it sets the "Semaphore"
CombatMode is combatBehaviour/setCombatBehaviour/setBehaviourStrong command

This is so confusing....

Cannot reproduce in vanilla. You're probably using a mod that breaks it.

In T164086#2294737, @LSValmont wrote:

Resolved, or wontResolve?

You can't close it yourself. It will be closed by the devs once the bug is fixed.

In T164024#2293268, @TokyoCowboy wrote:

Sorry, this seems to be a CBA issue.

In T151907#2292766, @dedmen wrote:

If added, diag_getTerrainGrid should be removed

Your game/OS data might be corrupted. Try the potential solutions mentioned here:
https://community.bistudio.com/wiki/Arma_3:_Unusual_process_exit

Shameless bump. I also remade and reworded the ticket entirely.

@simao1234
Read this page.
https://community.bistudio.com/wiki/Arma_3:_Steam_Branches
The code for legacy 2.06 is: Arma3Legacy206

What is the problem? Your rpt (log files) are from several months ago, and there's no error or anything relevant in them.

And direction going precisely up/down together with normal up vector just doesn't work.

What if you simply do something like:

if (dir.x == 0 && dir.y == 0) {
   up = {1,0,0};
}

? Does changing the up manually not fix it?

Duplicate of T154293