FFB Probe Diagnostic
Current site language English
Download
Hardware database · 046D:C286

Logitech Force 3D Pro

046D:C286 · 5 approved reports · first 2026-05-09, last 2026-08-28 · probe 1.0.8

Capability snapshots · latest per OS

What this device reports on each platform

Windows

5 reports · latest 2026-08-28 · probe 1.0.8

Microsoft Windows NT 10
Axes4
Buttons12
POVs1
FF sample period 1000 µs
Min time resolution 1000 µs
Firmware rev0x0001
Hardware rev0x0001
FF driver ver0x0509
Capability flags: DIDC_ATTACHED | DIDC_EMULATED | DIDC_POLLEDDATAFORMAT | DIDC_FORCEFEEDBACK | DIDC_FFATTACK | DIDC_FFFADE | DIDC_SATURATION | DIDC_POSNEGCOEFFICIENTS | 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 | POSNEGCOEFFICIENTS | DEADBAND | STARTDELAY
Damper
DIEFT_CONDITION | SATURATION | POSNEGCOEFFICIENTS | DEADBAND | STARTDELAY
Inertia
DIEFT_CONDITION | SATURATION | POSNEGCOEFFICIENTS | DEADBAND | STARTDELAY
Friction
DIEFT_CONDITION | SATURATION | POSNEGCOEFFICIENTS | DEADBAND | STARTDELAY
Custom Force
DIEFT_CUSTOMFORCE | FFATTACK | FFFADE | STARTDELAY
Reported by OS

Submission count by OS family

Windows 5 reports
What testers felt · all approved reports

Chip selections by effect

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

What the commanded directions actually did

Consistent with the documented DirectInput mapping

Scored responses16
Matched16
Mismatched0
Consistency100%
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 Pulled back x4 4 0
90° east (right) Pulled left Pulled left x4 4 0
180° south (toward) Pulled forward Pulled forward x4 4 0
270° west (left) Pulled right Pulled right x4 4 0
Technical results · all approved reports

Create / Play / Stop outcomes by effect

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