Skip to content

Prelaunch successful ignition DU fix - #297

Closed
njits23 wants to merge 17 commits into
KSP-RO:devfrom
njits23:prelaunch_fix
Closed

Prelaunch successful ignition DU fix#297
njits23 wants to merge 17 commits into
KSP-RO:devfrom
njits23:prelaunch_fix

Conversation

@njits23

@njits23 njits23 commented May 9, 2026

Copy link
Copy Markdown
Contributor

Make sure you have read and understood the contributing guidelines!

Pull Requests that don't follow the guidelines will be rejected. If you need help or are confused just ask, and we will be glad to help.

  • [X ] PR being applied to the correct Feature Branch or dev
  • [ X] PR is not being sent to master

This should make the successful ignition DU only apply if pad ignition failures are actually on and awarding ignition failure DU on the pad is actually enabled..

Capkirk123 and others added 17 commits March 25, 2023 18:05
* Add additional TestFlight data to editor and flight PAW (KSP-RO#257)

* Add additional TestFlight data to editor and flight PAW

Goal is to add more engine PAW data similarly to how TestLite did it, so user doesn't have to use TestFlight's editor window.

Editor:

Add rated burn time; additionally display time in minutes for longer burn times (>60 sec), for ease of conversion
Display Continuous Burn Time rating for engine configs that have different continuous and cumulative values.
Add current and max flight data
Add current and max data MTBF
Add current and max data reliability
Add current and max data ignition chance

Flight:

Add current and max flight data
Add MTBF
Color engine failures in orange

* Fix SRMs not having ignition chance in editor PAW (KSP-RO#263)

---------

Co-authored-by: Falki <72734856+Falki-git@users.noreply.github.com>
Co-authored-by: siimav <siim.aaver@gmail.com>
@njits23 njits23 changed the title Prelaunch fix Prelaunch successful ignition DU fix May 9, 2026
@njits23 njits23 closed this May 9, 2026
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 this pull request may close these issues.

4 participants