Jump to content

Search the Community

Showing results for tags 'stock mechjeb features'.

  • 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

  • Developer Articles

Categories

  • KSP2 Release Notes

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

Found 1 result

  1. Here's my idea to make probes more realistic, while adding stock mechjeb in a fair way: Step 1: add communication delay. The way this would work is pretty simple. A time delay is added between when a command (like pitch up) is given and when it is initiated. The further you are from Kerbin the longer it takes. To compensate this probe cores will be given automation such as being able to execute maneuvers automatically and on higher level cores avoiding danger. Step 2: add mechjeb like automation to probe cores, the features form a hierarchy like this: Stayputnik: same features as in the stock game, plus communication delay, no SAS. Okto: Same as stayputnik but has SAS, smart A.S.S, and prograde retrograde lock. Hecs: Same as Okto, but can automatically execute maneuver and has maneuver lock. Okto2: Same as hecs but also has normal/antinormal and radial in/out lock. Rovemate: Same as hecs but has a bon voyage like rover autopilot. It is limited to a top speed of 0.05 m/s though. Small remote guidance unit: Same as Okto2, but has target mode and target lock. Large remote guidance unit: Same as the small one, but it has support for auto gravity turn and orbital insertion, as well as the ability to run simple kos like scripts. Hecs2: Same as large remote guidance except it has more advanced kos Hecs3: A new probe core that can be set to stabilize its orbit automatically if is on an impact trajectory. Has also features of hecs2 Dodec: A new probe core that can automatically orbit and transfer to any body and has full kos. All features of Hecs3 Dodec2: all probe core features and full mechjeb and kos. Step 3: change what Kerbals can do: Kerbals can now: Increase the top speed of the rovemate to 15 m/s. Use probe core specific features like smart A.S.S. without time delay. Kerbals can no longer: Use docking mode. Use target mode on navball. My ideas aren't perfect, but they get the point across, so what do you guys think of the idea and how it should be implemented?
×
×
  • Create New...