Microsoft SideWinder Force Feedback 2
045E:001B · 1 approved report · first 2026-05-09, last 2026-05-09 · probe 0.8.2-beta.1+20d4bc4d046c5d52834d04a667b2792706af9647
What this device reports to DirectInput
What the device claims it can play (12)
Submission count by OS family
Chip selections per effect
Create / Play / Stop HRESULTs by effect
| Effect | Create | Play | Stop |
|---|---|---|---|
| Square | OK | OK | OK |
| Sine | OK | OK | OK |
| Triangle | OK | OK | OK |
| Sawtooth Up | OK | OK | OK |
| Sawtooth Down | OK | OK | OK |
| Spring | OK | OK | OK |
| Damper | OK | OK | OK |
| Inertia | OK | OK | OK |
| Friction | OK | OK | OK |
These fields are kept for FFB-Bridge internal triage and are NOT displayed on the public hardware page. None of the values are PII.
The one private field
The only thing kept off this page is the per-effect free-text notes (responses[].notes) — what the tester typed in the answer text box. Everything else — capability flags, supported effects, OS breakdown, chip labels, HRESULT codes, failed effects, run errors — is published exactly as the device reported it. Read the full privacy contract →
Got this stick?
Run FFB Probe and share your result to improve this page.