Search Issue Tracker
Active
Under Consideration for 1.14.X
Votes
0
Found in [Package]
1.14.0
Issue ID
ISXB-1579
Regression
No
Player Input Manager assigns wrong indexes for newly connected devices when the previously disconnected controllers are reconnected
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter the Play Mode
4. Connect 3 controllers by pressing the D-pad down button (remember the sequence in which they were connected)
5. Observe the indexes of the connected players in the Game View
6. Disconnect the first 2 controllers by pressing the D-pad up button
7. Connect one of the disconnected controllers again
8. Observe the indexes of the connected players in the Game View
Expected result: Smallest unused index will be used for the newly connected device, which should be 0. The text shows “Connected Players: 0, 2“
Actual result: The newly assigned index is calculated by subtracting 1 from the previous smallest index. The text shows “Connected Players: 1, 2“
Reproducible with: 1.12.0, 1.13.0, 1.13.1, 1.14.0 (2022.3.63f1)
Reproducible on: M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment