Command and Option Tooltips For F-16 Controls

[mkel2010]

Does anyone know if the Commands part of the Command and Option Tooltips feature is supposed to work for the F-16? According to the DCS user manual, I should see the associated command (for using X:SetCommand in Mission Editor triggers) by hovering over the command description in the Controls section. When I do this, all I get is a repeat of the named description but no associated command number; I can see the Clickable Cockpit commands when hovering over the Keyboard bind for an command so I'm pretty sure I have everything configured correctly.

[mkel2010]

@Lord Vader Would you by chance be able to answer my question, posted above?

[rob10]

23 hours ago, mkel2010 said:

Does anyone know if the Commands part of the Command and Option Tooltips feature is supposed to work for the F-16? According to the DCS user manual, I should see the associated command (for using X:SetCommand in Mission Editor triggers) by hovering over the command description in the Controls section. When I do this, all I get is a repeat of the named description but no associated command number; I can see the Clickable Cockpit commands when hovering over the Keyboard bind for an command so I'm pretty sure I have everything configured correctly.

There was a change recently in what you have to do to make this show up IIRC.  I don't use it so I can't remember exactly what it is or where to find it, but I'd start by reading through the Mission Editor subforum because it was likely there.

[mkel2010]

1 hour ago, rob10 said:

There was a change recently in what you have to do to make this show up IIRC.  I don't use it so I can't remember exactly what it is or where to find it, but I'd start by reading through the Mission Editor subforum because it was likely there.

I think what you're referring to is creating an Autoexec file to show the Command and Option Tooltips. I've already done that. I can see the commands for Clickable Cockpit items for switches, but they don't work for knobs that need to be turned. For that, there needs to be a numeric command that "should" populate in the tooltips for the far left column of the Controls page (the descriptive name of each control.) The information doesn't show for me.

[rob10]

1 hour ago, mkel2010 said:

I think what you're referring to is creating an Autoexec file to show the Command and Option Tooltips. I've already done that. I can see the commands for Clickable Cockpit items for switches, but they don't work for knobs that need to be turned. For that, there needs to be a numeric command that "should" populate in the tooltips for the far left column of the Controls page (the descriptive name of each control.) The information doesn't show for me.

Yep, that's what I was thinking of.

[Rudel_chw]

On 8/31/2024 at 1:04 PM, mkel2010 said:

but they don't work for knobs that need to be turned.

 

Hi,

Can you tell me which knob you need to turn? ... I'd like to take a look

 

Eduardo

[mkel2010]

15 hours ago, Rudel_chw said:

 

Hi,

Can you tell me which knob you need to turn? ... I'd like to take a look

 

Eduardo

For starters, the Comm 1 and Comm 2 knobs on the left console - to off. 

I've read through other posts that say you just need to repeat the Clickable Cockpit commands multiple times and I've tried that. I get zero movement when trying it this way. Whereas the Clickable Cockpit option has a field for the cockpit ID, the Command and a value, the X:SetCommand only has fields for the command and value. The command from Clickable cockpit alone (without the cockpit ID) doesn't work for turning knobs, at least for me. It stands to reason that if you can set switch positions through ME, you should be able to also set cockpit knobs.

[Rudel_chw]

59 minutes ago, mkel2010 said:

For starters, the Comm 1 and Comm 2 knobs on the left console - to off. 

 

Ok, the command for those knobs are:

 

Device 39, Command 3019, for Comm 1, value 1 for CW or -1 for CCW

Device 39, Command 3022, for Comm 2, same values as above.

 

59 minutes ago, mkel2010 said:

I've read through other posts that say you just need to repeat the Clickable Cockpit commands multiple times and I've tried that.

 

That's correct, a single execution of the X:COCKPIT PERFORM CLICKABLE ACTION moves the knob just a bit, you need to repeat it about 50 times to get the knob fully CCW.

 

59 minutes ago, mkel2010 said:

I get zero movement when trying it this way. Whereas the Clickable Cockpit option has a field for the cockpit ID, the Command and a value, the X:SetCommand only has fields for the command and value. The command from Clickable cockpit alone (without the cockpit ID) doesn't work for turning knobs, at least for me. 

 

You don't use X:SET COMMAND for this type of control, instead it is used for simulator stuff like calling up the external view, or enabling active pause. Using this  trigger works for me:

 

 

I'm attaching the test mission for you to try.

 

Eduardo

F-16C - Cockpit Trigger Testing (by Rudel_chw).miz

[mkel2010]

1 hour ago, Rudel_chw said:

 

Ok, the command for those knobs are:

 

Device 39, Command 3019, for Comm 1, value 1 for CW or -1 for CCW

Device 39, Command 3022, for Comm 2, same values as above.

 

 

That's correct, a single execution of the X:COCKPIT PERFORM CLICKABLE ACTION moves the knob just a bit, you need to repeat it about 50 times to get the knob fully CCW.

 

 

You don't use X:SET COMMAND for this type of control, instead it is used for simulator stuff like calling up the external view, or enabling active pause. Using this  trigger works for me:

 

 

I'm attaching the test mission for you to try.

 

Eduardo

F-16C - Cockpit Trigger Testing (by Rudel_chw).miz 11.4 kB · 1 download

I will give that a try (but it shouldn't take repetition of a command 50 TIMES to do this!) Is it possible to create a script that can be called in a single line instead of having to input this command 50 times?

[Rudel_chw]

8 minutes ago, mkel2010 said:

…  it shouldn't take repetition of a command 50 TIMES to do this!

 

agree, I would prefer that the value could be set to any value from 0-100%

 

8 minutes ago, mkel2010 said:

Is it possible to create a script that can be called in a single line instead of having to input this command 50 times?

 

sure, but it would likely take longer to code rather than just clicking 49 times on the CLONE button.