Devlog 1-

Hi! I’m Mae, I absolutely love the game KSP (Kerbal Space Program), and have been considering making a custom controller for a while. This is gonna be kind of a yap session because I want to set the scene for later devlogs, so I apologize in advance.
.
I’ve already put together a basic parts list, and am finishing up 3d models of all the basic components (see below). Once all the components are modeled, I’ll start drafting a 3d model for the top cover based on some concept drawings (I seem to have misplaced them, sorry :C ), and then once I’m happy with it, I’ll order the parts and start with the programming.
.
To actually interface with the game, I’ll be using the Kerbal SimPit Revamped Mod, and the whole controller will be run off of several arduino boards (the details for this section will be worked out more once the controller is built).
.
The plan for the controller is pretty simple:
.
Construction- The base construction of the controller will be quite simple. It will be in a 3d printed PETG case. The top cover will be a black ABS sheet, with holes for the buttons and switches CNCed out. The sheet will then be spray painted white, and finally a laser cutter will do some quick passes over the sheet to burn away the paint and create labels for all the inputs.
.
Input- Use one joystick for rotation/translation, big button with covering for staging, probably the same button but red for abort, latching blue switches for toggles, keyboard keys for momentary switches, and keylock switches to lock out throttle/ joystick to prevent accidental input as well as act as the power switch (bc who doesn’t love the feeling of turning on a device with a switch)
The lights in the latching switches are (thankfully) not controlled by the button itself. This gives them the added benefit of being able to update themselves when switching to a different vessel, with different settings enabled on it.
.
Display- Have 3-4 rows of 7 or 14 segment displays showing mission information (apoapsis, velocity, altitude, delta v remaining, etc.)
The displays have different modes that show different information , swapped using buttons (ie. orbital, surface/landing, rendezvous/docking, and maneuver information)
One or two additional displays would be nice to keep time warp info separate, but not strictly required.
The coolest idea (but also the most expensive and difficult to program) would be to have a small display to show the navball and/or the current orbit visually.
.
Thanks for reading my first, and hopefully not my last, devlog!