Looking for a file for the cockpit element name F1-EE

[Gladius]

I would like to try to do a few training missions for the Mirage F1-EE.
But to highlight the switches, I need the clickabledata.lua file for the Mirage F1-EE. I found the file but I can't find the cockpit element name.

Where are these cockpit names stored?

[TOViper]

.) Just fire up the DCS model viewer (dcs\bin-mt\modelviewer2.exe).
.) There, select File > Load model, and browse to your DCS\Mods\aircraft\MirageF1something folder, there search for the shapes folder, there select the  F1something.EDM file.
.) Then select Show > Show connectors, and surfe through the cockpit to see the cockpit control or element of your desire, then hover your mouse over it, and the ELEM NAME is then shown in cyan color. Note: this only works for controls, not for indications!

 

BTW: It must read "Auslassdruck und Einlassdruck" (7 is behind the turbine, 2 is in front of the fan).
 

Edited November 2, 2024 by TOViper

[Rudel_chw]

33 minutes ago, Gladius said:

Where are these cockpit names stored?

 

For most aircraft the cockpit switches, knobs, and levers are defined on the clickabledata.lua file, located inside its cockpit sub folder. However, the Mirage F1 has four playable variants, so Aerges has placed those common to all versions on a separate clickabledata_common.lua file ... so you may have to search a bit to find exactly on which file the switch is defined:

 

 

For your example, the battery switch is defined on the common file, like this:

 

 

As the lua file is quite long, you can search it using the tooltip text that appears when you hover the mouse over the switch, on this case search for "Battery switch".

 

PNT-113 is the element name, to be used on the X:COCKPIT HIGHLIGHT trigger action.

113 is the argument, to be used on the ARGUMENT IN RANGE trigger condition, to check the current status of the switch ... on this example if the argument is 0 the switch is Off, an argument of 1 denotes the switch at On.

[Gladius]

vor 5 Stunden schrieb TOViper:

.) Just fire up the DCS model viewer (dcs\bin-mt\modelviewer2.exe).
.) There, select File > Load model, and browse to your DCS\Mods\aircraft\MirageF1something folder, there search for the shapes folder, there select the  F1something.EDM file.
.) Then select Show > Show connectors, and surfe through the cockpit to see the cockpit control or element of your desire, then hover your mouse over it, and the ELEM NAME is then shown in cyan color. Note: this only works for controls, not for indications!

 

BTW: It must read "Auslassdruck und Einlassdruck" (7 is behind the turbine, 2 is in front of the fan).
 

 

Thank you very much for the tip, I didn't know about the model viewer.

And thank you for the tip about Viggen. I'll adjust it. By the way, your training missions are very well done.

[Gladius]

@Rudel_chw Thanks for the detailed explanation.
I almost suspected that the merging of the clickabledata.lua of the different models would happen. I actually think it's a good solution, it increases efficiency for the programmers.

I'll get to grips with it then.

I've probably chosen a more complex pattern to get the necessary information from the lua files, but I find it very interesting.

Unfortunately, the training missions for F1-EE are still missing. So I'd like to try to add something here.

I hope that this winter is a little quieter and that I can spend a little more time with DCS and learn to create training missions on my own.

[Rudel_chw]

31 minutes ago, Gladius said:

I hope that this winter is a little quieter and that I can spend a little more time with DCS and learn to create training missions on my own

editing training missions is almost like a game within a game, I truly enjoy the challenge of making the triggers so aware of what the player is doing, that you can dispense with as many of those dreadful "press spacebar to continue" as possible …  

[TOViper]

9 hours ago, Rudel_chw said:

...., that you can dispense with as many of those dreadful "press spacebar to continue" as possible …  

Yeah, absolutely.
Best trick is to set the switches to incorrect positions after spawning, so the student has to correct as much as possible.
Seen from a didactic perspective, a click to correct something is much better than just a "check this and that and press SPACEBAR to confirm".
But it also has some taste of "non-realistic", since pilots usually set all cockpit switches to correct positions when turning off the aircraft.

You can change switch positions by using the trigger action "X: COCKPIT PERFORM CLICKABLE ACTION" (dev, command, value).
Check the status of a switch with "X: COCKPIT ARGUMENT IN RANGE" (arg, min, max)

In the mission editor, open up the training lessons for the Viggen on my homepage or Rudel's training lesson for the Viggen; they all contain thousands of such actions and checking of switch positions.

But be aware: finding out dev, command, value, arg, min, max requires carefuly study and often time consuming investigations, so be prepared to spend A LOT of hours on making and testing on one single lesson.

Good luck mate!

Edited November 3, 2024 by TOViper

[Gladius]

DCS is actually there to fly and carry out missions.
I like doing that too, but every time I spend some time with a model, I would rather write a manual about it, create a skin or, more recently, create training missions.
And once I've started something, I can't stop until it's completely finished.
That will probably take several hours

So everyone will find something for themselves in DCS, including practicing patience.

[TOViper]

Haha, you tell me ....

[Gladius]

Is it actually possible to press another key instead of "Press the space bar"?
Or if, for example, I want to press the "F2" key to continue? Where can I find the element name and argument number for that?

[Rudel_chw]

2 minutes ago, Gladius said:

Is it actually possible to press another key instead of "Press the space bar"?

 

The Spacebar (and also the backspace) is hardwired for use during training .. in fact if you bind the spacebar to an aircraft function, like for example "firing guns", then it will interfere with it.

 

2 minutes ago, Gladius said:

Or if, for example, I want to press the "F2" key to continue? Where can I find the element name and argument number for that?

 

The F2 has uses as both a View key and a communications menu key, so it probably wouldnt work on this case.

 

You can try to have the user operate a cockpit control instead, like flicking a switch for example .. this is my favorite option, so that the transition from one step into another feels natural to the user.