Hardware database · 03EB:2056

Microsoft SideWinder Force Feedback Pro (USB adapter)

03EB:2056 · 12 approved reports · first 2026-06-08, last 2026-10-21 · probe 1.1.2

Device class: other

Capability snapshots · latest per OS

What this device reports on each platform

Windows

9 reports · latest 2026-10-21 · probe 1.1.2

Microsoft Windows NT 10

Axes8

Buttons16

POVs1

FF sample period not reported reliably

Min time resolution not reported reliably

Firmware rev0x0000

Hardware rev0x2056

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

Supported effects 12

Constant Force

DIEFT_CONSTANTFORCE | FFATTACK | FFFADE

Ramp Force

DIEFT_RAMPFORCE | FFATTACK | FFFADE

Square

DIEFT_PERIODIC | FFATTACK | FFFADE

Sine

DIEFT_PERIODIC | FFATTACK | FFFADE

Triangle

DIEFT_PERIODIC | FFATTACK | FFFADE

Sawtooth Up

DIEFT_PERIODIC | FFATTACK | FFFADE

Sawtooth Down

DIEFT_PERIODIC | FFATTACK | FFFADE

Spring

DIEFT_CONDITION

Damper

DIEFT_CONDITION

Inertia

DIEFT_CONDITION

Friction

DIEFT_CONDITION

Custom Force

DIEFT_CUSTOMFORCE

Linux

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

Unix 6

Axes5

Buttons13

POVs0

FF sample period 0 µs

Min time resolution 0 µs

Firmware rev0x0111

Hardware rev0x0000

FF driver ver0x0000

Capability flags: Linux evdev EV_FF; event=/dev/input/event2; ff_effects_max=40

Supported effects 11

Rumble

EV_FF 0x50

Periodic

EV_FF 0x51

Constant

EV_FF 0x52

Ramp

EV_FF 0x57

Square

EV_FF 0x58

Triangle

EV_FF 0x59

Sine

EV_FF 0x5A

SawtoothUp

EV_FF 0x5B

SawtoothDown

EV_FF 0x5C

Gain

EV_FF 0x60

Autocenter

EV_FF 0x61

Reported by OS

Submission count by OS family

Windows 9 reports

Linux 3 reports

Test strength: 75% (2 reports), not recorded (10 reports)

Test strength is the share of full force every effect played at, set on the app's checklist and never above 75%. Read weak or did-nothing answers against it. Reports from app versions before 1.1.1 do not record it.

What testers felt · all approved reports

Chip selections by effect

Damper 9 reports

Damped x6 Like syrup x2 Did nothing x1 Resists motion x1

Friction 9 reports

Drag x3 Sticky x2 Weak friction x2 Did nothing x1 Heavy x1 Strong friction x1

Inertia 9 reports

Resists changes in motion x5 Heavy x2 Did nothing x1 Lagging x1 Weak inertia x1

Saturation — 1 co-directional constants 9 reports

Pulled back x3 Pulled forward x2 Did nothing x1

Saturation — 2 co-directional constants 9 reports

Pulled back x6 Pulled diagonally x2 Strong pull x1

Saturation — 3 co-directional constants 9 reports

Pulled back x6 Brief jerk x2 Strong pull x2 Did nothing x1

Sawtooth Down 9 reports

Asymmetric ramp pulses x5 Repeated ramping x3 Did nothing x1

Sawtooth Up 9 reports

Asymmetric ramp pulses x7 Did nothing x1 Repeated ramping x1

Sine 9 reports

Smooth oscillation x6 Rocking back and forth x2 Did nothing x1

Spring 9 reports

Centered x5 Returns to center x4 Did nothing x1 Springy x1

Square 9 reports

Sharp pulses x7 Did nothing x1 Tapping x1

Triangle 9 reports

Smooth oscillation x4 Rocking back and forth x2 Slow x2 Did nothing x1 Fast x1

Two-axis diagonal — diagonal 9 reports

Pulled diagonally x6 Strong pull x3 Did nothing x1

Polarity sweep — DI east (right) (90°) 8 reports

Pulled left x5 Pulled right x2 Did nothing x1 Strong pull x1

Polarity sweep — DI north (away) (0°) 8 reports

Pulled back x4 Pulled left x2 Strong pull x2 Did nothing x1

Polarity sweep — DI south (toward) (180°) 8 reports

Pulled forward x6 Strong pull x2 Did nothing x1

