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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Fixed in: 1.5.0