Description
The Stadia Controller (running the official Bluetooth Mode firmware) is not being correctly mapped within the Cannoli frontend. The triggers (L2/R2) are detected as constant negative axis values, which prevents them from being used as functional inputs in the navigation profile and passed correctly to emulated cores.
Observed Behavior
In the Cannoli Navigation profile, L2 and R2 are captured as (-1) while in the resting state.
This constant signal causes "ghost inputs" or prevents the software from recognizing when the trigger is actually being pulled.
Multiple UNKNOWN (0) entries appear, likely due to how the Stadia Controller reports its HID descriptor.
Description
The Stadia Controller (running the official Bluetooth Mode firmware) is not being correctly mapped within the Cannoli frontend. The triggers (L2/R2) are detected as constant negative axis values, which prevents them from being used as functional inputs in the navigation profile and passed correctly to emulated cores.
Observed Behavior
In the Cannoli Navigation profile, L2 and R2 are captured as (-1) while in the resting state.
This constant signal causes "ghost inputs" or prevents the software from recognizing when the trigger is actually being pulled.
Multiple UNKNOWN (0) entries appear, likely due to how the Stadia Controller reports its HID descriptor.