Polarity sweep — DI west (left) (270°) 8 reports

Pulled right x5 Pulled diagonally x2 Did nothing x1 Strong pull x1

Linux Sawtooth Down 3 reports

Asymmetric ramp pulses x1 Did nothing x1 Repeated ramping x1

Linux Sawtooth Up 3 reports

Repeated ramping x2 Did nothing x1

Linux Sine 3 reports

Did nothing x1 Rocking back and forth x1 Smooth oscillation x1

Linux Square 3 reports

Did nothing x1 On-off pattern x1 Sharp pulses x1

Linux Triangle 3 reports

Did nothing x1 Rocking back and forth x1 Smooth oscillation x1

Linux constant force - backward pull 3 reports

Did nothing x2 Brief jerk x1

Linux constant force - forward pull 3 reports

Brief jerk x1 Did nothing x1

Linux constant force - left pull 3 reports

Did nothing x2 Brief jerk x1

Linux constant force - right pull 3 reports

Did nothing x2 Brief jerk x1

Linux ramp force - backward pull 3 reports

Pulled back x2 Did nothing x1

Linux ramp force - left pull 3 reports

Pulled left x2 Did nothing x1

Linux rumble 3 reports

Sharp pulses x2 Did nothing x1

Ramp sweep — DI east (right) (90°) 2 reports

Did nothing x1 Pulled left x1

Ramp sweep — DI north (away) (0°) 2 reports

Did nothing x1 Pulled back x1

Polarity sweep — DI east (0°) 1 report

Pulled back x1

Polarity sweep — DI north (270°) 1 report

Pulled right x1

Polarity sweep — DI south (90°) 1 report

Pulled left x1

Polarity sweep — DI west (180°) 1 report

Pulled forward x1

Direction consistency · constant-force direction tests

What the commanded directions actually did

Consistent with the documented DirectInput mapping

Scored responses28

Matched24

Mismatched4

Consistency86%

No direction20

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 x5 Pulled left x2	5	2
90° east (right)	Pulled left	Pulled left x6 Pulled right x2	6	2
180° south (toward)	Pulled forward	Pulled forward x7	7	0
270° west (left)	Pulled right	Pulled right x6	6	0

Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect	Reports	Create	Play	Stop
Damper	9	OK x9	OK x9	OK x9
Friction	9	OK x9	OK x9	OK x9
Inertia	9	OK x9	OK x9	OK x9
Sawtooth Down	9	OK x9	OK x9	OK x9
Sawtooth Up	9	OK x9	OK x9	OK x9
Sine	9	OK x9	OK x9	OK x9
Spring	9	OK x9	OK x9	OK x9
Square	9	OK x9	OK x9	OK x9
Triangle	9	OK x9	OK x9	OK x9
Linux Sawtooth Down	3	OK x3	OK x3	OK x3
Linux Sawtooth Up	3	OK x3	OK x3	OK x3
Linux Sine	3	OK x3	OK x3	OK x3
Linux Square	3	OK x3	OK x3	OK x3
Linux Triangle	3	OK x3	OK x3	OK x3
Linux constant force - backward pull	3	OK x3	OK x3	OK x3
Linux constant force - forward pull	3	OK x3	OK x3	OK x3
Linux constant force - left pull	3	OK x3	OK x3	OK x3
Linux constant force - right pull	3	OK x3	OK x3	OK x3
Linux ramp force - backward pull	3	OK x3	OK x3	OK x3
Linux ramp force - left pull	3	OK x3	OK x3	OK x3
Linux rumble	3	OK x3	OK x3	OK x3
Polarity sweep — DI east (right) (90°)	2	OK x2	OK x2	OK x2
Polarity sweep — DI north (away) (0°)	2	OK x2	OK x2	OK x2
Polarity sweep — DI south (toward) (180°)	2	OK x2	OK x2	OK x2
Polarity sweep — DI west (left) (270°)	2	OK x2	OK x2	OK x2
Ramp sweep — DI east (right) (90°)	2	OK x2	OK x2	OK x2
Ramp sweep — DI north (away) (0°)	2	OK x2	OK x2	OK x2
Saturation — 1 co-directional constants	2	OK x2	(none) x2	(none) x2
Saturation — 2 co-directional constants	2	OK x2	(none) x2	(none) x2
Saturation — 3 co-directional constants	2	OK x2	(none) x2	(none) x2
Two-axis diagonal — diagonal	2	OK x2	OK x2	OK x2

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.