Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Lock rather than zero throttle on loss of control #245

Closed
pjf opened this issue Dec 16, 2014 · 2 comments · Fixed by #473
Closed

Feature Request: Lock rather than zero throttle on loss of control #245

pjf opened this issue Dec 16, 2014 · 2 comments · Fixed by #473

Comments

@pjf
Copy link
Contributor

pjf commented Dec 16, 2014

Presently if control is lost, RT sets the throttle to zero. If that loss of control was because the ship was doing its final burn into orbit and passed over the horizon, then a future of fiery re-entry awaits.

It would be lovely to have a setting (even a global one) that could be toggled to simply lock the throttle rather than setting it to zero.

Bonus points if this was a toggle in the flight computer panel itself, so the player could manually set or un-set it per vessel.

Many thanks!

~ Paul

@krenshala
Copy link

If you use the flight computer for that circularization burn into your initial parking orbit then it won't matter if you have loss of signal before or during the burn. There was quite a bit of debate whether or not a vessel should shut down its engine when it loses comms, and both options share similar issues: if it doesn't shut down you can expend too much fuel and crash when entering orbit of a new body just as easily as you can fail to make orbit by having it shut down early on a launch circularization burn.

@pjf
Copy link
Contributor Author

pjf commented Dec 18, 2014

If you use the flight computer for that circularization burn into your initial parking orbit then it won't matter if you have loss of signal before or during the burn.

Indeed, although even as a somewhat experienced RemoteTech user I wouldn't trust myself to pull this off flawlessly. It involves understanding the flight computer (something which takes new users some time), and depending upon one's OS it may involve dodging input issues when entering numbers ( #197 ), or potential delta-v issues ( #243 ).

Hence the suggestion for a global setting; players can set this to whichever mode they prefer (throttle cut or throttle lock), and can over or under burn on unexpected signal loss as per their personal preferences. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants