ZBoT

Lua attached. Although it probably doesn't matter because you state in another thread this file does not affect the StreamDeck DCS interface listing. AH-64D_BLK_II.lua I was able to find a CSV file of all the device/button ID's here: So that helps. Would still be nice to just click and have it import through the app though.

Thanks! Update doesn't do anything unfortunately.

Hi. I'm having an issue with the Apache .lua and DCS StreamDeck. When I try and view the clickable data for the Apache in the StreamDeck DCS interface, I don't get any listings: I do see them when I am looking at other modules: I have tried copying the Apache .lua from github again, but that didn't work. Anyone know how to resolve this? Thanks!

I tried downloading the apache .lua file again but that didn't work for me. I still can't get the apache module to show the device/button ID's. Just a blank page like I posted above. Thanks for the response though! If anyone else has any idea how to fix this, please let me know.

How are you finding the button and device ID's? I don't see them in the AH-64D_BLK_II.lua file. When I try and view the clickable data for the Apache in the StreamDeck DCS interface, I don't get any listings: I do see them when I am looking at other modules:

Thanks!! I'll give it a try tonight! I really appreciate it!

Anyone get the Buddy Fox Master Caution to work with the AH-64D Apache yet?

This is working for me. Thank you SO MUCH!!!!

Thanks for confirming. Thought maybe I was doing something wrong.

The F/A-18C manual states that HARM Pullback mode works in either A/A or A/G modes: I'm unable to pickle a HARM in A/A mode though. I have the following set: Master Arm = On A/A mode = selected HARM Override = unboxed When a critical threat is detected I get HARM in the HUD (with no X). I press the pickle button but no HARM is fired. I have to switch to A/G to be able to fire. Can anyone confirm they are able to shoot HARM from SP pullback mode when in A/A mode? If so anyone know what I am doing wrong? Thanks!

Ended up finding that a macro was assigned to the F9 key causing it not to work. No idea how that got assigned but everything now works perfectly!

I ended up finding it in the keybinds. It wasn't under F18, I had to go under the general section. Come to find out the F9 key on my keyboard is not working. So that explains why it wasn't working.

Thanks but I have searched in the keybinds and nothing comes up for LSO. Also when I press alt-F9 it doesn’t go to anything in the keybinds. Could someone take a screenshot of their lso option in the keybinds? That might help me find it. Thanks!

Hi, Since buying the Supercarrier I've been unable to enter the LSO view. I hit alt-F9 and nothing. I've searched in the keybinds but I don't see anything for LSO view. Anyone know where the keybind is located? Or how I can fix this? Thanks!

I received my throttle back from Thrustmaster yesterday. 10 days after I shipped it. Not bad turn around time. Unfortunately they did not fix my issue. They simple replaced the main board on the throttle and sent it back to mean without even testing. The main board was fine in my throttle and I believe (which I told them) the issue was with the HALL sensor which should have been replaced. So now I'm back at the beginning and have emailed Thrustmaster and awaiting a response (typically 3 business days to get a reply back). I'm pretty frustrated they didn't even test it before sending it back to me.

Will do. Still no communication yet and they've had it almost a week. Will post my experience here when complete so others can reference in the future if they have Thrustmaster RMA's.

Thanks Madone! Mine got there a couple days ago but I haven't heard anything from them. Hoping for a quick turnaround. Thanks for your insight.

@Madoneone more question if you don't mind. Once your throttle got to Thrustmaster, how long until they sent back the new throttle? Also did they give you a return shipping tracking number or any other contact? They received my throttle two days ago but I still haven't heard anything. Just curious what your experience was. Thanks!!

Thanks for making these charts! They are great. One correction I noticed is on Al Dhafra. You have the taxiway entering 31R as J and I think it is B.

Awesome news Madone! Glad they sent you a new throttle!! That's awesome!! I think I will send mine in after the new year here and see if they do the same. Thanks for posting back your experience. That was really quick. Enjoy that new throttle!

Thanks for the response again. I asked Thrustmaster what the turnaround time was but they ignored my question. I have an RMA setup now but I'm going to wait until after the holidays since I want to use my throttle now while I"m off. I'm also in USA so it will have to go through customs which I'm guessing will take a bit longer. I keep hoping I can just fix this myself but I'm coming to the conclusion the HALL sensor needs to be replaced like you stated. Thanks again for your feedback.

Thanks for the response. Please do post back once you receive your throttle back and the turnaround time. I will probably wait until after the holidays to send into Thrustmaster so it's not delayed further. Did you have the delta slew installed in your throttle? I'm guessing I have to uninstall that and put the original slew back in before sending back to Thrustmaster. What a hassle.

I just put the original Thrustmaster detent in and ran the calibration again. Issue still persists. It's odd the issue is only with the right throttle and Button29, left throttle and Button30 works perfect. Thanks again for the help!!

Just wanted to drop a note and say THANK YOU for this plugin!! Just started using it and it is fantastic. Well designed, written and documented. You sir are an asset to this community! Thanks again!

Thank you for your response and suggestions. I have tried clearing the Windows calibration and calibrating with the tools from your website at least 10-15 times. I have even tried uninstalling the Thrustmaster driver, rebooting and reinstalling. I do have a custom push through detent and hadn't tried removing that for calibration. I just tried removing it though and calibrating again and the issue still persists. Any other suggestions? Thanks again!!