FFB Probe Diagnostic
Current site language English
Download
Hardware database · 346E:1003

MOZA AY90 FFB Base

346E:1003 · 3 approved reports · first 2026-07-28, last 2026-08-29 · probe 1.0.8

Capability snapshots · latest per OS

What this device reports on each platform

Windows

3 reports · latest 2026-08-29 · probe 1.0.8

Microsoft Windows NT 10
Axes8
Buttons128
POVs1
FF sample period not reported reliably
Min time resolution not reported reliably
Firmware rev0x0000
Hardware rev0x1003
FF driver ver0x0001

A reported force-feedback interval or resolution of 1,000,000 µs (1 Hz) or more is firmware filler rather than a capability, and 1,000,000 µs is what this device reports. It is shown as unreported instead of being republished here.

Capability flags: DIDC_ATTACHED | DIDC_EMULATED | DIDC_FORCEFEEDBACK | DIDC_FFATTACK | DIDC_FFFADE | DIDC_SATURATION | DIDC_DEADBAND
Supported effects 11
Constant Force
DIEFT_CONSTANTFORCE | FFATTACK | FFFADE | STARTDELAY
Ramp Force
DIEFT_RAMPFORCE | FFATTACK | FFFADE | STARTDELAY
Square
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Sine
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Triangle
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Sawtooth Up
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Sawtooth Down
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Spring
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY
Damper
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY
Inertia
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY
Friction
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY
Reported by OS

Submission count by OS family

Windows 3 reports
What testers felt · all approved reports

Chip selections by effect

Damper 3 reports
Did nothing x2 Like syrup x1 Resists motion x1 Weak damping x1
Friction 3 reports
Did nothing x2 Sticky x1 Weak friction x1
Inertia 3 reports
Did nothing x2 Resists changes in motion x1 Weak inertia x1
Polarity sweep — DI east (right) (90°) 3 reports
Pulled left x3 Strong pull x1
Polarity sweep — DI north (away) (0°) 3 reports
Pulled back x3 Strong pull x2
Polarity sweep — DI south (toward) (180°) 3 reports
Pulled forward x3 Strong pull x1
Polarity sweep — DI west (left) (270°) 3 reports
Pulled right x3 Strong pull x1
Saturation — 1 co-directional constants 3 reports
Pulled back x1 Soft pull x1
Saturation — 2 co-directional constants 3 reports
Pulled back x2 Strong pull x2
Saturation — 3 co-directional constants 3 reports
Strong pull x3 Pulled back x2
Sawtooth Down 3 reports
Repeated ramping x3 Fast x1 Weak x1
Sawtooth Up 3 reports
Repeated ramping x3 Buzzing x1 Fast x1
Sine 3 reports
Smooth oscillation x3 Fast x1 Rocking back and forth x1 Strong x1 Weak x1
Spring 3 reports
Returns to center x2 Did nothing x1 Soft spring x1 Strong spring x1
Square 3 reports
Fast x2 On-off pattern x2 Sharp pulses x2 Strong x1
Triangle 3 reports
Fast x2 Rocking back and forth x2 Weak x1
Two-axis diagonal — diagonal 3 reports
Pulled forward x2 Pulled left x2 Pulled diagonally x1 Strong pull x1
Direction consistency · constant-force direction tests

What the commanded directions actually did

Consistent with the documented DirectInput mapping

Scored responses12
Matched12
Mismatched0
Consistency100%
No direction0
Several directions0
Unparseable0

Scoring covers the Windows polarity sweep and the Linux constant-force tests. A commanded direction is the direction the force comes from, so 0° should move the stick toward the tester. Scoring uses the documented mapping: 0° → Pulled back, 90° → Pulled left, 180° → Pulled forward, 270° → Pulled right. Answers that name more than one direction are counted separately and never scored.

Commanded Expected Observed Matched Mismatched
0° north (away) Pulled back Pulled back x3 3 0
90° east (right) Pulled left Pulled left x3 3 0
180° south (toward) Pulled forward Pulled forward x3 3 0
270° west (left) Pulled right Pulled right x3 3 0
Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect Reports Create Play Stop
Damper 3
OK x3
OK x3
OK x3
Friction 3
OK x3
OK x3
OK x3
Inertia 3
OK x3
OK x3
OK x3
Sawtooth Down 3
OK x3
OK x3
OK x3
Sawtooth Up 3
OK x3
OK x3
OK x3
Sine 3
OK x3
OK x3
OK x3
Spring 3
OK x3
OK x3
OK x3
Square 3
OK x3
OK x3
OK x3
Triangle 3
OK x3
OK x3
OK x3
Diagnostic visibility · current policy

Technical diagnostics are aggregated on this page so driver authors and tool builders can compare what multiple testers saw, including Windows and Linux runs for the same VID:PID. They use closed result names and path-redacted errors; the private response-notes field includes typed text and the probe-measured motion.

What's NOT on this page

The one private field

The per-effect responses[].notes field stays off this page. It can contain optional typed text and the probe-measured motion. Capability flags, supported effects, OS breakdown, test strength, chip labels, result codes, failed effects, and run errors can be published in aggregate or as a latest-per-platform snapshot. Read the full privacy contract →

Measured motion is what the probe saw on the stick's X and Y axes while each effect played: the signed peak movement as a percentage of the axis's half range, for example X peak +25.1%. It is measured from where the stick rested when the effect started, so it can exceed 100% when the stick rests off-centre. Condition effects such as spring and damper are not expected to move a centred stick.

Got this stick?

Run FFB Probe and share your result to improve this page.