Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable Read AH-64D clickabledata #95

Open
jieweiyang opened this issue Mar 28, 2022 · 4 comments
Open

Unable Read AH-64D clickabledata #95

jieweiyang opened this issue Mar 28, 2022 · 4 comments

Comments

@jieweiyang
Copy link

AH-64D clickabledata not showing in the "ID Lookup" page.

Is this about the new "Crew" parameters in those clickable definitions?

@inexus888
Copy link

Hi,
I'm curious about how to use the clickable data too.

The reason is that I would like to be able to bind to the special MFD buttons like WPN, TSD, etc. which I can see in exportscripts are available but I can't find a way to trigger them.

I've tried various permutations such as assuming the device id is 44 (based on the dcs lookup screen) and setting the button id to 10 (based on the exportscript file for the AH64).

Keen to hear if anybody knows how to make this work.

@Dan-09
Copy link

Dan-09 commented Apr 30, 2022

Hi, I'm curious about how to use the clickable data too.

The reason is that I would like to be able to bind to the special MFD buttons like WPN, TSD, etc. which I can see in exportscripts are available but I can't find a way to trigger them.

I've tried various permutations such as assuming the device id is 44 (based on the dcs lookup screen) and setting the button id to 10 (based on the exportscript file for the AH64).

Keen to hear if anybody knows how to make this work.

Hi,
I have the Profile for CPG but not the pilot (mostly playing as CPG so far)
I am using Momentary with lamp, I can try to share the profile on the DCS forum. contains every key or switch for CPG |

1
2
3

@inexus888
Copy link

inexus888 commented Apr 30, 2022

Thank you. I finally found out how to bind them. So please ignore my post.

I.e. FCR for the left MFD for the pilot is the last 'left MPD Pushbutton' (button id 3031,device id 11). Then each previous button are the other special MPD buttons counter clockwise - i.e. FCR, WPN, TSD, A/C...

M is different as it is the 18th LFT MPD Pushbutton.

Binding these makes it a lot easier for me to fly as I struggle to take my hand of the joystick and use my mouse to click in the cockpit :)

BTW, so are you able to have a button light enabled when the specific screen say like WPN is selected? I tried that using button id 10 for the pilots left WPN button from the exportscript but the value always appear to be 0 apart from momentarily when I click the button.

@Dan-09
Copy link

Dan-09 commented Apr 30, 2022

No worries, It does make things easier.
No, you can not set the light on or off based on which mode of screen wpn, com, vid... you have selected.
if you look at the script and key feedback, there is no feedback from the DCS to Streamdeck
The only input is you pressing the key momentarily for that moment you apply value 1 for example and when you let go it goes to 0 when a switch is like this you can not set the light, I set it so if I hold it, it will be bright.

Also, you see in the picture those keys which are black? those show value. I used this for them to show value (this is just one example):
0.0000=FLIR LEV
0%,0.2000=FLIR LEV
20%,0.4000=FLIR LEV
40%,0.6000=FLIR LEV
60%,0.8000=FLIR LEV
80%,1.0000=FLIR LEV
100%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants