This is really weird.
So, when I set a shortcut to Capture + Home (binding doesn't matter), it breaks one of the dpad buttons on the left joycon (second in group) and jumbles the dpad buttons in general (they don't trigger the right bindings anymore).
When I set a shortcut involving the dpad and a face button on the right joycon, that made one of the dpad buttons trigger both its binding and the binding for the button that became broken simultaneously.
Setting shortcuts that only involve the left JoyCon still causes the issue.
Removing the shortcut fixes the issue.
Moving the left JoyCon to the third spot in the device group fixes this issue.
PS: if I move the left JoyCon to the third spot in the group, it starts working fine, but the same time gyro in both controllers becomes decoupled - if there are any gyro bindings, they're active for each JoyCon instead of just the first one in the group and Gyro Off/Toggle bindings only affect the gyro of the JoyCon whose button is bound to Gyro Off/Toggle. This might be intended behaviour though, idk.
Cheers
So, when I set a shortcut to Capture + Home (binding doesn't matter), it breaks one of the dpad buttons on the left joycon (second in group) and jumbles the dpad buttons in general (they don't trigger the right bindings anymore).
When I set a shortcut involving the dpad and a face button on the right joycon, that made one of the dpad buttons trigger both its binding and the binding for the button that became broken simultaneously.
Setting shortcuts that only involve the left JoyCon still causes the issue.
Removing the shortcut fixes the issue.
Moving the left JoyCon to the third spot in the device group fixes this issue.
PS: if I move the left JoyCon to the third spot in the group, it starts working fine, but the same time gyro in both controllers becomes decoupled - if there are any gyro bindings, they're active for each JoyCon instead of just the first one in the group and Gyro Off/Toggle bindings only affect the gyro of the JoyCon whose button is bound to Gyro Off/Toggle. This might be intended behaviour though, idk.
Cheers
Comment