X: Cockpit Argument In Range Question

[DishDoggie]

I wanted to be able to tell when the Player turns on the Battery in the Huey. Problem I am finding out is I don't see a way to do that with the X: Cockpit  Argument In Range with the Volt Meters or the Battery Switch or any other thing Voltage should be input to. Looks like I don't have the right Logic thinking to find the way to get this done.  Can any one help with a way for this to work. I do not know programing so I can not write a file. Lol Sucks to be me. Thank You if You can help.

[DishDoggie]

Well It's like this all the time but I found the answer after posting this so I now know it is Argument 219 and the Min=0 and the Max=0 for ON and Min=0 and Max=1 for OFF

So it is X: Cockpit Argument In Range

219

Min = 0

Max = 0

Whatever Action you want to trigger with it.

[Rudel_chw]

17 hours ago, DishDoggie said:

Well It's like this all the time but I found the answer after posting this

 

Hi,

I see that you already solved your problem, but I'd just like to expand a bit on this subject, to hopefully make it clearer for anyone with the same issue. This information is described also on the DCS User Manual 2020, located on the /doc/ folder of the DCS install, on the "Cockpit Triggers Guide" section, starting on page 149.

Basically, the X:COCKPIT ARGUMENT IN RANGE is a trigger condition that allows you to check the status of the cockpit switches and knobs. The position of a switch or knob is a value between -1 to +1, so for example you can see if a certain switch is ON or OFF, or if a 5-position knob is set on its 3rd position for example.

The exact values that a switch or knob may have on each of its positions is not standarized, usually for a two position switch the value 0 is down and 1 is up, for a three position switch it can be -1 for its down position, 0 for its center one, and 1 for its up position, but some switches may behave differently. Knobs can be particularly annoying, for example a knob can have values like 0 0.1  0.2  0.3  etc, other times they can be 0 1/13 2/13 3/13, etc.

I usually find the correct values by trial and error using a small mission where I only have the necessary triggers to detect different positions, like this:

 

 

The first trigger highlights the switch or knob that I'm interested in, the remaining triggers check possible values using X:COCKPIT ARGUMENT IN RANGE and if match they display the value on the screen for a few seconds. The triggers are of the Switched Condition type so that I can flick the switch or knob several times during the test. Also note that to check a value, I use MIN and MAX to preclude the chance of a rounding error since the argument value is non-integer, so to check for 0.5 I ask if it is between 0.49 and 0.51

Please note that this trigger probably won't work well on a multiplayer mission, since it does not specify to which client it is applied.

best regards and thanks for the credits

 

Eduardo

[DishDoggie]

Awesome Good Stuff Thank You So Much.