It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Star Wars™: TIE Fighter Special EditionControl problem with Thrustmaster 16000m Joystick(7 posts)solved(7 posts)solved
(7 posts)solved
Pages:
1
This is my favourite topic
Posted September 25, 2017
Hello I currently have a T16000M plugged in, as it was recommended on this forum a while back as a good joystick for old dosbox games as well as modern flight sims.

I have the current drivers and the current TARGET software (which is a bit less than intuitive imho) but made a config.
I have various basic buttons mapped, but I am seeing 2 issues.

1) This one is minor and I can work around it if I need to. The deadzone is pretty big. I went back into the config and removed the deadzone buffer I had added, as this joysick is really tight, but I feel more slack in the middle than I would expect.

2) This is the big one. Per other instructions I found, for a button thaat I can press and hold, liek the trigger, I set it to HOLD in the TARGET software, rather than pulse, but I currently have a semi-automatic Tie Fighter, I have to spam the trigger to get it to do multiple shots.

Any thoughts? Having to spam the trigger will wear on the hand after a while.
Post edited September 25, 2017 by Necro55
This question / problem has been solved by Antaniserseimage
Posted September 25, 2017
I have tried it in both pulse and hold mode, same behavior either way.
Posted September 25, 2017
You shouldn't need to change the default behaviour for the trigger in the software; in Tie Fighter (and basically any other flight sim, really) holding the button will already fire continuosly

I'm not familiar with the thrustmaster software, but it should be possible, in your profile, to just leave the button unmapped/unprogrammed, and the native behaviour will take precedence in the game

I'm pretty sure that the HOLD and PULSE settings are there for games that do not support that form of auto-fire or joystick input at all.
For example, shoot-em up where fast fire is achieve by fast button press, you can set the PULSE behaviour so that by simply holding down the button, you wll send a macro of multiple inputs to the game... HOLD is probably there to mirror a keyboard hold to a button hold
Post edited September 25, 2017 by Antaniserse
Posted September 25, 2017
avatar
Necro55: Hello I currently have a T16000M plugged in, as it was recommended on this forum a while back as a good joystick for old dosbox games as well as modern flight sims.

I have the current drivers and the current TARGET software (which is a bit less than intuitive imho) but made a config.
I have various basic buttons mapped, but I am seeing 2 issues.

1) This one is minor and I can work around it if I need to. The deadzone is pretty big. I went back into the config and removed the deadzone buffer I had added, as this joysick is really tight, but I feel more slack in the middle than I would expect.

2) This is the big one. Per other instructions I found, for a button thaat I can press and hold, liek the trigger, I set it to HOLD in the TARGET software, rather than pulse, but I currently have a semi-automatic Tie Fighter, I have to spam the trigger to get it to do multiple shots.

Any thoughts? Having to spam the trigger will wear on the hand after a while.
Rule 1: Never remap the trigger unless the game itself allows you to, most spacesims and flight games already have autofire assigned to it which isn't necessarily true with the equivalent keyboard command.
Rule 2: in 90% of the cases remapping button 2 (or 1 depending is the software button designations start from 1 or 0) is a bad idea too since it often has functions that cannot be emulated by keyboard commands.
Posted October 08, 2017
You guys were both right about the trigger, I unmapped it and it worked perfectly.

Now i just have to figure out the deadzone issue, I have the software set to as low a deadzone as possible, and it is pretty high still.

If there is any suggestions there, great, if not, thanks for the advice that fixed the trigger.
Posted October 08, 2017
avatar
Necro55: You guys were both right about the trigger, I unmapped it and it worked perfectly.

Now i just have to figure out the deadzone issue, I have the software set to as low a deadzone as possible, and it is pretty high still.

If there is any suggestions there, great, if not, thanks for the advice that fixed the trigger.
It might be because Tie Fighter and the X-wing games in general had a built-in deadzone, I was so used to it I only noticed recently after looking at the stats in CH control manager while playing X-wing Alliance in windowed mode after another user told me about it.
Sincerely I don't know if it was intentional (probably to take into account for the crappy stcks 90% of the users had) or just a quirk of the engine.
Post edited October 08, 2017 by Det_Bullock
Posted October 09, 2017
Gotcha, good info, although not what I wanted to hear.
THANKS
Pages:
1
This is my favourite topic
Community
Star Wars™: TIE Fighter Special EditionControl problem with Thrustmaster 16000m Joystick(7 posts)solved(7 posts)solved
(7 posts)solved