Jump to content

Search the Community

Showing results for tags 'ksp2br-uiux'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Welcome Aboard
  • Kerbal Space Program 2
    • KSP2 Dev Updates
    • KSP2 Discussion
    • KSP2 Suggestions and Development Discussion
    • Challenges & Mission Ideas
    • The KSP2 Spacecraft Exchange
    • Mission Reports
    • KSP2 Prelaunch Archive
  • Kerbal Space Program 2 Gameplay & Technical Support
    • KSP2 Gameplay Questions and Tutorials
    • KSP2 Technical Support (PC, unmodded installs)
    • KSP2 Technical Support (PC, modded installs)
  • Kerbal Space Program 2 Mods
    • KSP2 Mod Discussions
    • KSP2 Mod Releases
    • KSP2 Mod Development
  • Kerbal Space Program 1
    • KSP1 The Daily Kerbal
    • KSP1 Discussion
    • KSP1 Suggestions & Development Discussion
    • KSP1 Challenges & Mission ideas
    • KSP1 The Spacecraft Exchange
    • KSP1 Mission Reports
    • KSP1 Gameplay and Technical Support
    • KSP1 Mods
    • KSP1 Expansions
  • Community
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
    • KSP Fan Works
  • International
    • International
  • KerbalEDU
    • KerbalEDU
    • KerbalEDU Website

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


About me


Location


Interests

  1. KSP2 Version: 0.1.0.0.20892 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods used: None Video Evidence: First look to see that I activate the engines. Then I stop after 2 seconds into the burn and the timer still keeps counting down. https://youtu.be/3h5p-kF6N9c Possible Expected Behavior: This is more complicated because what if the player only drops the throttle to 50% or 80% because once that happens the timer is inaccurate. Alternative possibility: A way around it might be that the timer just stops and turns to another colour indicating an error on the part of the player? Additional Information: This wouldn't matter very much if it was the same as KSP1 where dV is a much more important indicator of how a maneuver is progressing which I made another bug report for:
  2. KSP2 Version: 0.1.0.0.20892 Operating System: Windows 10 CPU+GPU+RAM: i9 9900K+3070ti+32GB Mods used: None The following explanation is to show why the required dV actually should be counting down on the Burn Timer. An experienced Kerbal player (well...me at least) does the following for executing a maneuver node burn typically (KSP1): They start the burn at 100% throttle at the appropriate time. They are watching the required dV reducing as the fuel gets used up. Towards the end of the burn they drop the throttle for finer control. They watch the dV display until it hits exactly zero but are also watching the actual maneuver to see if it matches the predicted one. Video Evidence using KSP1: This follows the above 4 steps. https://youtu.be/9DLHwIUxFP8 Video Evidence using KSP2: This is less precise than KSP1 primarily because the deltav isn't reducing like KSP1. https://youtu.be/aJxAZ9nnexc Additional Information: In the case of a maneuver node execution 1 second is a very long time. Recommended actions: Have the dV display reduce as the burn progresses as its being used up like how KSP1 does it. If dV passes below 0 show negative numbers to show how far to recover using RCS etc. Have the dV display on the burn timer a little bigger and reduce the size of the time remaining.
×
×
  • Create New...