Chapter 2: Controls & Affordances

Created by Sarah Choi (prompt writer using ChatGPT)

Controls & Affordances (Analog vs Fly‑By‑Wire) — Cockpits, Bridges & UX (for Vehicle Concept Artists)

Why Control Philosophy Shapes Everything You Draw

A cockpit or bridge lives or dies on how its controls invite use (affordances), signal state (signifiers), and behave under load. Whether you sketch a rally buggy, a VTOL shuttle, or a littoral patrol bridge, the decision to go analog/mechanical or fly‑/drive‑by‑wire changes ergonomics, redundancy, failure modes, and even panel geometry. Concept‑side, you must place hands, eyes, and attention with intent. Production‑side, you must translate that intent into sensor chains, actuators, power budgets, and service logic. This article builds a shared language for designing controls that are beautiful, legible, and survivable—woven with human factors, HUD use, and diegetic UI.

Affordances, Signifiers, and Feedback: The Core Loop

Affordance is what a control can do; signifier is the visual/tactile cue that says “use me like this.” Feedback confirms action: motion, click, haptic, sound, or visual change. The loop should be unambiguous even in gloves, vibration, and stress. Big muscle: wheels, yokes, sticks, throttles. Fine muscle: toggles, rotaries, encoders, soft keys. For high‑risk functions (gear down, e‑stop, arming), use shape‑coded and guarded controls with unique textures and detents. Pair every critical act with feedback in at least two modalities (haptic + visual, or visual + audio).

Analog/Mechanical Controls: Pros, Cons, and Good Practices

Pros: direct feel, passive fail‑safe states (springs, cables), minimal latency, intuitive diagnosis. Cons: routing complexity, weight, limited geometry freedom, and compliance/backlash under load. Good practices: keep cable radii generous, provide adjusters at service points, isolate NVH so resonance doesn’t buzz the control, and route away from heat. Use positive detents for modes, progressive springs for feel, and over‑travel stops. Label stroke ranges and include mechanical position indicators visible from the eyebox.

Fly‑/Drive‑By‑Wire: Architecture and UX Implications

By‑wire abstracts the control into sensing (potentiometers/Hall sensors/force transducers), computing (control laws), and actuation (hydraulic/electric). Pros: flexible ergonomics, envelope protection, adaptive feel, integrable autonomy, and smaller mechanical intrusions. Cons: power and compute dependence, latency/jitter risk, mode confusion, and software faults. UX rules: always show who has authority (manual, assisted, autopilot/autodrive) with a persistent diegetic indicator; expose mode transitions with haptic/aural cues; and provide reversionary controls for degraded modes.

Force‑ vs. Position‑Sensing Controls

In by‑wire, the main design choice is force‑sensing (control barely moves; system measures applied force) versus position‑sensing (traditional throw; system reads position). Force‑sensing enables compact layouts and good high‑G operation; position‑sensing preserves muscle memory. Mix as needed: a force‑sensing sidestick with position‑sensing throttle; a force brake pedal with position accelerator. Specify artificial feel units (springs, magnets, motors) that create detents and resistance curves. Document latency budgets end‑to‑end (sensor → compute → actuator).

Haptics, Detents, and Artificial Feel

Great by‑wire controls feel physical. Use motorized detents for mode gates (e.g., gear, flap, reverse), texture coding on knobs, notch‑through effects for warnings, and vibrotactile cues tied to system states (stall/traction limits, proximity alerts). For analog controls, tune spring rates and friction to avoid freeplay. Production notes should include torque vs. displacement curves, detent forces, buzz thresholds, and glove compatibility.

Layout Patterns: HOTAS, Wheels‑Plus, and Bridge Logic

HOTAS (Hands On Throttle‑And‑Stick) keeps primary flight controls and key modes at the hands. Wheels‑plus layouts combine a steering wheel/yoke with thumb clusters (D‑pads, rotaries) for secondary tasks. Bridge logic groups helm, throttle, and nav/comms with clear talk lines between stations. Concept‑side, map reach envelopes and keep emergency controls within elbow range. Production‑side, give mount stiffness targets, breakaway features for crash safety, and tilt/telescope ranges.

Mode Management and “Don’t Make Me Guess”

Mode confusion kills UX. Tie modes to persistent diegetic signifiers: e.g., a thin light band along the yoke rim that changes pattern for Manual/Assist/Auto; HUD symbology that grows a caret when protections are active; throttle detents that hard‑stop at auto thrust max unless overridden. Publish a mode transition table in your packet: entry conditions, feedback cues, and exit conditions. Provide a hard reversion (mechanical backup, or a Direct/Fixed‑gain law) with a distinct control feel so the operator knows they are in limp‑home.

