Stream Deck Interface - Issues with Certain Types of Push Buttons

[Toni Carrera]

Hi All,

I have a SD XL and am coding a new profile for the AH-64D at the moment. All the options I am using are using Device and Command ID's and no keyboard shortcuts. Naturally, i am using the ctytler interface to achieve this. I have both MPD's, EUFD, KBD and Comms panel's done (Pilot Only), and all is fine with them

The issues arise when it comes to buttons such as Guard, Tail Lock etc etc. Having looked at the output from the various buttons, no matter what you do when you press them, they end up back at 0.0000. This makes it difficult to change text based on behind the scenes values, or change graphics based on value. You can see when you press the button and watch the value change on the SD, and it counts up to 1.0000, and then straight back to 0.0000, despite the value having changed in the sim

Can anyone advise on what I need to do. Do I have to make some fundamental change a file or something. I just do not get it. If you look at things like a squelch button, press it and the value goes from 0 to 1, press the tail lock and it goes from 0.0000 to 1.0000, and then straight back to 0.0000, despite the Tail wheel has unlocked or locked

Can someone advise me on this please. It was not like this when I coded my F/A-18C Profile

Thank you

Toni Carrera

[Bailey]

For these buttons it takes about a second for the sim to register if they are activated externally (much like the F18 ON/OFF button for those who were familiar with that one). Specifically for the tail wheel lock, in the sim the tail wheel must be aligned before the lock can physically drop into place. To make sure it is working I suggest a cold start. 
Here is what I have for the tail wheel.

 

Most of the other buttons of this "type" follow the same "logic" of making sure you press and release.

 

[Toni Carrera]

Afternoon Bailey,

I understand about the tail wheel etc and when or not the pin falls, but I have the same for the Pilot Emergency Guard button for instance, as well as many others

Emergency Guard (Pilot)

OFF

ON

When pressed, the correct button turns on and off in the Pilot Seat, and yet the value in StreamDeck rolls back to 0.0000, but stays activated or deactivate in the cockpit. So I know it is working, it just goes back to 0.000, not matter what state it is in. I only use this kind of button for testing initially to make sure I have the right control

I am looking at your settings above and wondering whether we are using the same clickabledata reference file. I have no 5,3003, 402 for the tail wheel

Are you using a different one?

Toni

Edited March 27, 2022 by Toni Carrera

[Bailey]

It looks like you are monitoring the position of the button arg. Monitor the status of the light arg instead. 

You can find the light arg in my apache export Lua file on the github in my signature. 

Edited March 27, 2022 by Bailey

[Toni Carrera]

I am trying to set it, as normal, so that I can have a button that when pressed changes from, let's say 'GUARD' unlit, to 'GUARD' lit, using the same method I did for the others in my complete, e.g.

to 

But I need the value to be specific so that the formula will work. Which is what I did for my F/A-18C, but if the value always ends up at zero the formula to switch the icon can never work

Of have I gone way off the rails and totally mind f'd myself?

Toni

[frostycab]

Set your Image State Change ID to 403 and try that.

The value you're seeing is the state of the signal being sent to DCS. You need to be able to see the state of the item within DCS, otherwise the button will just return a 1 while you're pushing it.

If you look in the lua file and scroll down to the section "-- Warning Lights and Button Lights" you'll find the ID there.

Edited: Had wrong ID

Edited March 27, 2022 by frostycab

[Toni Carrera]

Hi @frostycab / @Bailey 

I understand the whole -1.0000 or -1 and 0, or .00 and 1 thing, I only use it for debugging. I convert the string under the last section of the interface

0.0000=GUARD OFF, 1=GUARD ON etc etc

Once I have that sorted, which I only use for testing and debugging, then I put in the proper graphics., or button type, and swap the images with the < than

 

etc etc. i am just trying to understand why, when off, GUARD has a value of 0.0000 and then when you manually press the button with the mouse to turn it on in the keyboard, you can see the value go to 1.0000. and then when displaying as on in the keyboard, the value goes straight back to 0.0000

