The specific Arduino I chose was an “eBay knockoff” of the 5V/16MHz Pro Micro. For this, I chose the Arduino as the micro-controller platform as I’ve used them previously, they are simple, and they work straight out of the box. Whilst I was waiting I started thinking about how to drive it. Next, I chose the type of buttons and the enclosure I wanted and ordered those.

I settled at around 60 after deciding which SC functions would be mapped to the panel itself, the buttons on the sticks, neither or both. The first step in designing the control panel was to determine how many buttons I wanted to implement.

they can be configured as left or right handed, and.

The factors that decided this choice were: I decided upon two Thrustmaster T.16000m joysticks. Having decided on the HOSAS setup, the next question was which joysticks I wanted to use. My rationale is that the game is primarily space based and the additional axes that the dual sticks afford, provide fine control of all three “strafing” directions as well as all three rotational “Pitch, Roll and Yaw” rotations. The first thing I decided was that I wanted my flight control to be a HOSAS (Hands On Stick And Stick) rather than the perhaps more common HOTAS (Hand On Throttle And Stick) setup. Note: I only outline setting up the SC “flight” functionality as I primarily use keyboard and mouse for other parts of the game such as First-Person Shooting (FPS). I saw this problem as something that could be overcome by designing a physical “control panel” which would have the most important functions mapped to a dedicated button. When I started playing Star Citizen (SC) I found the key combinations required during “flight” overwhelming.

Joystick to keyboard mapper