Throttle Behavior Exiting Hyperspace Jump

[Faded Glory]

Hi

I have been having the issue in beta and now in live that despite setting my throttle to zero during the countdown to a hyperspace jump, the game is setting it back to full so that on occasion, unless I keep altering it, I will exit the jump, facing the star, at full throttle / speed.

Personally I find this undesirable. I would like to exit a hyperspace jump at whatever speed / setting I decide to based upon my control inputs.

I understand from support that this is intended behavior in response to the throttle being automatically set to zero by the game. There is a patch note that says this was fixed.

However, I don't believe that fixing the throttle from automatically setting to zero should mean automatically setting it to full. Surely the throttle (and indeed any control) should reflect whatever the user sets it to, nothing more, nothing less.

This thread is not intended to discuss the pro's and cons of what speed is 'best' to exit a hyperspace jump. That surely is simply a player preference. What I am asking for is simple.

That whatever settings a player sets their controls to (in this case it is specifically about the throttle), the game reflects that setting and does not arbitrarily change it.

That is how things worked in 2.4, and I cannot understand why that would be changed.

 

[Riverside]

I understand this is a known bug & not intended behaviour. The game isn't receiving the input from the controller during the jump (as it did before), or isn't checking the current input value, instead just using the last known value (which would always be full throttle for a jump).

 

[Faded Glory]

I understand this is a known bug & not intended behaviour. The game isn't receiving the input from the controller during the jump (as it did before), or isn't checking the current input value, instead just using the last known value (which would always be full throttle for a jump).

Could you point me to where that is acknowledged as a known bug please?

As I said, support have told me this is intended behavior. I sincerely hope it is not so (I haven't closed the ticket), and I would really like the issue resolved.

 

[Riverside]

https://forums.frontier.co.uk/showthread.php/409620-Flight-assist-mode-changing-automatically?p=6453106#post6453106

777Driver has linked to it in a thread you posted in too:

https://forums.frontier.co.uk/showthread.php/410556-Throttling-down-to-next-jump?p=6463021&viewfull=1#post6463021

(to be fair this is about flight assist not specifically the throttle)

 

[Riverside]

Looking further into this it seems you are right, or more right than I am at least

This seems to be the lastest info:

Hey Cmdrs,

There has been some debate about how this should work.

I've passed on this report for review.

The thread this is in seems to be both the first report, and the most helpful thread (for explaining the problem). I agree the game should recognise the controller input position at all times.

 

[Faded Glory]

Looking further into this it seems you are right, or more right than I am at least

This seems to be the lastest info:



The thread this is in seems to be both the first report, and the most helpful thread (for explaining the problem). I agree the game should recognise the controller input position at all times.

Thanks. Well hopefully they will continue to look into it (and fix it) and support is mistaken.

 

[Juniper]

The bug is that the game is ignoring what the player has the throttle set to.

Yes, they 'fixed' it so that it doesn't automatically set to zero if the player has throttle up, but they've just replaced one bug with another... a far more dangerous version in fact (as my repair bills will testify).

Please Frontier - just set the throttle to whatever it is actually set to on leaving hyperspace. Don't try and second guess... at all.

 

[lesscode]

+1 for reverting to the old behavior. Almost crashed into a NS on the first jump after the update dropped. The ship should honor the pilot's throttle setting at all times.

 

[Tath]

I would like to add my voice to the zero throttle being reverted to its previous behaviour.

* Personally, I considered this a quality of life piloting aid (an autopilot assist, if you will, in game speak).
* I and undoubtedly others, still suffer from sun texture loading issues, which cause graphical hitching and momentary lack of input on arrival in a new system.

 

[NightWalcker]

I SUPPORT back speed return reset as it is safe and convenient or at least make a choice of this option in the ship options. I think this is important for most explorers.

 

[Lightspeed]

Frontier ... you had it working right before you tried to fix it ...for whatever reason commanders were complaining in Beta. If you set it back to its condition in 2.4, all will be well.

 

[PiLhEaD]

..I agree the game should recognise the controller input position at all times.

Quite right, and to think otherwise is simply crazy.

What FDev have seemingly decided to do is choose to wilfully ignore the player's input, and for 'reasons' to override our controls to how they think everyone should always be playing.

Why? What are their reasons? Some commanders want to come out of hyperspace at full-speed, others want to come out stationary. I like to have the option to choose for myself, setting the throttle accordingly during hyperspace, and actually be in control of my ship.

That they've also managed to do it in a manner that has HOTAS Commanders (myself included) positively dis-advantaged is 'very very very poor'.

Honestly FDev, I am often left wondering quite what is in your heads with some of these 'design ideas' - any ordinary player of your game could have told you to leave this well alone.

 

[Flatkat]

I should add my support to this, i prefer the option to set my exit speed when "things" could be waiting on the other side

 

[Agony_Aunt]

Agree with OP. Throttle should respect what the player does with it.

 

[Ronzer]

Since the controller was mentioned, I wonder if this has anything to do with the PS4 bindings they've ported over from the PS4. Previously, on PC, I was able to use 'toggle' or 'hold' for those bindings that give the option. When I got the PS4 game, I noticed and made a post about how on the PS4, I cant use 'hold' as an option...'toggle' is the only thing that works. Now, they've 'fixed' the PC game to use the PS4 bindings. Now, on PC, I can only use 'toggle' even though I'm using my old binding set. I hope FDev can 'unfix' this, so I can use 'hold' again at least on PC. But, really, would be best if they make the PS4 game have the 'hold' ability too. Or is this only happening to me?

 

[gord-s]

Agree with OP. Throttle should respect what the player does with it.

nail on head

sick of crashing every time
toys out of pram - I'm just not playing

 

[Riverside]

nail on head

sick of crashing every time
toys out of pram - I'm just not playing

It was fixed earlier today according to the patch notes

 

[Faded Glory]

It was fixed earlier today according to the patch notes

I have tried it, and it does indeed seem to be fixed. Throttling down during the countdown leaves the throttle at zero during the jump and when exiting hyperspace.

(Note: I still see the cockpit throttle move and then reset itself to zero. It seems to go full reverse for a second then back to zero both at the start of the jump and when exiting it. This may be to do with the fact that I am using the throttle with the full range setting so zero is in the middle, but it's not an issue as it does go back to my zero setting, and stays there, and that is really all that I am concerned with.)

 

[Riverside]

I have tried it, and it does indeed seem to be fixed. Throttling down during the countdown leaves the throttle at zero during the jump and when exiting hyperspace.

(Note: I still see the cockpit throttle move and then reset itself to zero. It seems to go full reverse for a second then back to zero both at the start of the jump and when exiting it. This may be to do with the fact that I am using the throttle with the full range setting so zero is in the middle, but it's not an issue as it does go back to my zero setting, and stays there, and that is really all that I am concerned with.)

Thanks for confirming, I haven't been in the game today. I never notice the in-game controller movements, they are usually out of my line of sight (I only use mouselook occasionally) so I don't know how they behaved before

 

[Faded Glory]

I'm using digital thrusters and it's finally back to original 2.4 behavior. Great and big thanks!

But I'm still shaking my heads in awe that they actually have put in an option for permanent FA OFF, but no not really. It's DA Off (drive assist off) which must be one of the most wanted options during the last couple of month (NOT)! I can only guess that's British humor. I'm afraid I'll never get British humor ...

Well, I do hope that the FAOFF issue gets resolved soon...

I know these things aren't exactly game breaking, but in a game that has a sim element involving flying spacecraft, having controls misbehave is more than a minor irritation, and they really do need to work right, not have to be worked around.