Complete list of Cockpit arguments for triggers.

[Nate--IRL--]

Olgerd just published a Complete list of Cockpit arguments, they maybe useful for Mission builders for cockpit based triggers.

 

http://files.digitalcombatsimulator.com/en/84654/

 

Nate

[Cibit]

Thanks. So now I can set a value on say the Vertical Velocity indicator and then have left engine fail as an example?

[Nate--IRL--]

I haven't a clue sorry :) I'm sure you'll figure it out, I just saw they were available and thought I'd point them out - I don't actually know how to apply them.

 

However - a quick look suggests setting a continuous trigger with a Cockpit argument of 12 and unit of -1 and a failure set to left engine- Will have the Left engine fail at a Decent rate of -6000 ft/m

 

EDIT:- Yep that's it see attached

 

Nate

Cockpit arg test.miz

Edited June 29, 2011 by Nate--IRL--

[Cibit]

Thanks pal:thumbup:

[Snoopy]

I sure wish I had the time to dig into the ME and learn how to use these or any other triggers!

[Nate--IRL--]

Once you do a few of them they kinda become intuitive, it is worth the effort.

 

Nate

[Speed]

Thanks Olgerd!

[jeffyd123]

will this guarantee me a date with that hottie down the road?????

[Nate--IRL--]

Well you'll either know how to push her buttons or get arguments, so 50/50 I'd say :)

 

Nate

[jeffyd123]

goood 'nuff for me

[BBQ]

if I'm using the Cockpit Parameter is equal to statement--what do I put for the parameter--the relevant description text in first row of excel spreadsheet--or the argument number? I know what to put for the value--

[HotFish]

Hi, I´ve seen somewhere here in the Forums, that ed will (probably) create a detailed ME guide for cockpit based triggers sooner or later. Good.:)

 

In the meantime, how to use (Olgerd) the complete list of cockpit arquments to make more realistic voiceovers? Radio messages heard when radio is off or is not set properly does not feel good.

 

I would like to use parameter is equal to -tool in ME to check, that radio is set to right frequency, when audio (F10 radio or other audio) is played. I tried it, but it didn´t work yet.

 

 

I´m looking for trigger, something like this for VHF/AM radio frq 131.00;

 

RULES:

parameter is equal to (parameter# 138, value 0.1); check if radio is set TR.

parameter is equal to (143,13); check the first knob is set 13.

parameter is equal to (144,1); check the second knob is set 1.

parameter is equal to (145,0); check the third knob is set 0.

 

And so on...

 

 

 

How to use these arguments and values? Any experiences?:helpsmilie:

[Lino_Germany]

Argument for Pinky Switch is missing

 

Hello dudes,

 

I am missin the cockpit argument for the Pinky Switch (Master exterior light control switch). Can someone help?

 

Kind regards

Lino_Germany

[HiJack]

I belive its this one:

POSITION FLASH/OFF/STEADY (PTR-LGHTCP-POSITION) = 287

 

EDIT: No it's not I see now.

 

EDIT2: Fount it. It's "Pinky Switch = 753 (-1(AFT), 0(CENTER), 1(FORWARD))

 

(HJ) :D

Edited July 27, 2012 by HiJack

[Lino_Germany]

Thanks for your quick help!

[Lino_Germany]

Ok, now I have the Argument for the Pinky. But how can I highlight it via the "X:Cockpit Highlight Element" Script? For this I need a special Name, such as "PTR-LCP-AUTOPILOT-ENGAGE" for the autopilot.

 

Regards

Lino_Germany

[HiJack]

The name was not in the description so ED needs to answer this.

 

EDIT: Are you sure this argument is not used in any of the other training missions?

EDIT2: Unzip the missions and search through the "mission" files after "753"

EDIT3: Use Notepad+ or ProgrammersNotepad.

 

(HJ)

Edited July 29, 2012 by HiJack

[Lino_Germany]

The name was not in the description so ED needs to answer this.

 

EDIT: Are you sure this argument is not used in any of the other training missions?

EDIT2: Unzip the missions and search through the "mission" files after "753"

EDIT3: Use Notepad+ or ProgrammersNotepad.

 

(HJ)

 

Thanks for your help. I even thought the same. Unfortunetly every "Startup training Mission" I played does not use the Master exterior light control switch in the Startup protocol. So it seems to be very hard to build a COMPLETE startup training mission... The Problem is not the argument Number (753), it is the missing special Name of the argument. Nearly every knob in the cockpit has a special name and can easyly highlighted with the "X:Cockpit Highlight Element", but not the HOTAS switches.

 

For me it is important, that before I change the anti collison lights for example, I check first the setting of the Master exterior light control switch on the HOTAS. But until now I have not found someone, who is able to highlight the Pinky switch via script Argument-NAME. (Sorry for my bad english, hope you understand what I mean.)

 

Kind regards, Lino_Germany

Edited July 29, 2012 by Lino_Germany

[EvilBivol-1]

All of the information you need to read cockpit switch/button states is defined in /.../Mods/aircrafts/A-10C/Cockpit/Scripts/clickabledata.lua. You can also use the maintpanel_init.lua file to read non-clickable items, like needle instruments.

 

You can find a more complete description of the cockpit triggers here (it is now slightly out of date):

http://forums.eagle.ru/showthread.php?t=81376

[Lino_Germany]

Dear EvilBivol, we all know that. But with all that aknowledge it is not possible to highlight anything at the Throttle or Stick because there are no CONNECTOR NAMES for the arguments.