T16000M Hotas Issue

[Butterlord]

Having a really specific and annoying issue with my new Thrustmaster T.16000 M Hotas.

So I'm completely new to flightsticks and I've tried it with four different games now and the games will always auto detect either my throttle or my joystick but never the entire hotas, I always have to manually set up either my throttle or my joystick and no game will ever detect both. Elite for instance detects my throttle 100% fine and provides me controls for it but doesn't map anything for my joystick. it seems like it has to do with where I plug it in but I honestly have no idea as all of my USB ports are working and my computer detects both sticks fine.

I've already downloaded the latest drivers of the TM site, I've tried messing around in the Smart config/launching custom profiles with no luck and I've also already checked to make sure that Steam generic controller is disabled.

At this point I'm at a complete loss at what could be causing the issue, really don't feel like having to manually rebind the controls for every game as I have no idea what I'm doing

[Bubba Fett]

I've got the same hotas and if I remember right, there was a preset for it in the config. I've tweaked a lot of controls, but I know it set stuff on both the stick and throttle when I first got it.

The only weird issue I ever ran into with it was button 2 on the stick sometimes muting the sound on the computer. Didn't do it all the time and I never found a solution. I finally just mapped secondary fire to button 3 on the stick.

Not sure what would be causing your problem though. Try starting the game with the stick and throttle unplugged, then restart with just the stick and see if you get controls in the game, then add the throttle and start it with both.
I'm wondering if Elite is seeing the throttle first, thinks the axis on that are a stick then it sees the stick and doesn't know what to do with that.

[Randalehörnchen]

Sounds like the problem I had just a few days ago.
Using the TARGET software from Thrustmaster with the provided profile for the FCS Hotas layout, the throttle worked fine, but the stick itself didn‘t respond to any input.

Following the guide from post 6 of the forum link sorted out all problems:

https://forums.frontier.co.uk/threads/thrustmaster-t16000m-fcs-hardware-problems.421485/

[Butterlord]

Originally posted by Randalehörnchen:

Sounds like the problem I had just a few days ago.
Using the TARGET software from Thrustmaster with the provided profile for the FCS Hotas layout, the throttle worked fine, but the stick itself didn‘t respond to any input.

Following the guide from post 6 of the forum link sorted out all problems:

https://forums.frontier.co.uk/threads/thrustmaster-t16000m-fcs-hardware-problems.421485/

Thanks for the response but I followed the steps and the parameters are already set to 0. Also not having any problems with input from the stick, but the issue is that no games are detecting the stick and throttle at the same time.

Originally posted by Bubba Fett:

I'm wondering if Elite is seeing the throttle first, thinks the axis on that are a stick then it sees the stick and doesn't know what to do with that.

That sounds very likely

[Butterlord]

So I noticed it had my model registered under profiles, and when I use it everything works 100% fine. Still don't get why they both don't get detected together, most of the flight games I play don't have a profiles option like this

[Bubba Fett]

Now that you've got it working with the default setup with your hotas, you're still going to do a lot of tweaking with the controls.
I don't even remember what it was by default, but I ended up using the analog stick on the front of the throttle for lateral thrust, the knob on the left side of the throttle for sensor zoom, the top stick on the right of the throttle for handling, (boost/flight assist, the middle for all the targeting , and the bottom one for ship functions, (gear, lights, cargo hatch, night vision) and the paddle axis for forward/back on the SRV.

What ever you decide to use, it might be better to set a lot of your own control bindings. When the config says a certain function is button 9, it doesn't tell you if it's button 9 on the stick or throttle. (assuming you even know which is button 9 on each device.
I just gave it some thought and decided for myself what was going to go where. That way it's easy to remember.

One last thing. There's a bug that I've had and read about on the frontier forums where button 2 on the joystick sometimes mutes the windows volume. It doesn't happen all the time, but when it does you have to tab back to windows, open your sound settings and unmute it. It only seems to mute the sound and pressing it again doesn't unmute it.
I never found a solution and finally just stopped using button 2 for secondary fire. (I use button 3 now)
This seems to be an Elite Dangerous issue since I don't get it happening in any other flight sims.
I also didn't see it mentioned on the Frontier forums happening with any other sticks. Only the TM16000 seemed to do it.