Joystick Tester
Not connected- XAxis 0
- —
- YAxis 1
- —
- Twist—
- —
- Hat—
- —
- Position
- —
TipStick, throttle and pedals on separate USB cables? Move each one once; the page reads them all together.
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.
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.
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.
Stick, twist, hat and most buttons.
The throttle lever with its dials, sliders, mini stick and buttons.
One rudder axis, or three with toe brakes. Press each fully.
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.
The Centering card marks each stop. Dots inside the small ring are fine; dots outside the dashed ring (0.10) turn amber.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
This page reads any game controller, but the wheel and gamepad pages show more for those devices. Steering wheel tester →
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.