Stadia controller L and R Trigger doesn't work. But everything else works MacOS.
opened this issue · comments
Hello, this is my first issue on GitHub I hope I respect the terms of use, thanks for your indulgence.
I am currently using a Mac mini M1 and a Stadia controller. In the Parsec application the controller is correctly recognized and all the buttons work except the Trigger L and R keys
On the site Gamepad tester the keys work very well, and they have the identities B6 and B7
while in the Parsec application it is written V2+ and V5+.
I guess that's a start.
I hope we can find a solution
I'm also having this same issue. Only the triggers don't work. Every other app detects it
Facing the same issue. Parsec on Ubuntu doesn't recognize L trigger and R trigger for Stadia controller. Every other application detects it as mentioned by Ethan.
B6 and B7 are constantly 0 in the raw data on Parsec. Gamepad tester shows them correctly.
Also having this problem, has there been any update?
Same issue here, and I can't even remap the keys. Any hint to solve it?
Having a similar problem with my ps4 controller on Nvidia shield. Triggers are digital. Only parsec app has this issue on shield controller triggers works w other games.
same problem here
I have the same issue with my Dualshock 4 using Parsec on my Nvidia Shield Pro. The triggers work fine in Moonlight and GeForce Now. Any suggestions?
I got the same problem with Ipega controller using Parsec in Android. Triggers work in other applications.
+1
Is there any update on this?
Is there any update on this?
I guess we habe to Wait for a Google Driver
At least on Linux machines, I found a temporary solution for the problem.
What I did to make it work is use xboxdrv to emulate an XBox-Controller from the Stadia controller input and use the emulated controller as input for Parsec.
To make it work, I just had to run this command:
sudo xboxdrv --evdev /dev/input/event22 --evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_Z=x2,ABS_RZ=y2,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y,ABS_BRAKE=lt,ABS_GAS=rt --evdev-keymap BTN_A=a,BTN_B=b,BTN_X=x,BTN_Y=y,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_TL=lb,BTN_TR=rb,BTN_START=start,BTN_SELECT=select,BTN_MODE=guide,BTN_TRIGGER_HAPPY1=tl,BTN_TRIGGER_HAPPY2=tr,BTN_TRIGGER_HAPPY3=rt,BTN_TRIGGER_HAPPY4=lt --mimic-xpad --axismap -Y1=Y1,-Y2=Y2
You have to replace the event22 with the device number of your controller. To find the correct device number, just run evtest. The Stadia controller should be listed there with the corresponding number.
Parsec should now recognize the XBox-Controller and everything should work fine.
I took the button map from this gist.
As I said, this is just a solution for Linux machines. Maybe there is something similar to xboxdrv on Windows and Mac.
If you test the Stadia Controller with https://gamepad-tester.com/ it works fine. When testing the raw input with Parsec the triggers detect input when the L and R shoulder buttons are pressed.
As per biller-aivy comment below, I did my testing over Bluetooth connection.
There are Bluetooth connection possible now
There are Bluetooth connection possible now
On macOS it doesn't detect the controller at all when using BT connection. http://gamepad-tester.com works without a problem. So, with bt it's even worse than via usb.
There are Bluetooth connection possible now
On macOS it doesn't detect the controller at all when using BT connection. http://gamepad-tester.com works without a problem. So, with bt it's even worse than via usb.
Hello all, it's still not working now ?
Thanks
Yesterday they released the version 150-88. According to the changelog Stadia Controllers are now fully supported by all platforms.
Xbox One S Gamepad Controller does not have R2 and L2 in Parsec on Android