Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://steamcommunity.com/groups/bigpicture/discussions/3/7004880943562398178/#c7004881118891628910
Holy crap, that's exactly what I was looking for, as I also have the Bluetooth Pro 2! Thank you so much!
Is this for D-input mode, or will it work in any mode?
In the other modes the Pro 2 is bound by the specs/protocol of the controller it's operating as - the paddles only output existing controls rather than be their own independent, unique button.
Okay, that's kind of what I thought. It's a lot to sacrifice, since you're losing gyro, analog triggers, and rumble in D-input mode, but it's still great that it's possible. Thanks again for sharing that research.
But yeah, gotta pick the right mode for the preference lol
X-input: +rumble, +analog triggers, -gyro, -independent paddles, +button remapping
Switch: +rumble, -analog triggers, +gyro, -independent paddles, +button remapping
D-input: -rumble, +analog triggers, -gyro, +independent paddles, +button remapping
MacOS: +rumble, +analog triggers, -gyro, -independent paddles, -button remapping
What we need is 8BitDo to write their own protocol that includes everything, then pass the info to the Steam Input team or let them work it out...
Save the following in a new text file:
Change the file extension to .reg and run the file.
Could check with joy.cpl and should see the trigger axes.
Do the controller setup process in Steam.
I remember the first time doing the setup in Steam, it wasn't mapping one of the sticks properly (think it was right stick Y axis). I just went through and mapped all that mapped correctly, skipping the problem bind, then corrected the problem bind in the mapping string with the same process linked in the first post.
what the binds ended up looking as:
That registry edit, is that specifically for this controller, or for all D-input devices on the system?
The device is specified by its Vendor ID and Product ID:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_2DC8&PID_6006\Axes\3
2DC8 is 8BitDo's vendor ID, Product ID 6006 is the controller in D-input mode over BT, PID 6003 over USB.
I got the procedure from these two Reddit posts regarding the Stadia controller, and just adapted stuff for us
https://www.reddit.com/r/Stadia/comments/edqrd1/comment/hiaw1vi/
https://www.reddit.com/r/Stadia/comments/edqrd1/comment/k8oh89y/
Woooh that Steam Input x 8BitDo collab is happening!!!
https://steamcommunity.com/app/353370/discussions/0/1755780323773182548/#c530970010564207028
What we're doing in this thread works because 1) the controller reports its additional buttons to Windows and 2) it does so for DirectInput (that's my understanding anyway).
Razer recently released firmware which made the Wolverine V3 in PC mode compatible with Synapse 4, so it seems to me it reports the buttons to the OS. If that's correct, then I believe if the Steam Input team investigate they can have Steam recognise the M-buttons...
Holy crap, that's genuinely fantastic. Valve has already made system updates for the Steam Deck specifically for 8BitDo controllers, so I'm glad they're still working with them.