HUD & Diegetic UI: Integrating With Controls

HUDs and diegetic UI should mirror control states and place the next required action at the operator’s focal distance. Show flight‑path vector/trajectory cues, lane or route overlays, and commanded vs. actual markers during by‑wire operations. Use symbology declutter under high workload (gear down, terrain low). Edge‑lit bezels, pillar ladders, or rim LEDs can echo warnings without glare. Production‑side, specify brightness ranges, focal distance, color semantics, and washout handling.

Redundancy, Power, and Degraded Modes

By‑wire demands redundant sensors (dual/triple), dual power buses, and independent processors voting or monitoring. Actuators need runaway protection and jam tolerance. Define degraded modes: e.g., loss of rack power → fall back to manual hydraulic; loss of one sensor → median voting; total HUD loss → fallback displays. Place manual overrides (mechanical gear/freefall, direct brake hydraulic backup) where reachable under G and vibration.

EMI, Harnessing, and Environmental Design

Route signal and power separately, twist pairs, and shield sensors near motors/radios. Keep drip loops and strain relief at controls; specify IP ratings for exposed switches. For maritime and desert ops, call out salt fog and dust seals; for arctic, specify elastomers that remain compliant. Provide service loops so columns and sticks move without stressing wires. Include grounding and bonding points to control static and fault currents.

Safety, Guards, and Error‑Proofing

Guard red‑bar functions (arming, e‑stop, jettison) with lift‑to‑unlock covers, two‑stage presses, or pull‑then‑twist motions. Separate mutually exclusive controls (gear vs. flaps) by distance and shape to avoid slip errors. Use interlocks tied to WOW/airspeed/weight to prevent bad states (e.g., prevent gear‑up on ground). Provide checklist affordances—tabs or flag tags that seat flush only when the step is complete.

Accessibility, Gloves, and Motion Limits

Design for gloved hands and cold‑stiff fingers: bigger knobs, deeper knurls, 2–3 mm edge radii. Use anti‑glare textures and matte finishes. Provide adjustable sticks/wheels for anthropometric extremes, and ensure the eyebox still sees HUD/indicators across seat travel. For seated operators in rough ride, give hand anchors and wrist rests to stabilize fine inputs.

Training, Discoverability, and Cross‑Vehicle Consistency

Borrow established metaphors: clockwise = increase, up/forward = more, guarded red = last‑resort. Keep transfer learning between models—don’t move the gear lever without a very good reason. Provide guided discovery: soft labels that expand on hover/touch, or HUD tooltips during training mode. In military/industrial contexts, include night mode color/brightness standards and NVG‑safe symbology.

Data, Telemetry, and Event Capture

By‑wire systems should log pilot/driver inputs, mode states, faults, and actuator commands for debrief and maintenance. Design unobtrusive event markers (tap paddle to drop a timeline flag) that appear in post‑run tools. For analog systems, provide position sensors on critical controls or mechanical counters for cycles.

Maintenance & Modularity

Design faceplates and switch modules as Line‑Replaceable Units (LRUs) with captive fasteners and keyed connectors. Provide calibration routines (center stick, zero force) and self‑test at power‑on with clear pass/fail diegetic indicators. Include torque specs, seal kits, and pot/sensor part numbers in callouts. For analog linkages, show lubrication points, cable replacement paths, and inspection intervals.

Concept‑to‑Production Handshake

Close your sheet with targets: control throws or force ranges; detent forces; latency budgets; authority/mode map; power draw; redundancy level; IP/EMI specs; environmental ranges; and human‑factor dimensions (reach, clearances, eyebox). Include a wiring and hydraulic overview block diagram, plus failure trees (what the operator feels/sees when X fails).

Case Studies in a Paragraph

A rally EV uses by‑wire steering with a small oval yoke and motorized detents for drive modes; the HUD previews torque vectoring limits as a shaded band on the lane. Brake is force‑sensing with hydraulic backup; throttle is position‑sensing with a tactile kick‑down to signal regen override. A tilt‑rotor cockpit keeps HOTAS: a by‑wire collective/throttle with guarded detent gates and a force‑sensing sidestick; diegetic LEDs along the stick collar show envelope protections. A harbor bridge retains analog throttles and mechanical emergency stop while adding by‑wire azimuth control; mode authority is always shown on a pillar light ladder and mirrored in the HUD.

Final Encouragement

Controls are conversation. Whether you choose cables and springs or sensors and code, make the affordance obvious, the signifier clear, and the feedback undeniable. Tie modes to your HUD and diegetic UI so operators never guess who’s in charge. Do this, and your cockpits and bridges will feel inevitable to artists and engineers alike.