Hardware database · 03EB:204E

Microsoft SideWinder Force Feedback Pro (Adapt-FFB-Joy USB adapter)

03EB:204E · 4 approved reports · first 2026-08-08, last 2026-10-21 · probe 1.1.2

Device class: joystick

Capability snapshots · latest per OS

What this device reports on each platform

Windows

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

Microsoft Windows NT 10

Axes8

Buttons16

POVs1

FF sample period not reported reliably

Min time resolution not reported reliably

Firmware rev0x0000

Hardware rev0x204E

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

1 report · latest 2026-10-21 · probe 1.1.2

Unix 7

Axes7

Buttons16

POVs1

Firmware rev0x0111

Hardware rev0x0000

FF driver ver0x0000

Capability flags: Linux evdev EV_FF; 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 3 reports

Linux 1 report

Test strength: 35% (1 report), not recorded (3 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 3 reports

Damped x2 Like syrup x1

Friction 3 reports

Heavy x1 Sticky x1 Strong friction x1

Inertia 3 reports

Lagging x3 Heavy x1 Resists changes in motion 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 x2 Strong pull x2

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

Strong pull x2 Pulled back x1 Pulled forward 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

Brief jerk x1 Pulled back x1

Saturation — 3 co-directional constants 3 reports

Pulled back x2 Soft pull x1

Sawtooth Down 3 reports

Asymmetric ramp pulses x2 Repeated ramping x1

Sawtooth Up 3 reports

Asymmetric ramp pulses x2 Repeated ramping x1

Sine 3 reports

Rocking back and forth x2 Fast x1 Smooth oscillation x1

Spring 3 reports

Returns to center x2 Soft spring x1

Square 3 reports

Sharp pulses x3 Fast x1 Strong x1

Triangle 3 reports

Rocking back and forth x3 Fast x1

Two-axis diagonal — diagonal 3 reports

Pulled diagonally x3 Strong pull x1

Linux Sawtooth Down 1 report

Repeated ramping x1

Linux Sawtooth Up 1 report

Repeated ramping x1

Linux Sine 1 report

Rocking back and forth x1

Linux Square 1 report

On-off pattern x1

Linux Triangle 1 report

Rocking back and forth x1

Linux constant force - backward pull 1 report

Did nothing x1

Linux constant force - forward pull 1 report

Did nothing x1

Linux constant force - left pull 1 report

Did nothing x1

Linux constant force - right pull 1 report

Did nothing x1

Linux ramp force - backward pull 1 report

Built up gradually x1

Linux ramp force - left pull 1 report

Pulled left x1

Linux rumble 1 report

On-off pattern x1 Sharp pulses x1

Direction consistency · constant-force direction tests

What the commanded directions actually did

Consistent with the documented DirectInput mapping

Scored responses10

Matched9

Mismatched1

Consistency90%

No direction6

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 x2	2	0
90° east (right)	Pulled left	Pulled left x3	3	0
180° south (toward)	Pulled forward	Pulled forward x1 Pulled back x1	1	1
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
Linux Sawtooth Down	1	OK x1	OK x1	OK x1
Linux Sawtooth Up	1	OK x1	OK x1	OK x1
Linux Sine	1	OK x1	OK x1	OK x1
Linux Square	1	OK x1	OK x1	OK x1
Linux Triangle	1	OK x1	OK x1	OK x1
Linux constant force - backward pull	1	OK x1	OK x1	OK x1
Linux constant force - forward pull	1	OK x1	OK x1	OK x1
Linux constant force - left pull	1	OK x1	OK x1	OK x1
Linux constant force - right pull	1	OK x1	OK x1	OK x1
Linux ramp force - backward pull	1	OK x1	OK x1	OK x1
Linux ramp force - left pull	1	OK x1	OK x1	OK x1
Linux rumble	1	OK x1	OK x1	OK x1

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.