Detecting when a trigger is pulled on an empty chamber

[Tyger]

I'm making a mission replicating a standard FTX (Field Training Excercise).

During FTXs, we are generally issued 2 magazines of blanks, and after we have expended them, we must yell "bang bang bang" to replicate small arms fire. Sparing no expense, I am attempting to replicate this.

As I expected, the "fired" event handler doesn't trip when the magazine is empty and the trigger is pulled. So my question is, is there a method I can use to detect if the player fired and the magazine was empty?

[JasonO]

Once the magazine is empty, its deleted from the player as if he drops it. Therefore if he has no ammo, he has no magazines?

Maybe doing a check to see if the player has any magazines. This is in the COMREF:

Code: [Select]

("_x == {M16}" count magazines soldier1)

[paddy]

Hmm, i'm not sure how feasable this is but you could give it a go ...

Obviously the player has run out of ammo when the 'needLoad' command reaches a certain value (i'm assuming 1, not tested that yet though).
How about whenever the player has run out of ammo creating a dialog with a button that covers the whole screen but is invisible, i.e. has a 0 alpha component?  This way when the user clicks again he will hit the button and this can trigger your 'bang bang bang' sound.  Obviously the player will have to have the ability to reload disabled until they click the button and you can code the dialog so that if it's closed by Esc it will automatically reload etc etc.   

[Tyger]

@JasonO
Thanks for the reply, but the trick is detecting when the player has clicked the mouse button to fire. Therefore, I can't use your solution unless there is a way to map which mouse button was clicked.

@paddy
Is it possible to still turn and move with a dialog up? That would be the only limitation to the dialog portion.

[paddy]

Is it possible to still turn and move with a dialog up? That would be the only limitation to the dialog portion.

Yes, that is a limitation but surely the player is supposed to shout before they do anything else?  I know its a crappy workaround but I think unless you want to just have a 'round counter' variable that counts to 30 and then spits out a bang bang bang msg thats all I can think of.
Probably okay cause its just a training mission, wouldnt really work on a real-time mission, having your squad shout 'bang bang bang' MIGHT give away their pos in rl lol. 

Be interested to see if anyone can think of anything snazzier, maybe some kind of addon with a '31st round' type thing, but then thats an addon and this is a scripting forum  .

Lookin 4ward to hearing what you go for.

[Cheetah]

I think that there are certain commands that enable you to detect when a specific button has been pressed. Can't find the command, but I recall that mandoble uses this for his Missile Suite (could be wrong).

Where he detects if buttons like 'A' and 'E' have been pressed. As far as I know this is possible.

As a start, you could take a look at actionKeys.

EDIT:

it has to do with finding the correct key (keyName) and then checking if it's active / has been pressed I guess..

[JasonO]

http://www.ofpec.com/COMREF/index.php?action=list&game=All&letter=d#displaySetEventHandler

I believe its displaySetEventHandler

[paddy]

@ Cheetah & JasonO
Yes, I know this is possible, i've used it before.  Originally I think either Vektorbosen or UNN discovered that one, it was in OFP and didnt use actionkeys of displaysetEH because those are ArmA commands!!!  However Tyger asked is there any way to detect if a unit fires with no round in the chamber, i assumed he was using the mouse (most people do, ctrl is a little awkward in fps) and neither of these commands work with a mouseclick, or do they??

Still, yet asnother unsolved ArmA scripting issue, you mission gentlemen .. should you choose to accept it ...

N.B. Im waiting for my new comp, I cant run ArmA yet  , else I would test this myself

[dmakatra]

I'd add an option in the action menu. After all, it'd be more real since in reality shouting and shooting isn't exactly the same action. But that's just me.

[Tyger]

Thanks for the comments mates. I'll take a look at the displaySetEventHandler and see if I can dig the mouse out of that one.

[Mr.Peanut]

The problem is that the displaySet eventhandlers only detect which keys (or mouse button?) are pressed, not how the player has mapped them. There is no guarantee that each player has mapped his controls the same.  It is a real shortcoming that you can not detect how a player has mapped his keyboard/controls.