Newcomer / Intro T.A.R.G.E.T. Software (maybe useful) tipps - T16000 FCS Hotas

Greetings Commanders.

Preamble:
(Win 10 1803; T.A.R.G.E.T. 3.0.18.328)
I was using the Hotas X before and as I ran out of analogue controls I got myself a T16000m FCS Hotas.
First I just pluged and played, mapped all the buttons and controls and was happy. Then I thought to myself: "hmm what about that TARGET Software..." and took a look at it, watched some videos about it and decided "that sounds pretty nice". Finally downloaded and installed it. Went through the config with all the nice curves and deadzones and ran the profile. I was Aware I had to map the keys again but I thought it should be worth it...
To shorten the story a bit: after some attemps to get it working in ED I was frustrated, quit trying and used the T16000 without the TARGET Software. But still, it bothered me and so I started again with try and error.

To maybe spare some of you with the same frustrating Moments I had, I thought it could be useful to avoid some misunderstandings and mistakes using that software.


Interesting part:
The TM T16000 FCS Hotas are a Flightstick and a Throttle device. They are working as two seperate devices and as such they are recogniced in ED. So you can map the keys simply and even if you have 'JOY 1' by pressing the primary fire on the Stick and 'JOY 1' by Pressing the orange thumb key on the throttle, ED treat them seperatly because it's from two different devices.
Once you start a profile with TARGET you'll get a 'Thrustmaster combined' device. And it is what it says: Stick and Throttle are now counting as one device and ED treats it as such. So now you'll have an overwrite and 'JOY 1' is just 'JOY 1' with no difference between Stick and Throttle.

Step by Step:

First thing you want to do, is to make a backup of your custom binding (just in case).
You should find it in: ~/users/whateverusernameyouhave/AppData/local/Frontier Developments/Elite Dangerous/Options/Bindings
If you can't find the 'AppData' folder you should check your Windows folder options if you have 'show hidden folders and files' turned on.

Now just start the TARGET GUI, create a new configuration and remember (or better write down) where the .fcf gonna be saved in, because you want to make a backup of that file too once you're done with all the configuring.

In this GUI Screen you have to make sure you have unique designations for each analogue axis (or you'll get the same override Problem as with the keys)
TARGET_1.jpg

In the next GUI Screen follow the steps for each key on the throttle.
The flightsticks POV Stick isn't assigned with any functions so you have to assign them manually. The other 16 keys are as they are in the original mapping.
On the throttle keys you have to start with DirectX button 17 as the flightstick uses keys 'JOY 1' to 'JOY 16' and you'll have to do it with every single one (screenshot below)
Because you will run out of DX assignments you'll have to use some Keyboard keys (I used F1 to F4 for the Throttle POV Stick)
TARGET_2.jpg


So once you have done all the assignments you have to save it and run the profile. Maybe check with the Joystick Control Panel if all the Buttons and analogue controls are working as intended.
Start the game.
If you're now wondering why there is no 'Thrustmaster...' in the controls to choose: Think About it. You've created a virtual device with millions of possible Layouts. So you have to choose 'Empty' and map everything yourself.

Don't Forget to make a backup of your .fcf (TARGET Script file) once you done all the tuning of your curves and deadzones.

If you want to make changes in the curves, you should Exit the game and stop the profile. If you don't leave the game there might occure some troubles afterwards. So just to be on the safe side: Exit ED first.


Hope this helps

Greetings Earthlings
M3110w

P.S.:
My TARGET Script file (if you want to use it, feel free)
Open it with Notepad (or something like that) and save as… .fcf
View attachment CMDR_rootMellow.xml


P.P.S:
Maybe some moderator can move it into the guides section - once this prooved helpful
 
Last edited:
That was an interesting read.
I like the TARGET software, but that might be because I used to write software, I think some people will find it over-complicated.
I always promised myself I would write some macros - but never got around to it.
Although I have two different .fcf files for different ships.

Once in a while I forget to run the TARGET GUI before I start and discover my joystick doesn't work when I'm heading for the letterbox on the way out of a spaceport, but otherwise it's fine.

I got started by downloading a profile from Thrustmaster's website, and then messed about with it until I got a version I liked.
I also found a library of macro files which I was going to play with - but I've lost the link.

If I get snowed in again for 6 days - like last year I might have another look at it.
 
does anybody has an idea why my properly installed thrustmasters aren´t recognized by the game ?
i own this saitek x52 too, even that one is not recognized.
i´m clueless...
 
does anybody has an idea why my properly installed thrustmasters aren´t recognized by the game ?
i own this saitek x52 too, even that one is not recognized.
i´m clueless...

TARGET ... ;)

