You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Nvidia shield controller (0x0955, 0x7214) is supported for button presses, but there's no code for the rumble motors to work. This controller has 2 motors.
Rationale
Rumble support is good in games and adds to the game experience
Additional Details
I have a couple of these controllers and can test code mods/compile the source for minor changes and to help with testing. If you can point out to a capture program to log the motor commands I can let you know what readings I get if that information would be helpfull.
The text was updated successfully, but these errors were encountered:
You can capture packets on a PC using Wireshark. You can capture either USB or Bluetooth traffic, but you will need to make sure you install the optional USB capture driver during the initial setup (yes, for Bluetooth too). It might also be enough to grab the hid report descriptor, but this can probably be seen in the packet capture too.
There was no need to remap those, just changing the above fixes so the correct buttons are used.
I also have an Nvidia Shield TV, it might be faster just using an Android app to capture the hex values for the buttons as I think there's an app for that already made, I'll try wireshark though as I've not used it before.
Feature Description
Currently Nvidia shield controller (0x0955, 0x7214) is supported for button presses, but there's no code for the rumble motors to work. This controller has 2 motors.
Rationale
Rumble support is good in games and adds to the game experience
Additional Details
I have a couple of these controllers and can test code mods/compile the source for minor changes and to help with testing. If you can point out to a capture program to log the motor commands I can let you know what readings I get if that information would be helpfull.
The text was updated successfully, but these errors were encountered: