Double-tapping LCtrl should exit the "Lower Weapon" stance.

However, I personally would like take this chance to request this mechanic to be removed. In my opinion it has no place in a competitive environment. On top of that lowering the weapon happens quite frequently triggered by certain movements, renders the player defenceless and can cause quite a bit of confusion especially for new players.

Well, thanks, I didn't go through all controls settings, maybe I tapped Ctrl twice when changing aiming mode or posture/stance. :-)
I agree this should be removed as it is useless in this type of game.

Happened again today (v0.69), double Ctrl didn't ready the gun...
https://youtu.be/8r6TWor3WNc

Sorry for the (Arma) mixup. Mouse1 will definitely get you out of the lower weapon stance. Source: I have to use it a couple of times every gaming session.

Again, for this reason I would like to see this mechanic to be removed, due to the fact that it does not serve any purpose in Argo and is way too easy to trigger.

Since the only respawning game mode (Link) is not available now and the other two have long game times, I have no additional info on this issue, it hasn't occurred like since christmass...

While I can't say anything about the specific occurrence Katoga's bug report is about, the Lower Weapon animation can still be triggered.

Video: https://www.youtube.com/watch?v=OTu3xEI14G8

Easiest way to reproduce (as shown in the video):

• Climb ladder
• Drop from ladder

However, this animation can be triggered by pretty much anything that makes your character drop. Random stones, rock cliffs, raised stairs (such as those shown in the last ~10 seconds of the video (Land_i_Stone_HouseSmall_V1_F)), destroyed walls (Land_City_8md_F, Land_Stone_8mD_F), etc.

Two more occurrences. One from a wooden footbridge (which proofs that the character don't necessarily need to drop (more of a geometry thing?)), one from a random stone.

Video: https://www.youtube.com/watch?v=7rEkO45hysA

Potentially. I probably should have opened a new ticket for this particular problem, but at that point in time I decided against it because both problems share the same root problem. I apologise for that.