Flight control diagnostics

Joystick Tester

Move your flight stick and throttle so this joystick tester can show pitch, roll, twist, throttle, buttons, axes, and mapping.

Joystick and HOTAS Tester

Pitch, roll, twist, throttle, hat, and button state are arranged for flight controls.

No Controller Detected

Connect via USB or Bluetooth, then press any controller button to activate detection.

Pitch and roll

X +0.000 Y +0.000

Throttle axis+0.500

Twist axis+0.000

Axes

Axis 0+0.00000

Axis 1+0.00000

Axis 2+0.00000

Axis 3+0.00000

Buttons

+0.000

LB4

+0.000

RB5

+0.000

LT6

+0.000

RT7

+0.000

Back8

+0.000

Start9

+0.000

LS10

+0.000

RS11

+0.000

Up12

+0.000

Down13

+0.000

Left14

+0.000

Right15

+0.000

Flight Controls Have More Axes Than Gamepads

A joystick tester for HOTAS hardware needs to show pitch, roll, twist, throttle, hat switches, and many buttons without pretending the device is a console pad. This joystick tester starts with a pitch and roll scope, then adds throttle and twist meters plus raw values. That makes flight-stick behavior easier to inspect than a standard gamepad tester layout.

HOTAS devices vary widely. One stick may expose twist as axis 2, another may expose throttle there, and an adapter may reorder everything. The HOTAS tester displays raw browser axes and buttons so you can build bindings based on what the simulator or web app is likely to receive. Names are helpful, but indexes are the binding truth.

Use this controller tester after driver installation, firmware changes, powered hub changes, or profile switches. If a simulator ignores an axis, this page can tell you whether the browser sees it at all. If the joystick tester sees it clearly, the issue is probably inside the simulator profile.

Pitch, Roll, Twist, And Throttle

Move the stick slowly forward, back, left, and right. The pitch and roll scope should travel smoothly and return to center. A joystick tester can reveal noisy center behavior that makes aircraft trim feel wrong. If the dot shakes at rest, adjust deadzone in the simulator or inspect the hardware.

Twist and throttle are often mapped differently across devices. The HOTAS tester uses separate meters so you can identify whether a rotational rudder axis or throttle slider is moving. If the wrong meter responds, that is not necessarily a failure; it may simply mean the browser axis order differs from your expectation.

Hat switches may appear as buttons rather than axes. Check the raw button grid while pressing each hat direction. If one direction never appears in the joystick tester, try another mode, driver, or USB port. Flight hardware can require native support for every feature.

From Browser Values To Simulator Bindings

Use the joystick tester to create a binding map before opening a simulator. Note pitch, roll, rudder, throttle, trigger, secondary buttons, and hat indexes. Then configure the simulator with those values in mind. This reduces trial and error, especially when several USB flight devices are connected at once.

If the browser values are clean but the simulator jitters, check game deadzones, response curves, profiles, and duplicate bindings. If the joystick tester also jitters, compare another USB port, remove hubs, and check manufacturer calibration tools. Separating browser evidence from game configuration keeps troubleshooting focused.

This page does not provide force feedback, firmware flashing, or vendor-specific LED control. It is an input diagnostic for axes and buttons exposed to the browser. For specialized features, use manufacturer software after the basic HOTAS tester confirms the device is visible.

Diagnostic Glossary

HOTAS

Hands on throttle and stick, a common flight-control hardware setup.

Hat switch

A small multi-direction switch that may appear as several buttons.

Response curve

A simulator setting that changes how raw axis values translate to aircraft control.

Questions Users Ask

Short answers for common diagnostic decisions on this page.

Can this joystick tester see every HOTAS feature?

It shows features exposed through browser input APIs. Vendor-specific features may require native software.

Why does throttle appear on the wrong axis?

Axis order is device and driver dependent. Use the raw value that moves as the correct binding clue.

Should I calibrate in the browser?

Use the browser for evidence, then calibrate with simulator settings or manufacturer tools when needed.

Useful Next Checks

Inspect button mapping

Confirm indexes, labels, analog values, and unusual layouts.

Check polling rate

Sample browser input intervals while moving or pressing controls.

Compare input latency

Look at event timing clues and optional HID capability.

Read troubleshooting paths

Fix detection, Bluetooth, permission, browser, and mobile issues.