Horizons Hotas throttle setting/calibration help needed (thrustmaster t-flight)

Greetings!

Sorry for my bad english, i'm trying my best tough :)

So i used a Thrustmaster t-flight hotas x for E: D in the past but i didn't played for a while now.
I just reinstalled E: D a few days ago (first time since i use win 10 if that counts for anything), but the z axis (throttle) doesn't work properly. I don't think it's E: D related rather than calibration but still, i tried to google for some solutions but nothing i tried seemed to work.

My E: D setting for throttle is:
Throttle axis: [joy z-axis] inverted (deadzone: 0 (all the way to the left))
Throttle axis range: full range

With this setting and everything at default in windows here is how my throttle works:

Throttle stick in the middle position (my ship should be at full stop):
kuhoG1m.png
instead, throttle seems to be at about 35-40%



Throttle fully up:
0x6S3IN.png
I'm not sure how ship speed works nowadays but this does seem to be less than 100% throttle (my speed is 256 here, with flight assist off it goes up to 274, and after a boost (fa still off) it slows back to 370 from 496)


This setup looks like this in the win 10 built in setup utility (this is the default setting):
YtABRXE.jpg
Seems like it's less than it should be, i guess this is why my ship moves when it should stand still.


With the throttle stick fully pulled back, it looks like this:
TOnUKgG.jpg
This also less than it should be.


It looks like this during calibration.
All the way up :
Op419J4.jpg

Middle position:
9jn5ikX.jpg

All the way back:
C89b6Po.jpg
Everything else scales from 0-100% with 50% being the middle position.

After calibrating it looks like this: all the way up, middle pos, all the way down respectively.
xKtSmTP.jpg
It seem to be using the full scale now, but the middle position is still not quite right.

With these settings (meaning after calibration) ingame it works like this:
Throttle at middle pos:
3h5FBdB.png
Better than before but it's still not right, the ship still moves when it shouldn't.

Full speed ahead is the same as before (256).

Full backwards speed is 164, i didn't took screenshot but it was 128 before calibration.

So the windows 10 default tool to calibrate made things somewhat better but it's still not good.
Can any of you suggest a better calibration tool, or some other solution for this problem?
 
Elite absolutely requires throttle to reach full scale at either end, so what you have there won't be good enough.

With the control at zero, Windows control panel should show only a single pixel and it totally sucks at indicating 100%. Make sure that you don't force the control against limits when calibrating minimum and maximum, or the mechanical slop will lead to those bad end positions. The TARGET software may help to set up response curves that ensure end positions and maybe a plateau around midpoint to have a more reliable zero, but I have never used that so can't really give advice on it.

(edit) Small trick that usually works to un**** Saitek parts but may work here as well: disconnect the throttle, put it to central position, then reconnect it and softly move it through its full range. Depending on what trickery the firmware does, that may perform a self-calibration.
 
Last edited:
That TARGET sowtware doesn't support this model. Installed it but i can't do anything with it.
Already tried the reconnecting, even with restarting the pc before reconnecting the hotas.

Funny thing is, i realized that there is a small deadzone at a point when the throttle is pulled back slightly. That point should be the middle position, but it's not for some reason.
Maybe a firmware update could fix this but i can't find such a thing to this model.
 
Have you tried using "Joystick Curves"?

Download: http://xedocproject.com/joystickcurves.html
Tutorial video: https://youtu.be/CqzoJPCZM0w

I use this software to set input curves for pitch, roll and yaw axes on my Thrustmaster T.Flight (basically so I have a wider range of fine control around the first half or so of the movement for the three axes of the main stick). It's unusual to use this for a throttle but it might allow you to do it.

Incidentally, is your stick new 'cos that sounds like a bit of a hardware calibration fault to me.
 
I just tried joycurves but didn't seem to do much.

I didn't mentioned but another tool i tried is DXTweak2, but that seems to be ancient, it was made to work under win98 from what i saw and tough it runs under win 10 but doesn't seem to do much else. It was in DXTweak2 i noticed the strange deadzone where it shouldn't be tough.

