slughead

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.

Sadly, this year, I will be giving the taxman lots! A change of job has pushed my salary beyond the realms of regular tax returns! I'm not complaining.... ok, I am. I don't have the room for a dedicated "cockpit" setup, which is why I developed the Slugmouse. It allows you to point and click with your hands rather than reach for a mouse. It's the closest thing to actual cockpit interaction without a physical cockpit and passthrough. It's probably a good thing that I don't have the space, or I would be spending a small fortune in gear!

Happy Birthday! Did you get any flight som treats? A WinWing ICP perhaps?

Yes. The other file is misnamed, although the file's name shouldn't matter. I will correct it.

Please make sure you are using all of the files from the zip files. Some have changed and some haven’t. So best to replace all of them.

You’re welcome! Enjoy!

You will need both.

New release! New features! The following F-16C lamps will be replicated on the second column of LEDS from top to bottom: JFS RUN MAIN GEN STBY GEN FLCS RLY EPU RUN The following F-18C lamps will be replicated on the first LED, with the lower four LEDs indicating the speed brake position. APU RUN Note that the Warthog minimum background lighting level will be level 1 instead of off. Otherwise, the column of LEDs will always be off when the console lighting dial is set to off or the generators are not producing power. I will add other indications for the F-18C and the A-10C/A-10C2 soon. Let me know if you have any suggestions for the F-18C and A-10C LEDs.

That's good news! I will check the change into github. The virtual game controller vs combined controller might just be down to a newer driver; yours potentially being newer than mine. I'd not worry about it.

The thread for the script is here: Read through the thread and see if your problems are answered. Also, read the instructions on the GitHub pages. Simapp pro has nothing to do with my scripts. They are entirely mutually exclusive.

@Desertdawg @Red Panda Can you try this new script please? Rename your old copy of the file so you don't overwrite it, then copy this file to the same folder and give it a whirl. TMHotasLEDSync.tmc

Hmm. I have the F-18 and the F-16 stick. I haven’t tried the scripts with the F-18 stick attached. I will give it a go and see if that replicates the problem. What stick are you using on your AVA base?

No. My scripts do nothing with the joystick axis. Yes, I mentioned that a couple of replies back. You need to speak to Thrustmaster as the creation of the combined controller is all done internally by Thrustmaster. It’s their bug. Thrustmaster forgot to provide any control over the backlight/console brightness for the Viper. I have asked them if they would add it when I was in contact with the development team. That was a good year ago so I wouldn’t hold your breath.

Is your Windows account an admin account or a normal user account? Have you tried running the Thrustmaster software with admin privileges?

Mine looks like this when the script is running: I get the "Thrustmaster Combined," which is created by Thrustmaster when the script is executed, but I also retain the AVA Base. Please speak with Thrustmaster for assistance.