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
{{ message }}
This repository has been archived by the owner on Mar 9, 2023. It is now read-only.
First of all, fantastic library, very much appreciate that it was shared with the world. Also realise that there's not much traction on this anymore so this may never be answered!
Using Unity 2020.3.33f1 on Mac I'm finding that very occasionally - maybe 1 in 100 plays - that my game starts up and the button mapping for the controller is wrong. Stick x direction is being triggered without moving and buttons are debugging as different button presses. Stop/restart or reload of scene fixes it. Not been able to consistently replicate and can't confirm if its isolated to a specific OS or version.
Mac itself - macOS 12.3.1 - has connection issues with a Joy-Con anyway, disconnects itself randomly after approx. 15-20 mins. That appears to be a hardware issue unrelated to the library as have read about it elsewhere.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First of all, fantastic library, very much appreciate that it was shared with the world. Also realise that there's not much traction on this anymore so this may never be answered!
Using Unity 2020.3.33f1 on Mac I'm finding that very occasionally - maybe 1 in 100 plays - that my game starts up and the button mapping for the controller is wrong. Stick x direction is being triggered without moving and buttons are debugging as different button presses. Stop/restart or reload of scene fixes it. Not been able to consistently replicate and can't confirm if its isolated to a specific OS or version.
Mac itself - macOS 12.3.1 - has connection issues with a Joy-Con anyway, disconnects itself randomly after approx. 15-20 mins. That appears to be a hardware issue unrelated to the library as have read about it elsewhere.
The text was updated successfully, but these errors were encountered: