Hardware database · 11FF:3245

PXN V10

11FF:3245 · 2 approved reports · first 2026-06-03, last 2026-09-24 · probe 1.0.8

Capability snapshots · latest per OS

What this device reports on each platform

Windows

2 reports · latest 2026-09-24 · probe 1.0.8

Microsoft Windows NT 10

Axes7

Buttons24

POVs1

FF sample period not reported reliably

Min time resolution not reported reliably

Firmware rev0x0000

Hardware rev0x3245

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 | DIDC_SATURATION | DIDC_DEADBAND

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 | SATURATION | DEADBAND

Damper

DIEFT_CONDITION | SATURATION | DEADBAND

Inertia

DIEFT_CONDITION | SATURATION | DEADBAND

Friction

DIEFT_CONDITION | SATURATION | DEADBAND

Custom Force

DIEFT_CUSTOMFORCE | SATURATION | DEADBAND

Reported by OS

Submission count by OS family

Windows 2 reports

What testers felt · all approved reports

Chip selections by effect

Damper 2 reports

Did nothing x1 Resists motion x1

Friction 2 reports

Did nothing x1 Strong friction x1

Inertia 2 reports

Did nothing x1 Resists changes in motion x1

Saturation — 1 co-directional constants 2 reports

Did nothing x2

Saturation — 2 co-directional constants 2 reports

Did nothing x2

Saturation — 3 co-directional constants 2 reports

Did nothing x2

Sawtooth Down 2 reports

Did nothing x1 Fast x1

Sawtooth Up 2 reports

Did nothing x1 Fast x1

Sine 2 reports

Did nothing x1 Fast x1

Spring 2 reports

Did nothing x1 No centering x1

Triangle 2 reports

Did nothing x1 Fast x1

Two-axis diagonal — diagonal 2 reports

Pulled left x2

Polarity sweep — DI east (0°) 1 report

Did nothing x1

Polarity sweep — DI east (right) (90°) 1 report

Pulled left x1

Polarity sweep — DI north (270°) 1 report

Pulled right x1

Polarity sweep — DI north (away) (0°) 1 report

Did nothing x1

Polarity sweep — DI south (90°) 1 report

Pulled left x1

Polarity sweep — DI south (toward) (180°) 1 report

Pulled left x1

Polarity sweep — DI west (180°) 1 report

Did nothing x1

Polarity sweep — DI west (left) (270°) 1 report

Pulled right x1

Square 1 report

Did nothing x1

Direction consistency · constant-force direction tests

What the commanded directions actually did

Consistent with the documented DirectInput mapping

Scored responses5

Matched4

Mismatched1

Consistency80%

No direction3

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	Pulled left x2	2	0
180° south (toward)	Pulled forward	Pulled left x1	0	1
270° west (left)	Pulled right	Pulled right x2	2	0

Technical results · all approved reports

Create / Play / Stop outcomes by effect

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