However, the extension doesn't have proper control mapping for the joysticks so it's effectively unusable. I tried the Control Stadia Chrome Extension and with this extension, Stadia actually detects the controller. (I know that it's only supposed to work for USB connected controllers but the 360Controller software wouldn't pick up the controller whether connected by cable or wireless). I tried using the 360Controller patch that gets put forward as a solution by 70% of online articles but that didn't work. I tested it with apps like Controllers Lite and they all pick up the controller perfectly when connected by Bluetooth. Chrome Canary) and in incognito mode per Stadia support's suggestions, but that didn't work.
I also tried the controller in other Chrome browsers (e.g. I updated the controller on a Windows computer with the Xbox Accessories app but that didn't help. On mac it's detected by when connected by Bluetooth (but not when connected by USB) and it works in Steam but doesn't get detected by Stadia.
It gets detected by Stadia and works perfectly in Chrome on a Windows computer. I'm experiencing this exact issue using an official Microsoft Xbox one controller.
