FFB Probe Diagnostic
Current site language English
Download
Hardware database · 25BB:0121

Brunner FFB-G

25BB:0121 · 10 approved reports · first 2026-07-22, last 2026-08-20 · probe 1.0.8

Capability snapshots · latest per OS

What this device reports on each platform

Windows

10 reports · latest 2026-08-20 · probe 1.0.8

Microsoft Windows NT 10
Axes8
Buttons60
POVs1
FF sample period not reported reliably
Min time resolution not reported reliably
Firmware rev0x0000
Hardware rev0x0121
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 12
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
Custom Force
DIEFT_CUSTOMFORCE | SATURATION | DEADBAND | STARTDELAY
Reported by OS

Submission count by OS family

Windows 10 reports
What testers felt · all approved reports

Chip selections by effect

Damper 10 reports
Damped x7 Resists motion x2 Did nothing x1
Friction 10 reports
Sticky x5 Strong friction x2 Weak friction x2 Did nothing x1
Inertia 10 reports
Heavy x5 Weak inertia x3 Did nothing x1 Lagging x1
Polarity sweep — DI east (right) (90°) 10 reports
Pulled forward x6 Pulled right x4
Polarity sweep — DI north (away) (0°) 10 reports
Pulled left x5 Pulled right x5
Polarity sweep — DI south (toward) (180°) 10 reports
Pulled left x5 Pulled forward x4 Pulled back x1
Polarity sweep — DI west (left) (270°) 10 reports
Pulled back x9 Pulled right x1
Saturation — 1 co-directional constants 10 reports
Did nothing x3 Strong pull x2 Pulled left x1 Pulled right x1
Saturation — 2 co-directional constants 10 reports
Pulled right x2 Soft pull x2 Brief jerk x1 Strong pull x1
Saturation — 3 co-directional constants 10 reports
Pulled right x3 Brief jerk x2 Soft pull x2 Pulled forward x1
Sawtooth Down 10 reports
Asymmetric ramp pulses x4 Strong x2 Weak x2 Repeated ramping x1 Slow x1
Sawtooth Up 10 reports
Asymmetric ramp pulses x6 Weak x2 Buzzing x1 Fast x1
Sine 10 reports
Smooth oscillation x7 Weak x2 Rocking back and forth x1
Spring 10 reports
Centered x5 Strong spring x2 Did nothing x1 No centering x1 Returns to center x1
Square 10 reports
Sharp pulses x6 Tapping x2 Weak x2
Triangle 10 reports
Rocking back and forth x4 Smooth oscillation x3 Weak x2 Slow x1
Two-axis diagonal — diagonal 10 reports
Pulled diagonally x8 Strong pull x2
Known device behaviour · Brunner DirectX mode

Directions are turned by 90° in DirectX mode

Brunner bases map their axes rotated by 90° in DirectX mode: a 0° force pulls right, 90° forward, 180° left and 270° back. This is Brunner's firmware behaviour, not a fault. FFB-Probe records it as measured and does not correct it, so the direction card can report an X/Y axis swap for this device. For the tests FFB-Probe also raises the base's stored DirectX gains, 50% from the factory, to 100% and restores them afterwards.

Direction consistency · constant-force direction tests

What the commanded directions actually did

Reports are consistent with an X/Y axis swap

Scored responses40
Matched5
Mismatched35
Consistency13%
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 left x5 Pulled right x5 0 10
90° east (right) Pulled left Pulled forward x6 Pulled right x4 0 10
180° south (toward) Pulled forward Pulled left x5 Pulled forward x4 Pulled back x1 4 6
270° west (left) Pulled right Pulled back x9 Pulled right x1 1 9
Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect Reports Create Play Stop
Damper 10
OK x10
OK x10
OK x10
Friction 10
OK x10
OK x10
OK x10
Inertia 10
OK x10
OK x10
OK x10
Sawtooth Down 10
OK x10
OK x10
OK x10
Sawtooth Up 10
OK x10
OK x10
OK x10
Sine 10
OK x10
OK x10
OK x10
Spring 10
OK x10
OK x10
OK x10
Square 10
OK x10
OK x10
OK x10
Triangle 10
OK x10
OK x10
OK x10
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.