Target Bug Solution
-
Issue:
The Teamspeak Joystick and Gamepad Addon prevents Thrustmaster’s target software from working properly. The teamspeak addon prevents target from hiding the physical devices from windows, thus preventing target to function properly, even after Teamspeak is closed.Solutions:
1, By removing the Gamepad / Joystick addon from teamspeak target works properly. 2, Hard reboot the system start target and run your profile before opening teamspeak. Both solutions have been tested effective on the latest version of target across multiple systems.Background
Thurstmaster Target Principles of Operation: Target functions by creating a virtual control and hiding the physical devices (joysticks) from the system. This allows the user to program the joystick to any number of virtual functions, keyboard commands, axis modification, ect.Since the Teamspeak Joystick and Game Pad addon prevents windows from hiding the physical devices, a profile will not work properly. You end up with phantom joystick buttons, ect. It fundamentally breaks target. The problem continues even when Teamspeak is closed. I don’t think the joystick addon ever fully shuts itself down when target is closed. Disabling the addon doesn’t seem to help either.
The problems began to appear a few patches ago when the addon was bundled with the basic install. It got worse with the latest release.
How to delete the Teamspeak Joystick Addon
Open Teamspeak, select tools->Options->addons (it’s on the left sidebar), Select the Joystick and Game Pad addon and delete it. Restart teamspeak and run your profile.If you need target and joystick push to talk, I would recommend Discord, it functions flawlessly with target.
-
+1 for sticky! But in general joystick section as Target can be used with other TM devices too.
2, Hard reboot the system start target and run your profile before opening target.
Shouldn’t the latter read teamspeak?
-
Yes, thanks will edit.
-
Nice Summary Gastone.
TeamSpeak must have updated their Gamepad/Joystick Addon as I am no longer having a problem.
OR
After running Target before Teamspeak at least once, may have reset something, somewere.
Either way worthy of a sticky.
Cheers.
-
Sorry for bringing bad news guys, but it’s not an universal solution: on my rig I am running the latest version of TeamSpeak and deleted the joystick addon, but the anomaly is still present… sometimes it works, sometimes not.
-
I was going to post “me too” since had the error with TS3 but just now I tested it with TS3 running and could start-stop TARGET successfully. The difference was a hard boot since.
-
I was going to post “me too” since had the error with TS3 but just now I tested it with TS3 running and could start-stop TARGET successfully. The difference was a hard boot since.
Thanks, I will try and report… in fact, after I tried yesterday when I powered my rig off I heard the typical sound when you plug a new device and at the subsequent boot I was notified that a ‘Compatible HID device’ had been set up and was ready for use.
Maybe it is in some way “time sensitive”, or maybe it’s simply a question of
, who knows. :rofl:Nulla Dies Sine Linea
-
It’s not “who knows”
It’s “who forking knows”
I had this problem for months, and then found the TS3 sequence solution, but now I can’t force the issue.
Me thinks It might be sloppy USB standards implementation.
-
Thanks, I will try and report
OK, I tried and can confirm that an hard reboot solves the matter. :woohoo:
I think we can finally consider the problem solved, just start TARGET before everything else if you plan to use it. -
Since removing the TS3 addon (and a hard boot). I cannot get the error to reoccur. I’ve been deliberately starting and running TARGET after starting TS3 every time (even when I don’t want to use TS3) and it’s smooth sailing.
