[Device Mapping] DIY FFBeast(Wheel)

[osnipezzini]

Device Name

DIY FFBeast(Wheel)

USB Vendor ID (hex)

045B

USB Product ID (hex)

59D7

Platform

Windows

Axis Count

8

Button Count

64

Hat/POV Count

0

Button Mapping

Physical Button	Raw Button Index
A (South)
B (East)
X (West)
Y (North)
Left Bumper
Right Bumper
Back/Select
Start/Menu
Left Stick Click
Right Stick Click
Guide/Home

Axis Mapping

Physical Axis	Raw Axis Index	Inverted?
Left Stick X	0	No
Left Stick Y	3	No
Right Stick X	4	No
Right Stick Y		No
Left Trigger		No
Right Trigger		No

D-Pad Configuration

No response

Verification

• All buttons I mapped respond correctly in PadForge's raw input visualization
• All axes I mapped move in the expected direction
• I tested with the device connected directly (not through a hub/adapter that might change the mapping)

[hifihedgehog]

Hey @osnipezzini — thanks for submitting your FFBeast wheel!

It looks like the mapping tables (button and axis indices) are empty — could you fill those in? We need the raw button/axis indices that PadForge shows on the Devices page when you select your wheel. For example, which raw axis index corresponds to steering, which to throttle/brake, etc.

Since this is a wheel (not a standard gamepad), you likely won't have mappings for things like A/B/X/Y or stick clicks — just fill in what applies to your device and leave the rest blank. The axis mappings are especially important for wheels.

Thanks!

[osnipezzini]

Thanks, I edited it, I'm just not sure if it should be exactly like that.

[hifihedgehog]

@osnipezzini We've updated the mapping file based on the standard HID wheel axis convention used by FFBeast (confirmed via AFFBWheel and FFBeast firmware docs):

Raw Axis	HID Axis	Physical Control	SDL Gamepad Field
a0	X	Steering	leftx
a1	Y	Accelerator	lefty
a2	Z	Brake	lefttrigger
a3	RX	Clutch	rightx
a4	RY	Aux 1	righty
a5	RZ	Aux 2	righttrigger

The updated mapping file is here: gamecontrollerdb_padforge.txt

Download it (click "Raw" on the gist page), place it next to PadForge.exe, and restart. Your FFBeast should be recognized with auto-mapping for the first 6 axes.

Please let us know:

1. Does axis 0 respond to steering?
2. Does axis 1 respond to your accelerator pedal?
3. Does axis 2 respond to your brake pedal?
4. Does axis 3 respond to your clutch (if you have one)?

We still need your button mapping too — press each button on your wheel while on PadForge's Devices page and note which raw index lights up. Even just the main ones (paddle shifters, face buttons) would be great.

Thanks!