TARGET Software issues
-
I posted this in another topic about TARGET with my Warthog but would like anyone’s feedback on it:
++++++++++++++++++++++++++++++++++++++++
Actually should point out one thing about the warthog.This issue is serious.
You may find TARGET software doesn’t work all the time. Initially I was using TARGET with the Warthog and an extra stick the T16000m (Evochron Legacy) and it worked every second time without fail. Possibly due to a Windows 10 update (I don’t know) it worked only once every 50 times so I stopped using it for that and use direct instead but have lost some functionality (eg dead zones).
I have since yesterday been running using the script editor instead for just the warthog (morphine’s script) and it works again every second time.
I Will post this elsewhere on this forum, just wanted to let you know.
+++++++++++++++++++++++++++++++++++++++++Does anyone have these issues or can contribute on the ones below?
I read in April on this forum that they have to unplug and plug in first the throttle and then the stick on every boot.
I also read if you leave it plugged in when not in use too long you will eventually need a 54 euro PCB board replacement.
-
Yes, and here is the solution to your issue, I hope. This is a post I wrote some time ago, on another forum. Copying it here for posterity
If you are having TARGET issues, this might help.
Description of the issue :
TARGET Script takes a long time to load, and the physical joystick and / or throttle are still connected and functional after the script is loaded, on top of the virtual “Thrustmaster Combined” controller.Warning : The script has to be properly coded and both joystick and throttle need to be included for the explanation below to be valid.
Concerning the USB ejection issue during script loading :
This process is handled by “DeviceManagementApp.exe” located /Thrustmaster/TARGET/x64
This can be blocked by various processes, like for instance the TeamSpeak Joystick add-on, but not only, and even Windows Kernel processes might be the source of the issue.
One solution is to remove or rename this executable, and the TARGET script then won’t eject the joystick and throttle, but will still add the virtual controller “Thrustmaster Combined”.
You can then map only that last controller in the game, and ignore the buttons & axis of the physical joystick and throttle.If the above is not satisfactory, we need to take it one step further :
Discovering the process at the origin of the issue :
1 - What are the game controllers connected to the computer
Start menu -> Execute (depending on which version of Windows you have, I’ll let you handle that one)
Type in “joy.cpl” and executeThis is the list of the game controllers connected to your computer. YMMV.
Now launch the TARGET script. If it takes time to load, like below, there is probably an issue :
Once done :
Now look at the connected game controllers again. Two options : only Thrustmaster Combined (OK) or Thrustmaster combined and joystick and/or throttle (Not OK)
Script worked :
Script did not work (could not eject a physical device) :
2 - Finding the process preventing TARGET to eject the device
Start menu -> Execute (depending on which version of Windows you have, I’ll let you handle that one)
Type in “eventvwr” and executeNow go to Windows Journals -> System
There you should have some errors on top of your list. Select the first one and see what it says.
In the description you should see what process is preventing the ejection. See what it is linked to and if it can be killed or not…
Then use CTRL+ALT+SUPPR or simply quit the application, I’ll let you handle it from here on.Example of the TeamSpeak Joystick add-on making trouble :
In that preceise case, quit TeamSpeak, run the script, and reload TeamSpeak.
Good luck on the troubleshooting !
-
Windows store for instance blocks the USB ejection for some reason.
-
Wow, thanks so much will try it when I get home
-
This seems a good place to ask: What about the BMS Alternate Launcher, and bypass TARGET?
-
Alternate Launcher isn’t magic. Can’t use throttle POV, can’t make axis behave like button or button like axis. Sure you can avoid TARGET scripting and still fly BMS but some possibilities are off the table.
-
I tested all the above Flow put up.
I put a shortcut to system32/joy.cpl (something like that) on the desktop to easily test.
Anyway I have no errors in the event viewer.
Instead what I have is that after running the target script the first time it doesn’t work. The joy.cpl shows:
- only the combined Warthog shows (good)
- throttle works (good)
- stick doesn’t (bad)
So I stop it and run it again and it all works.
What bothers is me is this is what happened with the TARGET GUI software then at some point it stopped working (a lot of testing - hundreds of times - over a number of weeks).
Is the same thing going to happen with the TARGET Script software?
I originally emailed support at thrustmaster but they did not answer.
As it seems to be working every second time I will just use it until it stops altogether.
Good to know there is an alternative out there when that happens.
-
I get the same. I have to unplug/replug certain controllers and if I unplugged a controller included in TARGET device, re-run the script.
-
Ok that is something I should have tried first before giving up, thanks.
-
Alternate Launcher isn’t magic. Can’t use throttle POV, can’t make axis behave like button or button like axis. Sure you can avoid TARGET scripting and still fly BMS but some possibilities are off the table.
Can you provide more detail for a newbie re: can’t use throttle POV? If someone was using TrackIR, would he even need to use the throttle POV to provide view movement. In that case wouldn’t the throttle POV at least be programmable with Alternate launcher for other purposes?
-
Can you provide more detail for a newbie re: can’t use throttle POV? If someone was using TrackIR, would he even need to use the throttle POV to provide view movement. In that case wouldn’t the throttle POV at least be programmable with Alternate launcher for other purposes?
BMS won’t recognize the hat switch on the second joystick. Nothing can be assigned to it unless outside software is used.
-
BMS won’t recognize the hat switch on the second joystick. Nothing can be assigned to it unless outside software is used.
This is still hazy to me.
If you have 1 Warthog FCS joystick are you saying that a hat switch on the Warthog throttle won’t be recognized? (I believe there’s a hat switch on the Warthog throttle, not sure, mine hasn’t arrived yet, but the specs led me to believe it has one)
-
This is still hazy to me.
If you have 1 Warthog FCS joystick are you saying that a hat switch on the Warthog throttle won’t be recognized? (I believe there’s a hat switch on the Warthog throttle, not sure, mine hasn’t arrived yet, but the specs led me to believe it has one)
Both devices, the throttle and the joystick, have hat switches. If two devices with hat switches are plugged in, BMS will only recognize only one of the hat switches. You will not be able to bind functions to one of the devices, unless you use a target profile.
-
Both devices, the throttle and the joystick, have hat switches. If two devices with hat switches are plugged in, BMS will only recognize only one of the hat switches. You will not be able to bind functions to one of the devices, unless you use a target profile.
Thanks. Nice to know.
edit> This explains why the “BMS Key File Editor.xls” found elsewhere on this site doesn’t have anything assigned to the Warthog Throttle Hat switch.
-
Finally got my Warthog HOTAS and decided to just drop the hassle of the “Target” software as suggested for now.
I’m trying to set things up with the Alternate Launcher, but I can’t seem to get the Stick:Pinky Switch and/or the Stick: Pinky Switch DX Shift to work correctly. Any pointers on what the input box(es) are supposed to show?
example:
-
I am not at a computer with a joystick attached, but I have access to the alternate launcher so I pulled it up and will see if I can remember how to do this. I get an error with your attachment and cannot see what you posted so I cannot reference that.
- Open the Alt Launcher and go to “Key Mapping”
- Type “shift” in the search bar
- Double click on the line that says "STICK: PINKY SWITCH (DX SHIFT)
- Click “CLEAR DX” button to clear any existing button assignment
- Then click the appropriate button on your HOTAS that will be your pinky switch/shift button
- Click “Save”
- This will assign that button as the shift button
To assign the shift functions to other buttons, you will just enable the shift layer when setting it up. For example:
To set up the shift layer on H4P (CMSPress) DX:18 CKPIT: Trim-Reset
- Navigate to “Key Mapping”
- Search “Trim-Reset”
- Double click the “CKPIT: Trim-Reset” function
- Click the “Keycombo/Pinkyshift” button to make it white in the dialog box
- Press the appropriate button on your stick to assign the button to this function
- Click “Save”
This function should now be activated when this button is pressed in conjunction with the pinky switch.
-
84hd79: Thanks. That did the trick for the Pinky Shift button usage.
Got another question if you got the time…
Several of the buttons have (CTR from Fwd) or (CTR from Back), etc. Example the Dogfight Switch on the Throttle going back to MRM/DF Cancel. How does that work? I presume it’s something to do with how the forward and back buttons are programmed, but how? Your help is greatly appreciated.
-
This one is little more difficult for me to answer because I do not have the Warthog or any switch like your dogfight switch on my HOTAS. All of my switches are press and release type buttons.
I believe that this is a 3-position switch on your HOTAS. So the “Boat Switch Fwd” and “Boat Switch Back” indicate when you are sliding the switch from the Center position to the Forward or Rear positons. The “CTR from Fwd” and “CTR from REAR” indicate the movement from the forward or rear positions back to the Center
<back rear=“”>–-
<center>— <forward>So Center to Forward would enable the MRM override mode
Forward to Center would cancel the override mode and return you to the mode you were in before you went into overrideCenter to Rear would enable the DOGFIGHT override mode
Rear to Center would cancel the override mode and return you to the mode you were in before you went into overrideSo how this will work with a 3-position switch, I am not sure…
But looking at the example for the Master Arm Switch, it may go something like this…
MRM Override | DX40 INV: DN
Cancel Override | DX40 REL INV: DN & DX41 REL INV: DN
Dogfight Override | DX41 INV: KEY DNSo when your slide our 3 Position switch to the MRM override (FWD) position, you would want the button that says “Invoke Both” in white to read “Invoke Down” Click that white button to change it
When your switch is in the Cancle Override position (Center), you would want both the “Realease” and “Invoke Down” buttons white for DX27 and “Release” and “Invoke Down” button white for DX28. This is the part that I am unsure about how to do exactly. I would slide the button FWD, double click the cancel callback, make sure both of the buttons are white, and then slide the button to the center and see how it registers. If it works, do the same thing from the rear positon to center
And when sliding from the center to the DOGFIGHT override (Back) position, you would again want the third white button in “Invoke Down” mode
That is how I would try it. If it does not work, maybe someone that has programmed a three position switch could chime in.
Mike</forward></center></back>
-
This one is little more difficult for me to answer because I do not have the Warthog or any switch like your dogfight switch on my HOTAS. All of my switches are press and release type buttons.
I believe that this is a 3-position switch on your HOTAS. So the “Boat Switch Fwd” and “Boat Switch Back” indicate when you are sliding the switch from the Center position to the Forward or Rear positons. The “CTR from Fwd” and “CTR from REAR” indicate the movement from the forward or rear positions back to the Center
<back rear=“”>–-
<center>— <forward>So Center to Forward would enable the MRM override mode
Forward to Center would cancel the override mode and return you to the mode you were in before you went into overrideCenter to Rear would enable the DOGFIGHT override mode
Rear to Center would cancel the override mode and return you to the mode you were in before you went into overrideSo how this will work with a 3-position switch, I am not sure…
But looking at the example for the Master Arm Switch, it may go something like this…
MRM Override | DX40 INV: DN
Cancel Override | DX40 REL INV: DN & DX41 REL INV: DN
Dogfight Override | DX41 INV: KEY DNSo when your slide our 3 Position switch to the MRM override (FWD) position, you would want the button that says “Invoke Both” in white to read “Invoke Down” Click that white button to change it
When your switch is in the Cancle Override position (Center), you would want both the “Realease” and “Invoke Down” buttons white for DX27 and “Release” and “Invoke Down” button white for DX28. This is the part that I am unsure about how to do exactly. I would slide the button FWD, double click the cancel callback, make sure both of the buttons are white, and then slide the button to the center and see how it registers. If it works, do the same thing from the rear positon to center
And when sliding from the center to the DOGFIGHT override (Back) position, you would again want the third white button in “Invoke Down” mode
That is how I would try it. If it does not work, maybe someone that has programmed a three position switch could chime in.
Mike</forward></center></back>
Evidentally, I’m doing something wrong on these. Can’t seem to find the right combo. Thanks and Regards, especially for the Pinky Shift help above.
edit> BTW, what filename and where does the ALT Launcher store the saved keystroke information?
-
I believe that the Alt Launcher saves the data to the BMS - Full.key that is in your User/Config folder.
There are also some Setup.v100 files in the Config folder as well that looks like are modified by Alt Launcher.
Have you checked the “Use 3-Way ON-OFF-ON Switch for DOGFIGHT” option at the bottom of the screen?
There is a video that was put out by the dev a few years ago. He goes through the process of setting up the dogfight switch, but it is kind of fast and no sound, and looks like it is from when he was developing the program. Maybe you could watch it and get an idea of what you need to do. He also shows the files that are being used.