Hardware database · 044F:B550

HOTAS Force Feedback Joystick

044F:B550 · 4 approved reports · first 2026-10-17, last 2026-10-30 · probe 1.1.2

Device class: joystick

Capability snapshots · latest per OS

What this device reports on each platform

Windows

4 reports · latest 2026-10-30 · probe 1.1.2

Microsoft Windows NT 10

Axes4

Buttons8

POVs1

FF sample period 1000 µs

Min time resolution 1000 µs

Firmware rev0x0100

Hardware rev0x0100

FF driver ver0x0001

Capability flags: DIDC_ATTACHED | DIDC_EMULATED | DIDC_POLLEDDATAFORMAT | DIDC_FORCEFEEDBACK | DIDC_FFATTACK | DIDC_FFFADE | DIDC_SATURATION | DIDC_POSNEGCOEFFICIENTS | DIDC_POSNEGSATURATION | DIDC_DEADBAND | DIDC_STARTDELAY

Supported effects 8

Constant Force

DIEFT_CONSTANTFORCE | 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 | POSNEGSATURATION | DEADBAND | STARTDELAY

Damper

DIEFT_CONDITION | SATURATION | POSNEGCOEFFICIENTS | POSNEGSATURATION | DEADBAND | STARTDELAY

Reported by OS

Submission count by OS family

Windows 4 reports

Test strength: 50% (1 report), 75% (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 4 reports

Did nothing x2 Weak damping x2

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

Pulled left x4

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

Pulled back x4

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

Pulled forward x4

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

Pulled right x3 Pulled diagonally x1

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

(no labels)

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

(no labels)

Saturation — 1 co-directional constants 4 reports

Pulled back x2 Soft pull x1

Saturation — 2 co-directional constants 4 reports

Pulled back x3 Strong pull x2

Saturation — 3 co-directional constants 4 reports

Pulled back x4 Strong pull x1

Sawtooth Down 4 reports

Asymmetric ramp pulses x3 Repeated ramping x1

Sawtooth Up 4 reports

Asymmetric ramp pulses x4

Sine 4 reports

Smooth oscillation x4

Spring 4 reports

Centered x2 Returns to center x2

Square 4 reports

Sharp pulses x4

Triangle 4 reports

Smooth oscillation x3 Rocking back and forth x1

Two-axis diagonal — diagonal 4 reports

Pulled diagonally x4

Direction consistency · constant-force direction tests

What the commanded directions actually did

Consistent with the documented DirectInput mapping

Scored responses15

Matched15

Mismatched0

Consistency100%

No direction1

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 x3	3	0

Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect	Reports	Create	Play	Stop
Damper	4	OK x4	OK x4	OK x4
Polarity sweep — DI east (right) (90°)	4	OK x4	OK x4	OK x4
Polarity sweep — DI north (away) (0°)	4	OK x4	OK x4	OK x4
Polarity sweep — DI south (toward) (180°)	4	OK x4	OK x4	OK x4
Polarity sweep — DI west (left) (270°)	4	OK x4	OK x4	OK x4
Ramp sweep — DI east (right) (90°)	4	FAIL: DIERR_DEVICENOTREG x4	(no effect created) x4	(no effect created) x4
Ramp sweep — DI north (away) (0°)	4	FAIL: DIERR_DEVICENOTREG x4	(no effect created) x4	(no effect created) x4
Saturation — 1 co-directional constants	4	OK x4	(none) x4	(none) x4
Saturation — 2 co-directional constants	4	OK x4	(none) x4	(none) x4
Saturation — 3 co-directional constants	4	OK x4	(none) x4	(none) x4
Sawtooth Down	4	OK x4	OK x4	OK x4
Sawtooth Up	4	OK x4	OK x4	OK x4
Sine	4	OK x4	OK x4	OK x4
Spring	4	OK x4	OK x4	OK x4
Square	4	OK x4	OK x4	OK x4
Triangle	4	OK x4	OK x4	OK x4
Two-axis diagonal — diagonal	4	OK x4	OK x4	OK x4

Failed effects · all approved reports

Effects that did not play cleanly

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

seen in 4 reports

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

seen in 4 reports

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.