Well, if you have USB game controllers that are recognised by windows then E D should have no issue with them. The problems people find usually stem from things like the controller software (giving custom mapping / emulating keypresses etc). Two other things that are notorious are VJoy and any piece of Saitek driver spam luring in the machine. :)

I have five different game controllers with bindings in E D - 2 TM MFDs CHPro Throttle and Fighterstick plus a MS game pad thingie - I have no controller software installed and have never had an issue. I can even plug in a Logitech 3D joystick and use that for pew-pew (with the others still plugged-in) using a separate binds file.
 
Last edited:
Hi R1ZZ0

So ED isn't recognizing any of your Sticks?
Did you try to use in Controls 'Empty' and try to set the mapping completly yourself?
If you are using the TARGET Software you have to choose 'Empty' (follow my hints in opening post)

Maybe it helps to install the latest Drivers and Firmware from Thrustmaster
https://support.thrustmaster.com/en/cat-joysticks-en/

Other thing i've read several times searching for my own issue, that if you are using steam you have to disable Controller-Input for ED.

Hope this helps and you get your troubles fixed


Greetings
M3110w
 
does anybody has an idea why my properly installed thrustmasters aren´t recognized by the game ?
i own this saitek x52 too, even that one is not recognized.
i´m clueless...

And by not recognized you mean that they cannot be mapped in controls (nothing happens when you press the keys) or just that the preset isn't loaded? Or they were recognized but suddenly stopped working? Then it might be a case where you had more devices when you configured or device id changed somehow, and that will render your binds unusable. There is also a helpful "bindingloadingerrors.log" file in the folder with the binds, might be worth a look.

As for TARGET software, it's the most lazy thing ever - to push programming of the controllers to the users and not filling controller properties in device control panel. For example there could be an option to make pedals combined. But no, you have to use target which renders your whole config unusable because it creates a virtual device. All while it could be changed within the throttle properties to which pedals bind...

I get that you can do some nice scripts with it, but it should be an extra, not a requirement to control how the device behaves.
 
I get that you can do some nice scripts with it, but it should be an extra, not a requirement to control how the device behaves.
Yah it's not necessarly required. The T16000 works just fine without TARGET (in my case)
But I wanted to configure the curves and outer deadzones, so in that case it is necessary. And yes I would pretty much appreciate it, if one could set curves and outer deadzones within the driver settings.

There is also a helpful "bindingloadingerrors.log"
Yah, forgot about that.
It can be found in
~/users/username/AppData/local/Frontier Developments/Elite Dangerous/Options/Bindings
 
Yah it's not necessarly required. The T16000 works just fine without TARGET (in my case)

Yeah, plug & play works, but there is literally no control over the hardware without programming scripts in target. For example try to make a single axis from the TFRPedals to use it in SRV. No option in driver settings whatsoever, while my really really old Driving force GT wheel had a necessary checkbox present. It's not that uncommon.

Also "fer chrissake" setting the device name to thrustmaster combined is another example of being lazy. Why cannot it just change the properties of the device? Probably for the same reason those aren't present in settings. It's just lazy programming, that's what it is.
 
Sure you don't need TARGET, but you can do soooo many cool things with it.
I originaly just installed it for the curves, but then I started to browse through the target-script manual, and got some fun ideas.
Now I have a hugh script with lots of crazy function, macros, button combinations and much more.
But I guess it something for people who knows how to programm, or are at least not scared of writing their own script.
 
But I guess it something for people who knows how to programm, or are at least not scared of writing their own script.

I write software for a living, I am caling lazy when I see it. And the implementation of forced "combined device" is atrocious because imagine binding everything in Elite again just because you want to change how 1 axis behaves. It's silly.
 
+Rep Thanks for the great write up.

I got a T16000m HOTAS over the holidays as I also found thee T Flight HOTAS X had too few inputs, but not yet ready to take on Taget ;-)
 
Last edited:
Back
Top Bottom