Thrustmaster Combined only with TARGET
-
Newbie question here.
Windows 10
Throttle - HOTAS Warthog
Joystick - HOTAS WarthogThese two appear as the two devices in Game Controllers window before TARGET script is run.
I launch TARGET, run the script, the two above disappear and Thrustmaster Combined appears as the only controller.
I the CLOSE the TARGET window and the Combined disappears and the two (Throttle & Joystick) appear again.
Is this the way its supposed to function ? i.e. before launching Falcon 4 I run the script each time to get the Combined device as active and then leave TARGET open in the taskbar so I don’t loose it ?
Thurstmaster latest drivers installed, downloaded from TM website and instructions of installer followed when executing it.
-
Newbie question here.
Windows 10
Throttle - HOTAS Warthog
Joystick - HOTAS WarthogThese two appear as the two devices in Game Controllers window before TARGET script is run.
I launch TARGET, run the script, the two above disappear and Thrustmaster Combined appears as the only controller.
I the CLOSE the TARGET window and the Combined disappears and the two (Throttle & Joystick) appear again.
Is this the way its supposed to function ? i.e. before launching Falcon 4 I run the script each time to get the Combined device as active and then leave TARGET open in the taskbar so I don’t loose it ?
Thurstmaster latest drivers installed, downloaded from TM website and instructions of installer followed when executing it.
Yep! Run the TARGET Script and leave it running.
-
When you say you “…run the script.” what do you mean? I have just taken delivery of a Warthog and I have not managed to find out how to get Thrustmaster Combined up on my devices in game.
I admit that I haven’t read the TARGET manual yet and am leaving myself open to a bit of forum slapping, but any instant help would be welcome.
-
There are two programs for TARGET, TARGET script editor, and TARGET GUI editor. If you don’t have them go to the support website download and install them.
The script editor will run a script that will map from the physical controllers to a virtual controller. The GUI program is just a pretty user-friendly front end which writes the script for you. The script defines what button corresponds to what output. Button1 will output a keyboard keystroke ‘A’, Button2 will output DirectX button 6, Button3 will move axis Z increased by 1%, that sort of thing. Scripts are written by you or someone else usually specific to a game.
Devices can be excluded or not excluded from the TARGET virtual controller. Excluded devices will appear as the same controller as if TARGET is not running. Not excluded devices will be available as input into the TARGET script which drives the virtual controller and will not be available normally. The decision to exclude or not exclude a controller from TARGET depends on if you want script-level control over its behavior or not. The drawback to not excluding all controllers is that the virtual controller is limited to 8 axes, 1 POV, 32 buttons just like any other DirectInput device.
Playing BMS for example I start TARGET script editor, open the script file made for that game, and press the green play button. If I play a different game I load a different script and stop/play. Occasionally I don’t want TARGET’s script control and just run the bare devices.
-
Within target there upper, middle & lowe command sections. Plus within these sections you can have layers. Giving multiple possibility for commands