Skip to content

Trackpoint Usage Guide

This guide defines how the KN-86’s two trackpoints are used across the system and in cartridges. It covers the input model, recommended and discouraged uses, audio independence, system-wide conventions, and the hardware configuration.

  • The trackpoints are used as stick-and-throttle style analog input (e.g. drone piloting, rec driving), not primarily as a mouse cursor. Cursor use is limited.
  • They drive fast, smooth long vertical scrolling.
  • The input model is dual-analog, exposed as a platform capability.
  • The two strongest fits are drone pilot and lockpick.
  • Anti-pattern — rotary-encoder-in-disguise: if an interaction is really a single-dial / knob control, it is not a good trackpoint use. Reserve the trackpoint for genuine analog input.
  • Audio is not the control or feedback channel. The audio-first framing elsewhere in the docs is overstated.
  • Some sound is present (using the chip during play), but every trackpoint interaction must remain fully playable with sound off — operators may not have sound on or up.
  • Long vertical scroll: one trackpoint is used consistently for long vertical scroll across the system.
  • Clicks: the trackpoint modules have buttons that simulate clicks; use them for select / commit.
  • Side-by-side compare: in Black Ledger, the two trackpoints compare the two sides of a ledger / spreadsheet / data set.
  • Considered: 1 rotary encoder (left) + 1 trackpoint (right), which would open up additional interactions.
  • Finding: a rotary encoder is not available as a holykeebs purchase for the Ferris Sweep. The holykeebs pointing options are trackpoint / touchpad / trackball — there is no encoder option and no encoder footprint. An encoder would only be a custom hand-wired mod, and the existing board already has two trackpoints soldered (one-shot solder).
  • Fallback: if the encoder isn’t viable, make do with two trackpoints, or implement only one of them.
  • WETWARE (like Operation)
  • Tachikoma