And the stick is not new, i bought it in late 2015 and used it without any problem before (with win7). It's the first time i tried to use it under windows 10 tough.
 
I had this problem a while ago and tried more or less everything you are doing. When I eventually found the info in the video above and got the proper calibration screen in Win 10 it still went awry. If I remember correctly after calibrating I would do the ingame pre-flight check one time and I think that was part of the problem. In the end I think I bought a cheap sidewinder, recalibrated and flew out of the station without doing the pre-flight check in order to test the settings in open space without getting blown up again as that cost me 40mcr in my Corvette when the throttle problem originally happened to me. That worked and it hasn't happened again.
 
That shift+ctrl trick mentioned in the video did nothing for me with the driver installed. Without the driver i can get to the calibration but it doesn't solves the problem.

As Alec mentioned above this sounds like a hardware calibration issue, but the stick worked before without a problem. Nevertheless i just disassembled it to see if anything can be done that way but no. The stick when moved, turns a small potentiometer, but it cannot be adjusted manually. There is only one way and position it can be put back together.

Also, i just realized that calibrating in dxtweak did in fact do something, i can now use the full scale of the throttle from -100% up to +100% but the weird hardware deadzone is still there at -50% instead of 0 throttle.

ps: oh, and i'm in the middle of nowhere ingame, so i can't do preflight checks in the forseeable future. But the issue can be noticed in the driver or the calibration tools too so it's not Elite related, i just didn't knew any better place to ask, and hoped that someone might have a sloution. Maybe i'll ask thrustmaster's tech support.
 
Last edited:
...so it's not Elite related... Maybe i'll ask thrustmaster's tech support.

I think it's not thrustmaster either, but they will help you. I've got some isues with my stick for a couple of day's now, first i guessed it was it's age but now i'm convinced it's that windows update that did it. About 4 day's ago i started to roll to the left for 2 days on a row, yesterday it started to pitch down and no roll at all.
So maybe you should reinstall win10? ...i know! I just did a couple of months ago, hate it.
 
Yea' i contacted TM's support but they couldn't really help. They suggested to install the driver and gave me a pdf with some instruction on how to setup steam's big picture mode (???). They were quite fast to reply tough.
And yes i also came to similar conclusion. Tough i think it's possible that the win installation was somehow flawed even without any update. I'm not in the mood to reinstall tough :( I guess i settle with the not so perfect calibration i set up with dxtweak for the time being.
 
I fixed my issue with a rubber yep a simple office rubber, put it around the stick and the other end on the glider on the t16000 and it works perfect...if it does the left roll again i will put a rubber on the opposite side aswell...technology with a twist lol.
 
Does the t.flight have a switch on the side of the joystick base for PC or PS?

Also check that the (i think it was) green button on the joystick base hasn't been pressed. It toggles between to different sets of controls.
 
The green switch only makes the rudder to control the 4th axis (same as the stick twist) instead of it's own 5th axis. But it's turned on (lit). And the backside switch is on pc.
 
I've been away from Elite for the past year. The last version I played was 3.2. I just installed 3.3 and all the patches and set up my TM Warthog HOTAS as per normal and now I'm having the same problem. Under joy.cpl I can see the Warthog throttle properly outputting the full range of values, but in game it is limited to about half the throttle output even when the throttle is at 100%. Did anyone ever figure this problem out?
 
Just came back to ED recently and I also have this issue with my Saitek X52 Pro. I found that if I tabbed out of the game it will read the correct throttle value. Switching back to the game it will offset the controller values.

What I tried:
Playing with the settings in ED
Reinstalling the controller Drivers and software.
Installing previous versions of the controller Drivers and software
Reinstalling the game.
Reinstalling the Computer OS.
Tested controller in the profiler and in another game.

This is 100% an Elite Dangerous issue.
 
Back
Top Bottom