Button Box

A button box is what you build when you are tired of fumbling for a keyboard in a dark room with a VR headset on. It is a panel of real switches, meaning physical toggle switches with a satisfying snap, push buttons with aircraft-style safety covers, and rotary encoders with 16 or more detents, all wired to a USB controller board and mounted within thumb reach of the wheel. The inputs map to in-car adjustments that need to happen mid-race: brake bias forward or back, traction control up or down, ABS sensitivity, pit limiter on, fuel mix, engine map, tear-off, fast repair. Once you have trained your hand to the layout you stop thinking about buttons and start thinking about the car, which is the entire point of a dedicated physical interface in a sim racing rig.

Sim racing puts a cognitive load on your hands that few other hobbies replicate. You are already steering, shifting, braking, and modulating throttle simultaneously; adding a keyboard hunt for the F5 key at the exit of Lesmo 1 is a high-speed gamble. A button box solves that by moving 20 to 60 inputs into a static, label-free layout where every switch feels unique. A toggle with a flip cover does not feel like a push button, and a rotary encoder with 16 detents does not feel like either, so you find them by shape and position rather than by sight. That is the reason a Stream Deck, useful as it is for production work, does not replace a button box in VR: flat glass keys are impossible to distinguish by touch alone.

A button box is not a steering wheel, and putting wheel controls on it is a setup error. Wheel buttons are limited to roughly 10 to 20 inputs and need to stay mapped to things you adjust while actively cornering. The button box handles everything else: pit-stop presets, black-box navigation in iRacing, headlight and wiper toggles, ignition and starter sequences. It is also not a keyboard replacement in the sense of covering every possible command. Start with the 8 to 12 inputs you actually use every session and add only what earns a place, rather than filling every available slot on day one and then fighting the muscle memory you built for controls you never touch.

Controllers, switches, and the build decision

The controller board is the spine of the box, and the dominant two options occupy opposite ends of the effort spectrum. The Leo Bodnar BBI-32 (about $43 to $55) uses a no-matrix architecture where every button gets its own input pin, so wiring is pure point-to-point with no diodes or ghosting maths. Its push-in connectors eliminate soldering entirely. The BBI-64 doubles the input count. Derek Speare Designs controllers (DSD) use a similar no-matrix approach with Cypress, Microchip, and TI components, made in the US. At the other end, an Arduino Pro Micro or Leonardo (ATmega32U4 with native USB HID) costs under $10 and requires the MHeironimus Joystick Library and some wiring work. Do not use an Arduino Uno or Nano; they lack native USB HID and need bridging firmware that complicates the build for no benefit.

Switch choice determines the tactile character of the box. Toggle switches come in two varieties that serve different purposes. Latched ON-OFF toggles stay where you leave them and suit headlights, ignition, and stateful settings. Momentary ON-OFF-ON toggles spring back to centre and suit pit limiter, radio, and momentary commands. Rotary encoders need matching to their controller; the classic bug where one detent produces two clicks happens when the encoder’s transitions-per-click rating does not match the board’s mode. A Bourns PEC11H encoder with the BBI-32 in the correct mode solves it permanently. Price for a finished box runs from about $30 for a bare Arduino build with a 3D-printed case to $250 and beyond for a CNC-machined premium unit, with the sweet spot for a mid-range box landing around $130 to $190.

Button box vs. Stream Deck

The comparison is worth making because Stream Decks are everywhere in sim racing rig photos and they solve a problem adjacent to this one. A Stream Deck ($150 to $250) puts relabelable LCD keys on your rig that can trigger sim commands through plugins like iRaceIT or SimHub. The labels change dynamically, which is genuinely useful for multi-class racing or switching between sims. What it cannot do is give you tactile feedback: every key feels identical, and finding the right one in a dark room or under a VR headset means memorising the grid position with zero physical cues. A button box gives you a toggle cover that must be lifted, a rotary encoder that clicks at every detent, and a push button that depresses with a different force curve than its neighbour. That variety is what makes blind operation possible, and blind operation is the standard for anyone racing seriously with a headset on.

Where the sim racing button box came from

Button boxes did not originate in sim racing. They came from aerospace and industrial control panels, where banks of dedicated physical switches are standard in cockpits and on factory floors because a misidentified input has consequences heavier than a lost lap. The crossover into sim racing happened in the late 2010s as direct-drive wheel bases and load-cell pedals raised the hardware ceiling and the remaining bottleneck became driver input latency that was cognitive rather than electronic. Leo Bodnar, already known for his USB conversion boards and high-end sim racing electronics, released the BBI-32 as a no-solder, no-matrix solution aimed squarely at the sim community, and the DIY ecosystem followed within a year. Derek Speare had been shipping independent button controllers since roughly 2012. The AMstudio tutorial series on YouTube became the canonical DIY reference, teaching thousands of builders to wire an Arduino Pro Micro with the MHeironimus library and a custom enclosure.

Common mistakes that survive the first build

The most common mistake is mounting the box too far from the wheel. If the driver has to lean forward or reach across body to hit a button, the box stops being used mid-race and the investment turns into decoration. Mount it on wheelbase uprights or a horizontal crossbar within thumb distance, using the VESA 75×75 or 50/75/100 mm patterns most 8020 profile rigs accept. The second mistake is mapping every available slot on day one. A 32-input box with all 32 functions assigned forces the driver to learn a new instrument while racing, which degrades lap times for weeks. Start with the 8 to 12 inputs that are race-critical, use them until the movements are automatic, and then add one at a time. The third mistake is using an Arduino Uno instead of a Pro Micro, which produces a box that the computer does not recognise as a game controller without extra firmware that introduces latency and complexity.

DIY guides for sim racing layouts routinely cover button box placement and integration, and getting the ergonomics right before the enclosure goes together saves weeks of adjustment after the fact.