FFB Probe Diagnostic
Current site language English
Download
Hardware database · 0F0D:017A

HORI Force Feedback Truck Control System Model: HPC-044

0F0D:017A · 3 approved reports · first 2026-08-27, last 2026-09-04 · probe 1.0.8

Capability snapshots · latest per OS

What this device reports on each platform

Windows

3 reports · latest 2026-09-04 · probe 1.0.8

Microsoft Windows NT 10
Axes8
Buttons54
POVs1
FF sample period 1000 µs
Min time resolution 1000 µs
Firmware rev0x0001
Hardware rev0x0001
FF driver ver0x0074
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 3 reports
What testers felt · all approved reports

Chip selections by effect

Damper 3 reports
(no labels)
Friction 3 reports
(no labels)
Inertia 3 reports
(no labels)
Polarity sweep — DI east (right) (90°) 3 reports
(no labels)
Polarity sweep — DI north (away) (0°) 3 reports
(no labels)
Polarity sweep — DI south (toward) (180°) 3 reports
(no labels)
Polarity sweep — DI west (left) (270°) 3 reports
(no labels)
Saturation — 1 co-directional constants 3 reports
Did nothing x2
Saturation — 2 co-directional constants 3 reports
Did nothing x2
Saturation — 3 co-directional constants 3 reports
Did nothing x3
Sawtooth Down 3 reports
(no labels)
Sawtooth Up 3 reports
(no labels)
Sine 3 reports
(no labels)
Spring 3 reports
(no labels)
Square 3 reports
(no labels)
Triangle 3 reports
(no labels)
Direction consistency · constant-force direction tests

What the commanded directions actually did

Not enough direction answers to draw a conclusion yet.

Scored responses0
Matched0
Mismatched0
No direction12
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 No direction 0 0
90° east (right) Pulled left No direction 0 0
180° south (toward) Pulled forward No direction 0 0
270° west (left) Pulled right No direction 0 0
Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect Reports Create Play Stop
Damper 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Friction 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Inertia 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Sawtooth Down 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Sawtooth Up 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Sine 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Spring 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Square 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Triangle 3
FAIL: DIERR_INVALIDPARAM x3
(no effect created) x3
(no effect created) x3
Failed effects · all approved reports

Effects that did not play cleanly

Damper
seen in 3 reports
Friction
seen in 3 reports
Inertia
seen in 3 reports
Sawtooth Down
seen in 3 reports
Sawtooth Up
seen in 3 reports
Sine
seen in 3 reports
Spring
seen in 3 reports
Square
seen in 3 reports
Triangle
seen in 3 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.