If you look at my F/A-18C, you will see that I full created ever function of the cockpit, in both actions and Summary report screens. Not a single keyboard shortcut, all Device ID's,  Command ID's and Button ID's - https://www.digitalcombatsimulator.com/upload/iblock/5b7/r2ba9njiqxz1tu8ecjh2wpwmo14y8rsn/StreamDeck-XL-Published-Version.zip

I do not mean to come across like I am being argumentative, I am clearly not getting my point or issue across

I hope what I have written above does not come across as confrontational, it was not meant to be in anyway. I promise that all I am just trying to do is relay the issue I have noticed so you guys with the big brains who probably know an awful lot more about this issue

I hope what I have written and provided in terms of my released F/A-18C profile, you can see I am jut trying to relay a real problem I am experiencing

Thank you

Toni Carrera

Edited March 28, 2022 by Toni Carrera

[Bailey]

For your Guard button post pictures of the three sections and their current entries/values. Command, image, and text. 

[frostycab]

You don't sound argumentative, so don't worry. I may not understand exactly what you're having trouble with, so excuse me if this is repetitve and not what you're looking for.

When you manually press the button in DCS the debug goes to 1, correct?and then returns to 0 when you release the button in DCS or does it go to 0 while still holing it down with the mouse?

If it's the former then it's correct.

With the 403 Offset set in the Image Change section in the SD the button does exactly the right thing for me. I press the SD, and as long as I hold the button down the same button in DCS is pushed in. I release, it releases. Whether I press the button on the SD or in DCS, the icon on my SD changes to match the current state of the DCS button.

I suspect that what you're doing right now is debugging the wrong thing. What DCS ID are you reading in the Title Change field? I set my Title Change DCS ID to 403 to match my Image Change ID and It stays at 1 when Guard is lit.

Do you want to talk on Discord so we can really understand exactly what's up?

As Bailey says, pictures of all 3 sections should clear things up pretty quickly I hope.

Edited March 27, 2022 by frostycab

[Toni Carrera]

Hi All,

Would be happy to talk to you on Discord, sometimes you just can't say a thousand written words, what you can in 20 verbally. I will detail below as you have requested the issue and the results. For the purposes of testing, here is what I have setup

1.

2. When in the 'Pilot' Cockpit, when I press the button on the StreamDeck, the physical button depresses in the cockpit, and the GUAGE word lights up. When in the 'CPG' cockpit, just the word 'GUAGE' lights up obviously, with no displayed physical press of the cockpit button, because the one I have coded on the StreamDeck is for the Pilot Cockpit

3. When I press StreamDeck button again, The displayed physical press of the button appears in the 'Pilot' cockpit, and the illumination for the word 'GUAGE' goes out, and again, out in the 'CPG' cockpit

-------------------------------------------------------

4. During the physical button press on the actual SD button itself, I can see the values on SD button go from 0.0000 to 1.0000 and then straight back to 0.0000

Therefore, the whole functionality of the SD button works, however, I am not able to change the icon below from unlit to lit, because the value for the second state if the value is to be greater than 0.0000, as it only for a few milliseconds, shows the value of 1.0000

 

Does that make more sense now?

Toni

Edited March 28, 2022 by Toni Carrera

[Bailey]

Your image state change DCS ID is 310, which is Guard button. Change it to 403, which is Emergency Guard PLT Light.

[frostycab]

24 minutes ago, Bailey said:

Your image state change DCS ID is 310, which is Guard button. Change it to 403, which is Emergency Guard PLT Light.

Yup. I can confirm that this is 100% correct. As I said, your debug is currently reading the state of the button which is a momentary, whereas you need to read the lamp itself for it to stay latched. You can't get that offset from the ID Lookup with this plugin. You need to look in the lua file to find it.

Edited March 28, 2022 by frostycab

[Toni Carrera]

Yay, now we are cooking. So from an action point of view, I use what I have been, for the display point of view, that is what you were referring to before Bailey when you said read the value of the lamp in the ExportScript

Understood now

My sincerest thanks to you both for your patience an understanding, I truly appreciate the information you continue to, and have provided to me

Off to code the rest of them now

Toni