Throttling down to next jump

[Faded Glory]

It seemed like most complaints were from keyboard users, and a couple from consoles or PC gamepad users. I think you are the first Hotas/throttle user that has mentioned it affecting them?

So yet another inconsistency?

Nope. I'm using a T16000 HOTAS, and my behavior is all over the place.

I play in VR, so I can see from the cockpit throttle what the game is doing with the throttle at all times.

If I zero the throttle in the countdown, as soon as the jump starts it goes to full throttle. If I zero it again after this, when I exit the hyperspace jump it will either honor the setting, or will go full throttle again (I can see no pattern as to why it does one or the other), and if it does go full throttle again, any slight movement by me of the throttle sets it back to zero...

If I set the throttle to full reverse in the countdown, then when the jump starts the cockpit throttle goes full reverse, then shortly after it will set itself back to zero. If I then match the physical throttle with the animation (zero it), when I exit hyperspace it sets to full. If I leave it at full reverse, when I exit the jump it will be zero, and only start to register forward thrust after the physical throttle passes the center (zero throttle) mark.

It's painful, at least for me it is. I just want the game to set the throttle to exactly what I set it to, not automatically change it for any reason. This behavior also indicates to me something buggy going on, so despite support telling me it's working as intended (and I have great respect for the support team, but...) I think that's rubbish.

 

[Arguendo]

Nope. I'm using a T16000 HOTAS, and my behavior is all over the place.

I play in VR, so I can see from the cockpit throttle what the game is doing with the throttle at all times.

If I zero the throttle in the countdown, as soon as the jump starts it goes to full throttle. If I zero it again after this, when I exit the hyperspace jump it will either honor the setting, or will go full throttle again (I can see no pattern as to why it does one or the other), and if it does go full throttle again, any slight movement by me of the throttle sets it back to zero...

If I set the throttle to full reverse in the countdown, then when the jump starts the cockpit throttle goes full reverse, then shortly after it will set itself back to zero. If I then match the physical throttle with the animation (zero it), when I exit hyperspace it sets to full. If I leave it at full reverse, when I exit the jump it will be zero, and only start to register forward thrust after the physical throttle passes the center (zero throttle) mark.

I made some mental notes of how it worked for me in the game today, and it's exactly like what's described above (sans the VR). I am on a HOTAS X.

 

[Faded Glory]

Just did a couple more jumps, and this time left the throttle (physical) at full.

As soon as the jump starts, the cockpit throttle snaps to zero, then goes back to full, and of course I exit the jump at full throttle. Throttling down as soon as the jump ends stops me quickly enough.

So, to me at least, it looks as though the throttle is trying to go to zero, something that the patch notes suggest is fixed, but whatever they have done seems to have made a random mess for at least some players. Honestly I am struggling to understand why they made the change to have the throttle go to zero (something that in any case never happened for me that I could tell, but then I always zero my throttle during the countdown), because that change seems to have thrown a bit of a spanner in the works. Why it's not possible to simply revert the change to what it was in 2.4 also eludes me, but then I'm not a software engineer.

With so many other things needing attention, I have to wonder why they chose to make changes to something that was working fine...

 

[Faded Glory]

We should better be quite, otherwise they'll come up with the idea to remove FA Off totally as the ultimate end-fix. [mad]

Hehe... You're right.

Unfortunately this issue has got under my skin, and support suggesting it was 'working as intended' when what I described to them was not, at least IMO, the fact that the throttle wasn't zeroing by itself (quite the opposite in fact), didn't really help. Again, I have a lot of time for the support guys, they work very hard, so this isn't a criticism of them.

But truly, I have no idea why the devs messed with something that as far as I can tell had caused and was causing no issues, and subsequently cannot seem to get it back to how it was in 2.4 (after having the issue raised in the beta). Well, to me that's disappointing.

 

[PiLhEaD]

As per the patch notes, this issue reported resolved.

Hurrah.