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

Refurbish engines on the launch pad. #1638

Closed
Alex6511 opened this issue Mar 1, 2022 · 1 comment
Closed

Refurbish engines on the launch pad. #1638

Alex6511 opened this issue Mar 1, 2022 · 1 comment
Labels

Comments

@Alex6511
Copy link
Contributor

Alex6511 commented Mar 1, 2022

In the event of a launch ignition failure, you are currently forced to roll your entire stack back to the VAB and back out again. This incurs a time delay, but is generally seen as a balanced interaction.

In the event of a launch performance penalty, you are currently forced to roll your entire stack back to the VAB and swap the engine. This incurs a edit, time, and cost delay (though the amount is less because it is an engine refurb). Additionally, if one is not informed of how this works and only edits the craft or rolls it back out again without editing, like the ignition failure procedure, the engine will not display as performance degraded in the UI, both in the staging list or in the PAW outside of its raw thrust output numbers. This is some unclear UX that hides the fact that the engine is degraded.

A preferable solution to both of these would be a button in KCT when the craft is on the pad that allows the removal of all engine anomalies in exchange for a time delay and some factor of original engine cost. This would reduce scene transitions and the need for rolling back to the VAB, as pad swaps on engines are possible. This button should validate that launch clamps are still attached.

@siimav
Copy link
Contributor

siimav commented Mar 8, 2024

Implemented in #2327

@siimav siimav closed this as completed Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants