New HOTAS user astonished that Hyperspace Dethrottle does nothing by design?

I think this "by design" response needs to be revisited. (https://issues.frontierstore.net/issue-detail/1405)
I would rather be confused about my ship not moving than accidentally accelerate into a star because I am tired and forgot to dethrottle during my hyperspace jump.
Further, this essentially means the setting does nothing at all for HOTAS users. The entire point of it is to be an override for throttle position because it's a safety feature. If HOTAS users do not want to be confused by their throttle position, the setting can be turned off (and isn't OFF the default already?).

Anyway, please reconsider this "by design" response. I can assure you the current functionality is also resulting in confused players. I was confused as to why my ship was accelerating when I had the setting turned on and was convinced it was a bug. People are going to be confused either way, and I'd love for this setting to actually work as a safety feature while using HOTAS.
 
The de-throttle and HOTAS thing has always been a right pain in the derriere.
No idea why it's not been fixed, well maybe just pure incompitence?
 
Personally, I don't see why it would have ever worked with an analogue axis in use. I mean, seriously, your analogue axis is continually sending an input so when you drop out of hyperspace the game immediately sees that throttle input on next polling the inputs. Hence when the game is not in focus *alt-tabbed out" it isn't polling the input so that is why it could "work" then but when the game is in focus it must register the throttle position on polling so it wouldn't work.

However, I never fit a SCA so it would never occur to me to not pull the throttle back to zero on jumping.

EDIT - just realised that my buttons for 50% and 75% work (until my throttle control is moved) so it must be possible that a 0% command should override the throttle. So my analogue axis supposition above must be completely wrong. sorry
 
Last edited:
I was confused as to why my ship was accelerating when I had the setting turned on and was convinced it was a bug

It may be a technical reason why is "by design"

They can (and it's quite possible they actually do it) set the throttle to Zero by the hyperspace dethrottle function - but your analogic throttle is overriding that 0-throttle setting since the throttle position is sending inputs all the time

So... throttle to zero when you dont want your ship to move.
Or use a relative-throttle (one that autozero itself) or, fwiw, instead of a hotas, a setup with 2 joysticks
 
Does your throttle jitter when you have your hands off it? I don't have a traditional throttle anymore (I used to have the X52 Pro), and I have not used the dethrottle function of SCA in ages, but I don't think I remember ever having this problem. When not moved, my throttle's output did not change, and thus the throttle could be overriden any time by a button binding (0/25/50/75/100 percent) or SCA. Once I moved the throttle, it took over again.

So this might be more a hardware than a design issue.
 
That you have "no idea" I can agree with, as you are not party to any of the dev discussions (if any) around this issue, but nevertheless I'm sure that it isn't due to incompitence.
Grammar Police ALERT ALERT ALERT - 'incompitence' is actually spelt 'incompetence'........Nee naw nee naw nee naw.........
 
Does your throttle jitter when you have your hands off it? I don't have a traditional throttle anymore (I used to have the X52 Pro), and I have not used the dethrottle function of SCA in ages, but I don't think I remember ever having this problem. When not moved, my throttle's output did not change, and thus the throttle could be overriden any time by a button binding (0/25/50/75/100 percent) or SCA. Once I moved the throttle, it took over again.

So this might be more a hardware than a design issue.
Nope, it's rock solid. I tried adding a very small deadzone to see if that will help.I doubt that's the issue but it's worth trying. (EDIT: I am also looking at the Continuous vs. Increments setting but I am not sure if that will work on an analog throttle or not. I have an X56)
 
that's the great thing I find about Re- programable bindings you can change them back if you find what you have selected unsuitable 🤷‍♂️
 
Last edited:
On a related topic, it is somewhat annoying that after a rebuy the throttle isn't set to 0 even if you forget to zero the throttle handle. It's normally the only moment it happens to me that I forget to zero my throttle and on takeoff I always get surprised at the ship taking off like a bat out of hell.. :)

Not at home so I can't test how my Virpil throttle works during a jump with this option set, but unless I'm in a hurry it's burnt into my brain to reduce throttle during the jump.
 
Funny... I've never flown without a HOTAS since buying the game pre-Horizons... But now that you mention it, the does say something about de-throttling as you exit to the star, I always assume it had something to do with throttling down from the jump, not throttling down in super cruise. 🤷‍♂️
 
I normally don't de-throttle if I'm traveling, but I do if I'm jumping into a system where I have business. I like to study the starmap and set the navpoint before I start moving. If I'm in open I might also take a moment to study what ships are on the move before deciding what and how to do next. And if I need to go to the bathroom or do something else in the house I make extra sure to be de-throttled before arriving at the new system. :)
 
Nope, it's rock solid. I tried adding a very small deadzone to see if that will help.I doubt that's the issue but it's worth trying. (EDIT: I am also looking at the Continuous vs. Increments setting but I am not sure if that will work on an analog throttle or not. I have an X56)

Some more opinions on the matter from an older thread. 👇

I can also confirm what everyone else has said: if you have an analog throttle, its position will override the dethrottle as soon as the game gets its input.
In short, de-throttle doesn't work if you use an analog throttle, unfortunately.
My suspicion is that analog throttle position only overrides the dethrottle when the controller sends the game an update. For some controllers this might happen continuously, and for others only when the position is detected to have changed. This would explain why some people report that analog always overrides, others report that it only overrides when moved, and still others report that it overrides after an unpredictable delay. (I'm in the overrides-when-moved-except-sometimes-not boat, which makes me think it's tiny motions triggering it.)
 
This is very timely for me as I've just transferred over to the PC and set up a Thrustmaster HOTAS my son used to use. It's been a very long time since I used a joystick and lo and behold this problem has appeared for me - worked fine on XBox. I used the forward only setting when configuring the throttle, so any sort of setting other than dead stop is probably feeding a signal through. Yet if that's the case, wouldn't auto-launch auto-cancel itself with the throttle on? Or is that waiting for a throttle change to cancel it? I'll experiment some more next time I play, I literally just got this set up.
 
This is very timely for me as I've just transferred over to the PC and set up a Thrustmaster HOTAS my son used to use. It's been a very long time since I used a joystick and lo and behold this problem has appeared for me - worked fine on XBox. I used the forward only setting when configuring the throttle, so any sort of setting other than dead stop is probably feeding a signal through. Yet if that's the case, wouldn't auto-launch auto-cancel itself with the throttle on? Or is that waiting for a throttle change to cancel it? I'll experiment some more next time I play, I literally just got this set up.
So on my HOTAS, it worked fine if the throttle was midships or zero - anything else and I guess it was sending out an "I want to change my speed" signal that overrode the deceleration. So although my options are set to mid-throttle being 50% power, in hardware terms my HOTAS sees that as being between forward and reverse so presumably ED doesn't get told I'm trying to change speed for these purposes - it's like being in neutral. Any other position than that or 0 power does result in a speed change being perceived and deceleration getting cancelled. I avoided any other inputs.

So I guess a workaround is just go max throttle to jump, then flick back to middle position - if your HOTAS works like mine anyway. As soon as the countdown starts, midships. Then hopefully you're fine.
 
Back
Top Bottom