Search Issue Tracker
Fixed
Fixed in 1.5.0
Votes
0
Found in [Package]
1.2.0
1.3.0
1.5.0
Issue ID
ISXB-5
Regression
No
First connected input will not work when the second input is connected when using "MultiplayerEventSystem"
How to reproduce:
1. Open project "InputLocalMultiplayer.zip"
2. Enter Play Mode
3. Press Enter button and move with WASD, arrows, or a mouse
4. Press South Button on Gamepad and move with stick or buttons
5. Repeat 3rd step
Expected result: Both inputs are working
Actual result: First connected input (keyboard) is not working
Reproducible with: 1.2.0 (2019.4.36f1), 1.3.0 (2020.3.30f1, 2021.2.7f1, 2022.1.0b10, 2022.2.0a7)
Could not test with: 1.1.1 (Errors)
Notes:
- Reproducible in the Editor and in the Player
- If connecting Gamepad and then keyboard then the Gamepad will not work
- If disabling and enabling the first input after the 4th step then both inputs are working
- The colors of buttons are blurred (started in Input System 1.3.0)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
Resolution Note:
Fixed in: 1.5.0