FFB Probe Diagnostic
Current site language English
Download
Hardware database · CAFE:4022

test

CAFE:4022 · 1 approved report · first 2026-07-20, last 2026-07-20 · probe 1.0.4

Capability snapshots · latest per OS

What this device reports on each platform

Windows

1 report · latest 2026-07-20 · probe 1.0.4

Microsoft Windows NT 10
Axes1
Buttons8
POVs0
FF sample period not reported reliably
Min time resolution not reported reliably
Firmware rev0x0000
Hardware rev0x4022
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
Supported effects 12
Constant Force
DIEFT_CONSTANTFORCE
Ramp Force
0x00
Square
DIEFT_CONSTANTFORCE
Sine
DIEFT_CONSTANTFORCE
Triangle
DIEFT_CONSTANTFORCE
Sawtooth Up
DIEFT_CONSTANTFORCE
Sawtooth Down
DIEFT_CONSTANTFORCE
Spring
0x00
Damper
0x00
Inertia
0x00
Friction
0x00
Custom Force
DIEFT_CONSTANTFORCE
Reported by OS

Submission count by OS family

Windows 1 report
What testers felt · all approved reports

Chip selections by effect

Polarity sweep — DI east (right) (90°) 1 report
(no labels)
Polarity sweep — DI north (away) (0°) 1 report
(no labels)
Polarity sweep — DI south (toward) (180°) 1 report
(no labels)
Polarity sweep — DI west (left) (270°) 1 report
(no labels)
Saturation — 1 co-directional constants 1 report
Did nothing x1
Saturation — 2 co-directional constants 1 report
Did nothing x1
Saturation — 3 co-directional constants 1 report
Did nothing x1
Direction consistency · constant-force direction tests

What the commanded directions actually did

Not enough direction answers to draw a conclusion yet.

Scored responses0
Matched0
Mismatched0
No direction4
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 No direction 0 0
90° east (right) Pulled left No direction 0 0
180° south (toward) Pulled forward No direction 0 0
270° west (left) Pulled right No direction 0 0
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.