New Thrustmaster TARGET problem

[Daveyboy]

I started up ED for the first time in ages yesterday and although there were several new mappings required for things like full spectrum scanner and the new analysis/combat modes, everything relating to TARGET seemed fine.

Not sure if there's been a change / update to TARGET or to ED but today for some reason I'm getting duplicate inputs for every button I press. The target software is creating the combined input device (for stick + throttle) but leaving the original stick and throttle controllers there as well (I can't remember if it used to do this or remove the original controllers when a profile was running). Anyway, Elite is now picking up the input from both the combined controller and the individual one. So if I press any of the buttons on the stick it sees the button on the stick, plus the button on the "stick and throttle".

Wondered if anyone else is using target and has the same problem. My guess is it won't be an issue for existing controls and only when changing the mappings. I was planning on rejigging some of the mappings tonight due to the various new controls that need to be mapped up.

[moonpiespotlight]

I stopped using TARGET with my TM about a day after I installed it. Most people I know don't use it.

[Daveyboy]

Fair enough. Well it did work for me for ages anyway, and it gives better options on things like the axis. TBH though the main thing I use it for is just so I can use the mini-throttle on the joystick as a switch to keep my mining laser on.
Not sure if the change in behavior is caused by an ED update, Target update or Windows update but I may be able to work around it somehow. But because things like simply pressing the joystick trigger is now showing as Button 1 + Button 1 rather than just Button 1 it means I'm not getting alerted to conflicts unless I go through every single mapping.

[Daveyboy]

I did just find this topic on the issue: https://www.reddit.com/r/hotas/comments/7681ni/tm_target_not_combining_sticks_duplicating_inputs/

... so it seems the issue has been around for a while, funny it only started affecting me today. Oh well I'll continue to hunt for a solution.

[Daveyboy]

Solved: For me anyway, was fine after a reboot. Guess I should have tried that first lol