Full STOP!

raeat

Banned
I never used to come to a full stop when entering a system or normal space and I liked it that way. I don't want to come to a full stop now. How can I set it back to how it was?

Please answer the actual question if you have an answer to the actual question. Everything else is irrelevant.
 
Please answer the actual question if you have an answer to the actual question. Everything else is irrelevant.

You sound like 7 of 9

This was a bug in the Beta, although it only seemed to happen on certain setups. I use a a full HOTAS setup and never saw the behaviour some described, in the live build it also working as normal.

There is something in the patch notes about the fix, what type of setup are you using?
 
I'm see-ing the opposite - have to "blip" throttle to get full stop on entry - previously throttling to neutral during jump would mean you were stopped on arrival - saw someone else mention it who has Hotas X same as myself - not a biggie, but something about how the Hotas throttle is read has obviously been changed.
 

raeat

Banned
777Driver: I use a F16000 Thrustmaster HOTAS.
I'm trying different settings to see if I can get what everyone else has but doesn't want (no FULL STOP) now. I am not expecting success.
 
Last edited:

Deleted member 38366

D
Well, it does still work in SuperCruise (transition from normal space to SC), where the Ship will always start off at 100% Throttle (at least does so for me).
Took me a while to figure out why the Ship overshot quite a few times after checking out USS near Stations and then going back to SC....

I guess they "fixed" the Beta condition of the Ship uncontrollably accelerating after System arrival, but forgot to revert the SuperCruise Transition.

Either way, it seems we now still suffer from this new "an arbitrary fixed Throttle position is set upon completion of a Transition, regardless of actual Throttle setting of the Input Device".
I don't understand why they even touched and changed that.

-- edit --
Weird, repeatedly tested it again a moment ago and now the Normal Space -> SC Transition works normal again *scratches head*

-- edit 2 --
Still happens - but only seems to happen when leaving a USS...
 
Last edited by a moderator:
Either way, it seems we now still suffer from this new "an arbitrary fixed Throttle position is set upon completion of a Transition, regardless of actual Throttle setting of the Input Device".
I don't understand why they even touched and changed that.
Yeah, that one is pretty stupid. The game completely disregarding the position of an input axis at any time the player is supposed to control the ship is bad.
 
777Driver: I use a F16000 Thrustmaster HOTAS.
I'm trying different settings to see if I can get what everyone else has but doesn't want (no FULL STOP) now. I am not expecting success.

I'm using the same controller & haven't had this issue. I usually enter a system as full throttle (unless I plan to scan the main star) and it works fine for me, same as before (and in beta too). If I want to stop I zero the throttle during the jump.

A screengrab of your controls page might help.
 
I'm see-ing the opposite - have to "blip" throttle to get full stop on entry - previously throttling to neutral during jump would mean you were stopped on arrival - saw someone else mention it who has Hotas X same as myself - not a biggie, but something about how the Hotas throttle is read has obviously been changed.

I'm on keyboard and mouse and see something similar. I used to be able to set throttle to zero during the jump and arrive at a full stop if I wanted to but last night found I had to zero throttle after entering SC.
 
I haven't played the beta, but in 2.4 everything was fine, and come 3.0 live - ship STOPS on hyperspace exit.

I've noticed also that upon supercruise exit, my throttle is set to full BACKWARDS.

I do have a joystick with a throttle (which is always set to zero), but I only use buttons for throttle. After removing the throttle axis in settings, the game behaves normally on both counts.

Patch notes claim to have fixed this issue in 3.0, but it was actually fixed in 2.4 (at least for me) and reintroduced with 3.0.
 
Back
Top Bottom