Unable to Locate Su-25T Cockpit Argument IDs

[millytron]

Hello,

I'm trying to set a trigger using the state of cockpit arguments in the Su-25T.  According to the manual, cockpit arguments in non-clickable cockpits should be located in Mods/aircraft/Su-25T/Cockpit/Scripts/mainpanel_init.lua 

In my Steam version, I've navigated to this folder and there is no "mainpanel_init.lua" file for me to view to identify the correct cockpit arguments, or any other .lua files that have this information.   I've also looked at the included Su-25T training missions in the editor and that information is not visible.   I do seem to have these files for the TF-51 and F5-E (the only two other aircraft I have). 

Figuring out what is actually the "argument ID" in that morass of numbers and lines of code is another issue for me deal with, but does anyone know where I can I find the cockpit arguments for the Su-25T?  I found a post that showed a trick into revealing cockpit codes as a Tooltip in the Controls options, which was a helpful start, but I need access to the scripts themselves for more information.  Thanks.

[Rudel_chw]

On 3/24/2022 at 3:28 PM, millytron said:

In my Steam version, I've navigated to this folder and there is no "mainpanel_init.lua" file for me to view to identify the correct cockpit arguments, or any other .lua files that have this information

 

On my Stand-alone version of DCS there is no such file either. I believe that those files are only present on full-fidelity Modules, not on Flaming Cliff ones. For example, the free TF-51D does have the file, while the free Su-25T does not.

However, you can detect the keybinds that the user presses while flying ... is that enough for your trigger?  Can you describe in more detail exactly what are you trying to acomplish? Maybe there is a different way to achieve it.

 

[millytron]

Much appreciate the response - I believe it was one of your own past posts that gave me some more insight into the issue.  It appears the manual has outdated information. 

I want triggers to activate when the left/right engines start (to trigger a message display).  The keybind detection sounds like a perfectly fine workaround - I can use that.  Thanks very much.

[Rudel_chw]

7 hours ago, millytron said:

I want triggers to activate when the left/right engines start (to trigger a message display).  The keybind detection sounds like a perfectly fine workaround - I can use that. 

 

Correct, the trigger action to use is X:START LISTEN COMMAND, like this:

 

 

The Commands to detect would be:

Left Engine Start        311
Right Engine Start        312
Both Engines Start        309

Then you would check the Flag, to trigger the message:

 

 

This catches only the beginning of the engine start sequence. To detect when the engine reaches idle, use the Condition X:COCKPIT PARAM IN RANGE, like this:

 

 

The parameters to monitor are:

BASE_SENSOR_LEFT_ENGINE_RPM

BASE_SENSOR_RIGHT_ENGINE_RPM

 

PD: Thank you @NineLine & @BIGNEWY, for granting the wish to have named flags 

Su-25T - Detect Left Engine Start (by Rudel-chw).miz

Edited April 1, 2022 by Rudel_chw