TARGET program joystick trouble

[WelshZeCorgi]

I am having problems using the target program.

 

For some reason, the warthog joystick doesn't always register with TARGET, so I have to fiddle with the windows recognition software to get it to work. But what's really frustrating is that when this happens, it completely erases all the buttons and axes assigned to the stick in DCS, even in the lua files, causing me to have to remap the buttons on the joystick whenever this happens, anyone know the solution, or what causes it?

 

I don't plug it into Usb 3.0 ports.

[Weegie]

I get a similar thing where I often need to rerun the profile before the USB port gets recognized. It always sees the throttle but the stick is hit and miss

 

TBH I'm not sure if I'm running USB 3 or not and it is on a hub, so shoulld I ever investigate it could well be down to me

 

However I've never had anything erased, if the stick isn't there on mine then TARGET will still combine the profile and everything on the throttle works

 

I assume you're aware that when TARGET runs, you run a different "combined" profile, when it doesn't run DCS sees the Stick as a standalone entry. So DCS isn't deleting anything, when TARGET is running it uses the TARGET combined profile. When it's not running the stick is standalone and runs on a different profile (apologies if I am teaching my granny here, it's just a thought)

EDIT

To make it clearer when TARGET runs, a combined profile is created and that is the only one that will show in the DCS controls page. The seperate Throttle(if you have it) and Stick profiles are combined by the TARGET virtual controller. Therefore when you run TARGET you will not see the individual device contollers for stick and/or throttle.

 

When you don't run TARGET the stick and throttle profiles will show up in the DCS controls seperately and the TARGET virtual profile will disappear

 

When I get the stick recognized it stays that way until I change profiles

 

Couple of things are make sure Micrsoft Store isn't running in TASK Manager Processes

 

When I compile TARGET I make sure everything else is disabled (like Voice Attack, Teamspeak etc, having anything else running usually prevents me ever getting the Joystick to be recognized. Once it is running I don't have a problem and all is stable

Edited September 24, 2019 by Weegie
Clarity

[SGT Coyle]

I am having problems using the target program.

 

For some reason, the warthog joystick doesn't always register with TARGET, so I have to fiddle with the windows recognition software to get it to work. But what's really frustrating is that when this happens, it completely erases all the buttons and axes assigned to the stick in DCS, even in the lua files, causing me to have to remap the buttons on the joystick whenever this happens, anyone know the solution, or what causes it?

 

I don't plug it into USB 3.0 ports.

 

 

Are you using the GUI or the SE(Script Editor)?

 

I don't know anything about the GUI, but I can share some best practices I follow with SE.

 

1. Add this to your script:

   Configure(&Joystick, MODE_EXCLUDED);    //Needed for F18 grip to work better.

   or

   Configure(&JoystickF18, MODE_EXCLUDED);    //Needed for Standard grip to work better.

   
   

2. In Windows Device Manager, check to see that power management is not checked for usb devices / root hubs
   
3. In Windows Device Manager, check to see that power management is not checked for HID devices
   
4. Unplug stick when not in use. Seems to work fine after plugging in
   

As for losing the bindings in DCS. I don't know. My DCS setting page has a column for "Thrustmaster Combined", that is the TARGET Virtual Controller, combining all your TM products present in the script. Allowing you to map DX_Buttons/Axis , not key presses, to DCS in that column. If you have mapped anything in there and hit the OK button at the bottom of the page, then it was saved. When ever your TARGET Virtual Controller is present, your bindings should be there.

 

If you see TM Joystick, Throttle, MFD..., column headings in the DCS settings/controls page, DCS is not seeing your TARGET Virtual Controller. For what ever reason.

 

Whatever you mapped under the TARGET Virtual Controller heading, as described above, will(or should) be there when DCS reestablishes the TARGET Virtual Controller.

Add this to best practices:

Never plug/unplug or run/stop SE script while the DCS settings page is open. That scenario has only worked out fewer times than the Sun has failed to rise in the East.

I hope this helps. I use TARGET a lot and see the issues you describe rarely any more. It mostly reappears after Windows Update.