CM2024

If you want to synchronize the lights of the TM Warthog throttle with the F18, take a look at this thread. This works really well and feels like a big upgrade to the throttle.

@slughead This is perfect. I tested on the A-10C2 to turn on and off the battery, changing the light settings, the speed break, canopy open and close, and the gear handle lamp for gear up, down, and stalls. Also tested it when instantly restarting the mission and loading the mission a second time after starting DCS. Checked the F18 too and everything still works. The updated script makes a huge difference when learning the new plane. Thank you!

@slughead I'm starting to learn the A-10C2. Would it be possible to update the script for the warthog throttle? It would be great to have similar functionality like the F18. Especially to have the lights turn on and off with the battery switch. The gear handle lamp would also be a great addition. I don't think there is a separate APU light like in the F18, but the "Canopy unlocked" indicator could be a good option for the top LED. Really enjoying the script. Thank you!

@slughead Success! Those work perfectly. I did the same tests from last time and everything works great. The new additions are fantastic. Thank you!

@slughead Fantastic! When starting a cold start mission, both after starting DCS and when starting another one, or even restarting, works perfectly. Also the landing gear raise/lower/stall works with and without the speed break. This is really great. One last suggestion: When ending a mission, all lights and LEDs briefly light up. I think this is set at the highest light level and really bright for just one second. Is it possible to set that to the lowest light level?

@slughead I uninstalled the old script and reinstalled the 2 pre-release items and it works without the error. Maybe some of the files didn't override the first time. I started the test with the F18 free flight mission. The new landing gear indicator is fantastic! It works both when lowering and retracting the landing gear. It also gives the stall warning indication, which is very cool. Combing the bottom LED with the speed break is a great idea and works well. To test the cold start, I restarted DCS and then went to the default cold start instant mission. As soon as the mission loaded, all lights on the warthog throttle turned off. I then turned on the battery and nothing happened. Turning on the APU - as soon as the APU light came on, all the other lights turned on. Personally I prefer the old way where the lights come on with the battery and then just the top LED for the APU, but either is fine. The problem is when shutting down the plane, the warthog throttle lights no longer turn off. I also tested it by doing a cold start, turning on the battery and APU, waiting for the lights to come on, and then turning off the APU and battery, but the lights stay on. When starting a new cold start mission, without restarting DCS, the lights just stay on. So in short, with the pre-release files the only time all the lights are off is when first starting DCS and starting the first mission.

@slughead Thanks for looking into it. I just tried the 2 pre-release files. When starting Target, the script seems to work, but as soon as I start a cold start mission, the script stops with the following error: "Runtime Error: Index out of bounds for: packet in set_fa_18c_hornet_led_status (line 25 in fa-18c_hornet_led_utils.tmh) Aborting script Script stopped!"

@slughead I found one possible problem with the F18 and warthog script for the cold start. When I start DCS with the script running and start a cold start mission, it works fine. The lights are off until I turn the battery on. But when I start a second cold start mission, the lights start being on. I can turn the lights on and off with the battery switch, but initially they are on already. So each time I start DCS and do the first cold start mission, it works fine. But any following cold start missions, it starts with the lights on. I'm really enjoying the script. Just wanted to mention this inconsistency. Thanks!

The AI controlled F18 has a boarding ladder when the the wheel chocks are applied. @BIGNEWYCan this be added for the player controlled F18 too? I started "walking around" the F18 for pre checks and after the flight and having a ladder that appears and disappears would be very cool. Thanks!

Another suggestion for the F18 warthog script. When preparing to land and lowering the landing gear, the gear handle turns red until the landing gear is fully down. Could this be simulated with one of the LEDs on the warthog throttle? How about using the bottom LED as a landing gear indicator, then the next 3 for the speed break, and the top for the APU?

@slughead This is great. Makes such a difference. Thank you!

I just updated the Target software and now it works. Thanks! I was thinking about options to improve the cold start for the F18 and warthog throttle. Is it possible to use the battery switch for the background lighting level? Have the background lighting level off when the battery is off. Then when you turn on the battery, turn it to level 1. When shutting down the plane, the last item is to turn off the battery, which could then also turn the background lighting level off. I really like the new APU option. Using the battery in this way could improve immersion even more for cold starts.

@slughead That's a great addition for the F-16. Makes a big difference when starting the plane. Thank you! I also tried the F-18 with the warthog throttle and really like the APU light. This is great. I did notice that the lights no longer turn off when turning off the engines. Can this be changed back? The previous version seemed more immersive when starting cold and dark. Also, when I used the new script I got the following error: "Runtime Error: Symbol not found: AVA_F16 in main (line 37 in TMHotasLEDSync.tmc)" After removing the lines with AVA_F16 and AVA_F18, it works again.

Hello, I just bought the campaign. Thanks!

@Desertdawg Not related to the script here, but I had a similar problem with the Ava base not getting recognized in DCS. I solved it by installing Joystick Gremlin (https://whitemagic.github.io/JoystickGremlin/) and mapping the Ava base to a virtual controller. Then in DCS, you get a new virtual input device and can map the controls from the Ava base to it. What I do now is to 1. start Target for light script, 2. start Joystick Gremlin for the Ava base, 3. start DCS. It's a bit involved but may help. Good luck.