slughead Posted March 22 Author Posted March 22 16 minutes ago, CM2024 said: 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? I’ll see what I can do! Maybe combine the bottom led with the speed brake. I might at some point design an indicator panel for landing gear lights, APU etc that connects via USB or Bluetooth and make it available as a product. 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
CM2024 Posted March 23 Posted March 23 @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!
slughead Posted March 23 Author Posted March 23 8 minutes ago, CM2024 said: @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! Thanks for the report. I'm just sitting down to work on the F-18 script now so that was good timing. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
slughead Posted March 23 Author Posted March 23 On 3/22/2025 at 1:48 PM, CM2024 said: 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? This has now been added. Warthog user LED1 will flash when the gear handle lamp is lit. The speed brake still uses LEDs 1 through 4 with LED1 combined with the gear handle. 5 hours ago, CM2024 said: @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! This should be fixed. Please use the latest dcs2target.zip (v1.0.11a) and tmhotasledsync.zip (v1.0.8a) This is a pre-release. Please let me know how you get on so I can formally release it should there be no new problems. 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
CM2024 Posted March 24 Posted March 24 @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 Posted March 24 Author Posted March 24 9 hours ago, CM2024 said: @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!" That’s usually the result of the DCS side not sending enough bytes. So it would sound as though you may have missed some files or forgot to update the DCS scripts. Both the hooks and dcs2target folders. Can you check and let me know how you get along. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
CM2024 Posted March 24 Posted March 24 @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 Posted March 24 Author Posted March 24 1 hour ago, CM2024 said: @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. Right ok. Thanks for the thorough test and explanation. I will have another look at this. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
slughead Posted March 24 Author Posted March 24 @CM2024 Could you try the following patches please? Place this one into your dcs2target folder fa-18c_hornet_lamps.lua And this one where you TMHotasLEDSync files are led_utils.tmh Both files replace existing ones. This should solve the problems you raised and also improved LED test on start and end of mission plus the Warthog backlight will be turned off when the mission ends. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
CM2024 Posted March 25 Posted March 25 @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 Posted March 25 Author Posted March 25 7 hours ago, CM2024 said: 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? Yes. That’s an easy one. Perhaps just turn them off altogether instead of doing the LED test? Just leave the LED test for when the script starts on the Thrustmaster side. 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
slughead Posted March 25 Author Posted March 25 @CM2024 Try these. led_utils.tmhTMHotasLEDSync.tmc Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
CM2024 Posted March 25 Posted March 25 @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 Posted March 26 Author Posted March 26 Excellent. Thanks for your thorough testing and clear reporting. I will try to get a formal release out this evening. Enjoy! 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
LoLevel Posted March 26 Posted March 26 Hi Slughead, please can you help me? I installed everything as described and updated the software, but unfortunately the LED does not light up. Do you have any advice? TMHotasLEDSync v1.0.8a.txt
slughead Posted March 26 Author Posted March 26 2 hours ago, LoLevel said: Hi Slughead, please can you help me? I installed everything as described and updated the software, but unfortunately the LED does not light up. Do you have any advice? TMHotasLEDSync v1.0.8a.txt 938 B · 2 downloads From the log: Error:InitSocketServer failed with 0x00002740 : Only one usage of each socket address (protocol/network address/port) is normally permitted. I expect that indicates that either two copies of the script are running or something else on your system is already using port 1000. If you reboot your PC and try again, that should eliminate any duplicate execution of the script you may have managed to do. If that doesn't solve it, try turning off all other software except the script and see if it works. If it does, you know something else is using port 1000. Then, shut down the script, turn on one of the programs you shut down previously, and start the script again. Repeat until you find the culprit. If that fails, your firewall might be blocking the Thrustmaster software, and you will need to enable it in your firewall, probably the Windows firewall. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
slughead Posted March 29 Author Posted March 29 Formal release Added F-18C gear handle lamp and mapped to flash Warthog user LED1. F-18C speed brake remains on Warthog user LEDs 1 through 4, with LED1 shared with gear handle lamp. Fixed F-18C issue where console lights would remain on for subsequent cold starts when the battery switch is set to OFF when entering the cockpit. Fixed the behaviour of lights when missions are restarted and aircraft are shutdown. Corrected LED test when script starts. LED test on mission end removed. Warthog console lighting and all indicators extinguished on mission end. Ethernet port number moved to a random port in user port space. DCS2Target is now at version: 1.0.11 TMHotasLEDSync is now at version: 1.0.8 Other versions of dcs2target/tmhotasledsync are not compatible with this release. You must only use the versions listed above. For support issues, read the first post thoroughly, then follow the "Need Help" section before requesting support. 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
JarrodR5 Posted April 10 Posted April 10 Hey~ Somehow i have encountered this error while tried to get the TQS led working: TMHotasLEDSync v1.0.8 Physical USB HID devices managed by script! Currently plugged USB HID devices[7]: 1: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200" 2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 3: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110" 4: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" 5: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 6: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 7: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" USB HID device with hardware id "VID_044F&PID_0404" cannot be found USB HID device "Viper TQS"(USB\VID_044F&PID_0412\3655327C3530) selected USB HID device with hardware id "VID_044F&PID_0413" cannot be found USB HID device with hardware id "VID_044F&PID_0416" cannot be found USB HID device with hardware id "VID_044F&PID_0417" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Script stopped! Done Device name set to Thrustmaster Combined Runtime Error: STOP request received while running main on line 65 in "C:\Users\Jarrod\Saved Games\DCS\ViperTQSLight\TMHotasLEDSync\TMHotasLEDSync.tmc" Error:Script run timed out! =========== I can confirm TARGET software and TQS firmware are all newest. Is there anything I could do to slove this? Many thanks!
slughead Posted April 10 Author Posted April 10 49 minutes ago, JarrodR5 said: Hey~ Somehow i have encountered this error while tried to get the TQS led working: TMHotasLEDSync v1.0.8 Physical USB HID devices managed by script! Currently plugged USB HID devices[7]: 1: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200" 2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 3: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110" 4: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" 5: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 6: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 7: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" USB HID device with hardware id "VID_044F&PID_0404" cannot be found USB HID device "Viper TQS"(USB\VID_044F&PID_0412\3655327C3530) selected USB HID device with hardware id "VID_044F&PID_0413" cannot be found USB HID device with hardware id "VID_044F&PID_0416" cannot be found USB HID device with hardware id "VID_044F&PID_0417" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Script stopped! Done Device name set to Thrustmaster Combined Runtime Error: STOP request received while running main on line 65 in "C:\Users\Jarrod\Saved Games\DCS\ViperTQSLight\TMHotasLEDSync\TMHotasLEDSync.tmc" Error:Script run timed out! =========== I can confirm TARGET software and TQS firmware are all newest. Is there anything I could do to slove this? Many thanks! Are you using a USB HUB? Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
JarrodR5 Posted April 10 Posted April 10 (edited) 3小时前，slughead说： Are you using a USB HUB? Hi slughead! Thanks for the prompt reply! Yes i am using an USB hub because of too many usb devices, wanted to tried to make it tideier. Shall i not using it? or are there any methods i can do to make it work without switching to direct plug? Many thanks! Edited April 10 by JarrodR5
slughead Posted April 10 Author Posted April 10 Always connect directly to the pc when fault finding. Not all usb hubs are equal and many cheap ones are poorly constructed and are electrically noisy. Connect direct to the pc then see. If it works, get a better hub or usb pci card. 2 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
CM2024 Posted April 12 Posted April 12 @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 Posted April 12 Author Posted April 12 8 minutes ago, CM2024 said: @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! Sure. I’ll see what I can do. 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
Freakmeister51 Posted April 13 Posted April 13 On 4/10/2025 at 7:30 PM, slughead said: Always connect directly to the pc when fault finding. Not all usb hubs are equal and many cheap ones are poorly constructed and are electrically noisy. Connect direct to the pc then see. If it works, get a better hub or usb pci card. Could you suggest a good quality hub please?
Recommended Posts