Restore TF configs for generic thrusters #2829
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Restore TF configs for generic thrusters (only, since TF apparently does not support RCS failures). Configs are fairly generous, since they have to support a very wide range of thrusters and eras.
All configs get a 10 hour burn time (this should be enough for almost everything). Data rates are tuned so 10,000 du should be reached after ~100 minutes of operation (shorter in the event of a failure rewarding extra du).
Thruster types have been given the following stats
Cold Gas Thrusters (inert, only likely possible failure modes from valves)
ignition 0.98 -> 0.9999
cycle 0.99 -> 1.0
Monopropellant Thrusters (simple, but bed erosion and burn-through possible along with valve failure)
ignition 0.96 -> 0.9995
cycle 0.975 -> 0.9995
Bipropellant Thrusters (more complex, reliability based on AJ10)
ignition 0.90 -> 0.9994
cycle 0.95 -> 0.9994
This should give some incentive to choose something other than bipropellant thrusters the second they become available, and encourage installing backup engines, similar to many real space probes like Cassini-Huygens.