-
Notifications
You must be signed in to change notification settings - Fork 21
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
Comments
Hi, 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, |
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. |
No worries, It does make things easier. 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): |
AH-64D clickabledata not showing in the "ID Lookup" page.
Is this about the new "Crew" parameters in those clickable definitions?
The text was updated successfully, but these errors were encountered: