SiliconPyro

As a pod moves around Kerbal's heads can clip through the wall of the pod.

You know, I did for some time and I think it was accidentally removed during a code refactoring. Thanks for the suggestion.

Oh, yes. Still working on a balance between fun and physics.

You have to reach a checkpoint and drop them off. That will be explained in a future update. Not sure what you mean about gravity being selective.

I've finally gotten around to learning enough Unity to make something worth sharing. Of course it had to be space related thanks to so many hours in KSP. It's still a work in progress, but here's Rocket Rescue: https://siliconpyro.itch.io/rocket-rescue

Please change my name to "SiliconPyro".

Redjoker is 100% correct. If you program your Teensy to act like a standard joystick with the fader as a throttle, KSP will have no problem with it. This plugin is unnecessary if all you want it a new input device, but if you want to get clever with your controls, like using toggle switches or even getting data from KSP and presenting it on a display built into the controller, then the hardware plugin is perfect. Please update us on your progress. There are a lot of us working on dedicated control devices.

Keep at it, Rich. I'd hate to see such a great plugin die because of an update, especially since I pan to use it with some custom hardware.

Right now, when you place your mouse over your craft's path, it just shows you a little dot where you can make a maneuver node. It would be helpful if it also showed you a little more information, such as your projected altitude and speed at that point. In addition, if you have a target selected it could show your target's position on its own path, so if you are pointing to one hour ahead, it would show where your target will be in one hour.

Seems simple enough, but I don't know if maneuver nodes really calculate for efficiency. It would tell you how to burn to keep your apoapsis below a certain altitude though.

Say I have a rocket with poor acceleration. It has staged its primary lifting stage and is in a sub-orbital trajectory with an 85km apoapsis. My intent is to keep the apoapsis at 85km. Is it more efficient to start my circularization burn as soon as I reach 70km and steer below the horizon to keep my apoapsis from rising, or burn later and risk passing the apoapsis during circularization, possibly requiring me to steer higher? Obviously a circularization stage with a higher acceleration is ideal, but in this case, I'm just wondering what the most efficient option would be.

I hadn't noticed, but I guess I should go back and take another look. That would be nice, for sure.

This is just really .... looking. I hope you continue to develop and refine it.

Oops. Attention to detail.

Yeah, I scored an 80, so, not sure how to answer the poll.