slughead

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.

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.

Excellent. Thanks for your thorough testing and clear reporting. I will try to get a formal release out this evening. Enjoy!

@CM2024 Try these. led_utils.tmhTMHotasLEDSync.tmc

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.

@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.

Right ok. Thanks for the thorough test and explanation. I will have another look at this.

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.

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. 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.

Thanks for the report. I'm just sitting down to work on the F-18 script now so that was good timing.

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.

Graphics. HUD Symbology affected by engines heat blur effect - fixed The team must be running out of things to do! It's nice to have this finally done though.

What’s in your export.lua file? Post it and I’ll take a look. dcs2target stopped using export.lua a long time ago.

Please follow the troubleshooting section in the first post of this thread.

Unpair the devices in Windows, then repair them. Pair only one at a time, or Windows will get confused. You will then see two new devices in joy.cpl and DCS. I can't do anything about the device names in joy.cpl or DCS. This is a limitation of Windows and the BLE protocol/API.

The NVidia 572.75 hotfix solves this problem. GeForce Hotfix Display Driver version 572.75 | NVIDIA

@CM2024 Your wish has been granted. You need both the new dcs2target and TMHotasLedSync updates.

I expect what you have seen on YouTube is out of date. They rarely update their videos to match software changes. I would always advise going direct to the developer (in this case, me), their website, GitHub page, Discord channel, or thread on the forum. If you need help, comment on the thread I linked above. PS. A new release added new features yesterday, and there might be another for F-18C/Warthog users today.

Yes, I think that is achievable. If I get some time this evening, I’ll try to get this added. Perhaps also take a look at adding similar support for APU and backlight level on battery to the A-10 too.

I don't recall when you bought your Slugmouse, so I can't tell what firmware version yours would have. Anyway, the latest firmware, sold from 20th October 2024, allows you to set the Slugmouse to be a mouse or joystick/gamepad. If you set it to be a joystick/gamepad, the buttons become additional joystick buttons. Then, you should be able to map them to anything you want, including mouse buttons (I think). If you have an earlier version, I can provide the firmware and uploader to upgrade your Slugmice.

Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0412" That's your ViperTQS. Try performing a "Check for Update" in the Viper TQS control panel. Also, make sure you are using the latest version of the Thrustmaster TARGET software.

I think if you have a tobi eye tracker it would work. The Slugmouse itself doesn’t track hand movements.

That’s why people use the Slugmouse. Fingers and hands look good, but are terrible unreliable. Slugmouse gives you hand tracked cockpit clicking. It’s like having a mouse on your fingers. Point and click. See my signature for details.

I expect you are running an old version of the Thrustmaster TARGET software released before the AVA base was available. Hence it doesn't know about the AVA base symbols. Can you update the TARGET software and see if that solves your problem?

See below. I will have to see what I can do to make it more universal for those who do not have the AVA base.