72-direction outer-edge analysis

Measure joystick circularity, not just draw a circle.

Rotate one stick around its full edge to capture the outer envelope. Gamepad Bench reports angular coverage, roundness error, maximum and minimum radius, directional asymmetry and the actual trajectory.

Live trajectory5° direction binsLocal processing
Waiting for inputNo controller detected
0% angular coverage
Outer-edge traceLeft stick
Paused

The thin circle marks radius 1.00. The bright trace is the maximum radius captured in each 5° direction.

Connect a standard-mapped controller, choose a stick, then start the trace.

Roundness errormean absolute radial deviation
Maximum radiuslargest captured outer value
Minimum radiussmallest covered direction
Directional asymmetryrequires 80% coverage
01

Repeatable method

Trace the mechanical edge slowly, not a freehand circle.

The test needs the stick pushed against its physical gate. Moving inside the edge measures your hand path instead of the controller's available outer range.

01

Select one stick

Choose left or right. The test resets whenever you change sticks so data from separate mechanisms is never mixed.

02

Rotate against the edge

Push fully outward and make two or three slow rotations. Reverse direction once to reduce gaps caused by hand speed or corner transitions.

03

Stop above 80% coverage

Review the trace and metrics only after most directions are captured. Clear and repeat under the same connection when comparing changes.

Metric definitions

Each number answers a different question.

No single circularity score proves a stick is good or bad. Response curves, square ranges and firmware normalization differ by controller.

725° angular bins around the full rotation
MADRoundness error uses mean absolute radial deviation
Max / minOuter radius extremes among covered directions
L–R / U–DLargest opposite-direction average difference
02

Interpret the shape

Joystick circularity test FAQ

What does joystick circularity error mean?

This page divides the full rotation into 72 angular bins, keeps the largest radius captured in each direction and reports the mean absolute deviation from the average radius. It describes radial consistency, not aiming accuracy or input latency.

Why must I reach at least 80% angular coverage?

Maximum, minimum and directional comparisons are misleading when large parts of the circle were never sampled. The page withholds final metrics until at least 80% of the 5-degree direction bins contain an outer-edge sample.

Is a radius above 100% automatically bad?

No. Browser axes can form a square range where diagonal magnitude exceeds 1.00, and firmware may clamp or reshape the output. Compare shape consistency and behavior in the games you use rather than treating one universal percentage as a pass/fail limit.