TARGET Script not Hiding Individual Controllers

[speedbird5]

Hi all,

 

I have a TARGET script which used to combine both my TM Throttle and Joystick into one device and used to hide the individual controllers.

 

Now, the script creates the Thrustmaster combined device but does not hide the individual controllers which causes havoc with controller mapping in many games.

 

I am on windows 10 x64 version 1909 with everything up to date using the latest versions of TM driver software and TARGET script.

 

I have tried the following to no avail :

 

Updated motherboard chipset drivers.

 

In device manager on both USB devices and Human Interface Device controllers unchecked the "Allow the computer to turn off this device"

 

Uninstalled and reinstalled the driver and target software numerous times.

 

The only fix seems to be reboot or unplug and replug the controllers but this is a PITA.

 

Any help greatly appreciated.

 

 

EDIT: I think I may have found the solution...full credit to Clorydric at this post https://forums.eagle.ru/showpost.php?p=4050109&postcount=15

 

Kill the Windows Store app.

 

You can do this through task manager directly or by creating shortcut to:

 

taskkill.exe /f /im winstore.app.exe

Edited February 1, 2020 by speedbird5

[Ant0ine]

 

Good luck.

[speedbird5]

Thanks Ant0ine, see my original post above for a suggested solution.

 

Perhaps we could make this a sticky ?

[Ant0ine]

Thanks Ant0ine, see my original post above for a suggested solution.

 

Perhaps we could make this a sticky ?

 

Good find, I learned about this windows store issue not long ago but I didn't think it was related to your issue. :doh:

 

https://forums.eagle.ru/showpost.php?p=3925050&postcount=20

 

A little sticky in the Thrustmaster section could be nice indeed, with this issue, also the TeamSpeack joystick plugin, and also maybe the target release note saying it is important to disconnect controller before installing target..

[speedbird5]

Yes agreed this issue and the Teamspeak issue to be made sticky.

[Baryum]

The fact that it doesn't hide the individual controllers can be seen as an advantage, though.

 

With the virtual controller, you are limited to 8 axes so you lose several axes from the combo, joystick + Throttle + Pedals.

 

I would have to check if it works but you could use TARGET for the buttons (sequences, short/long press, etc.) and keep the individual controllers for the axes. Of course you need to properly unmap the unused part of the controllers. Has anyone given it a try?

 

Cheers !

[VpR81]

Yes agreed this issue and the Teamspeak issue to be made sticky.

 

Teamspeak issue? Never heard about it. Do you have a link?

 

The fact that it doesn't hide the individual controllers can be seen as an advantage, though.

 

With the virtual controller, you are limited to 8 axes so you lose several axes from the combo, joystick + Throttle + Pedals.

 

I would have to check if it works but you could use TARGET for the buttons (sequences, short/long press, etc.) and keep the individual controllers for the axes. Of course you need to properly unmap the unused part of the controllers. Has anyone given it a try?

 

Cheers !

 

Just out of curiousity, why would you include the pedals into your Target profile, while axis are mapped in DCS anyways? IMO there is no need for that and pedals can be excluded from the profile without missing any functions. Correct me if i'm wrong...

[=Panther=]

Teamspeak issue? Never heard about it. Do you have a link?

 

If your Teamspeak locks up your PC while TARGET is running, the gamepad/joystick plugin was causing it, not 100% sure but I believe that bug was fixed.

[VpR81]

Thanks for the informations. I'm going to take a look into this though.