ControllerTest.io

Joystick Tester

Not connected
Devices
Waiting · Press a button so the browser can see the device
Main stickTop view—
XAxis 0
—
YAxis 1
—
Twist—
—
Hat—
—
ThrottleMove to detect
Position
—

Centering

Not tested
Main stick · One dot per release, ±0.15
TwistTwist to detect
StickTwist
Max——
Releases——
Jitter——
Release to add a dot

All axes

Each cell is 1/40 of the travel —
AxisReachedValueEndsJitterJumps
0———
1———
2———
3———
4———
5———
6———
7———
8———
9———
Lit = reached, line = now, triangle = resting point; the last axis you moved is lit

Buttons

—
0123456789101112131415
PressedPossible bounce

Button log

Presses: 0
TimeButtonHeldGap
—No records yet
—
—
—
—
—
—
—
—
—
—
—

How to test

About 2 min
01
Press a buttonBrowsers need a press first.
02
Push to each sideThen twist the stick.
03
Move the throttleEnd to end, then each dial and slider.
04
Press each buttonCheck the log.

TipStick, throttle and pedals on separate USB cables? Move each one once; the page reads them all together.

What a page reads from a flight stick

8 parts

This flight stick test runs in the browser, so there is no HOTAS test software to install. To the browser, a stick, throttle or set of rudder pedals is a game controller: everything you push or twist reports as an axis, and every trigger, button and switch reports as a button. Logitech, Thrustmaster, VKB and Virpil all work the same way, so a T.Flight HOTAS test works like any other. Force feedback and lights aren't part of what the browser sees.

PartRead asShown in
1Main stickAxes 0 and 1Top view
2TwistOne axisTwist
3HatAn axis or buttonsHat
4ButtonsOne button eachButtons
5ThrottleOne axisThrottle slot
6Dials, slidersOne axis eachAll axes
7Rudder pedalsOne to three axesAll axes
8Force feedbackNone—
ReadNot readAxis numbers vary by model. Move a part to see which row lights up

Common flight stick problems

7 problems
SymptomIn the testUsual causeWhat to do
Doesn't centerShifted center or a weak springRecalibrate in the driver, or add a small center deadzone.
Falls shortPoor calibration, or a worn stop or sensorRecalibrate, then check the potentiometer.
Jumps at restDust or a poor contactClean the potentiometer with contact cleaner, or fit a Hall effect sensor.
Dead spotWorn trackClean the potentiometer, or replace it.
Double pressWorn switchReplace it with the same microswitch model.
Hat misses a directionWorn contacts, or the hat is in button modeCheck the hat mode, or repair it.
Device not listedThe browser hasn't seen that USB device yetPress a button on it, or try another USB port.
Amber marks the fault as it would appear in the test aboveAfter a fix, test again here

One press, two log rows: bounce and dropout

40 ms

Button bounce (one press registering twice) and dropouts last only tens of milliseconds. The button log records every press and release to the millisecond and marks a press within 40 ms of a release as Bounce.

NormalOne block and one log row, with the time held.
BounceA second press right after release; the log marks it Bounce. Usually a worn microswitch.
DropoutThe signal breaks while held, making two rows. Check contacts, solder and cable.
40 ms is this page's limit: no finger can release and press again that fast

How many devices is a HOTAS?

One per cable

A HOTAS (hands on throttle and stick) with separate USB cables shows up in the browser as three devices, each with its own axis and button numbers. This HOTAS tester reads them together and groups All axes by device. A stick and throttle on one cable count as one device.

StickDevice 1

Stick, twist, hat and most buttons.

ThrottleDevice 2

The throttle lever with its dials, sliders, mini stick and buttons.

Rudder pedalsDevice 3

One rudder axis, or three with toe brakes. Press each fully.

Chrome numbers at most 4 devices. Unplug any you aren't testing

Center error and center deadzone

Where it stops

A spring brings a flight stick back to center, but never to exactly the same spot. If the error is large, the aircraft turns on its own. A center deadzone treats a small range around the middle as 0 and hides the error.

One dot per release

The Centering card marks each stop. Dots inside the small ring are fine; dots outside the dashed ring (0.10) turn amber.

Center deadzone

Inside it, the axis reads 0; outside, it rises from 0. Set it just above your max error. Too large, and the middle feels dead.

Set the deadzone in the game's controls or the maker's software. The same applies to the twist axis

Frequently asked questions

12 questions

Why doesn't my browser detect my flight stick?

Press a button first

Browsers only see a controller after a button press or a stick movement, so press the trigger once the page is open. Use Chrome or Edge. A throttle or pedals on their own USB cable need a press or a move too; then they appear in the device row above the test area.

How do I test a HOTAS online?

Move each device

Open this page and move the stick, throttle and pedals once each. This HOTAS tester reads them at the same time, so a Thrustmaster T.Flight HOTAS test, a rudder pedal test or any other set needs no software. Push each axis to both ends and press every button.

Why don't the axis numbers match my controls?

Go by the number

Chrome on Windows numbers axes as the device reports them. On most flight sticks, 0 is left and right, 1 is forward and back and 5 is the twist; the throttle is often 2 or 6 and the hat 9. Models differ, so move a part and watch All axes.

Where does the hat show up?

As an axis or buttons

Most flight sticks report the hat as one axis that reads above 1 at rest. This page detects it and shows it in the Hat reading and in All axes; each of the eight directions lights up once pressed. Some sticks report the hat as four buttons, which show up in the Buttons card.

How much center error is normal?

Fine if you can't feel it

The Centering card draws each stop as a dot. The amber ring at 0.10 is the same limit the stick drift test uses: a reminder, not a verdict. If the aircraft drifts, calibrate in the driver or add a small center deadzone.

Why doesn't an axis reach both ends?

Calibrate in the driver

The small marks at each end of an axis bar light up once that end is reached. If an axis still stops short of ±1, recalibrate it in the Windows game controller settings or the maker's software. If it still falls short after that, the potentiometer or a stop is probably worn.

What do jitter and jumps mean?

Potentiometer wear

Jitter is small movement while the stick is untouched; a jump is a sudden spike that drops right back while the stick is still. Both get worse as a potentiometer collects dust and wears out, making your aim float or the throttle jump. Contact cleaner usually helps. Hall effect sensors have no contacts to wear out and rarely do this.

Why is one press logged twice?

Usually bounce

A press that comes within 40 ms of a release on the same button is marked Bounce. No finger moves that fast, so the cause is usually a worn microswitch, oxidized contacts or a poor connection. A break while the button is held looks the same in the log.

Can I test button boxes and flight panels?

Yes

If the computer sees them as game controllers, this page reads them: button boxes, landing gear levers and switch panels show up as buttons and axes. A toggle switch often reads as held in one position and released when you flip it back.

Can I test several devices at once?

Yes, all together

Each one is a separate device, and all are read at once, with All axes grouped by device. Chrome numbers at most 4 devices, so unplug the rest. Up to 128 buttons per device are read.

Does it work with racing wheels and gamepads?

Yes, but see their pages

This page reads any game controller, but the wheel and gamepad pages show more for those devices. Steering wheel tester →

Can it test force feedback and lights?

No

No. A web page only reads axes and buttons; it can't send force feedback or change the lights. Test those in the maker's app or in a game.