FIX: PlayerInput.Instantiate not handling control schemes correctly. #796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
User report: https://forum.unity.com/threads/playerinput-instantiate-ignores-controller-schemes-for-multiplayer-with-players-on-same-device.730868/
The following used to result in two players with both having all keyboard bindings from all control schemes active rather than one using "KeyboardWASD" only and the other using "KeyboardArrows" only. Was a problem in
InputUser
where the order in which actions were set on a user WRT when its control scheme was set ended up mattering when it shouldn't.