Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.7.0
1.8.0-pre.2
Issue ID
ISXB-719
Regression
No
“Have reached maximum player count of 2” error is thrown instead of a warning when the connected Gamepads count is bigger than Max Player Count
Reproduction steps:
1. Open the attached “MaxPlayerCountBug.zip“ project
2. Enter Play Mode and connect 3 Gamepads
3. Observe the Console
Expected result: A warning is thrown about reaching maximum player count of 2
Actual result: “Have reached maximum player count of 2” error is thrown
Reproducible with: 1.7.0 (2021.3.34f1), 1.8.0-pre.2 (2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1)
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
Note:
Full error:
”Have reached maximum player count of 2
UnityEngine.InputSystem.LowLevel.NativeInputRuntime/<>c__DisplayClass7_0:<set_onUpdate>b__0 (UnityEngineInternal.Input.NativeInputUpdateType,UnityEngineInternal.Input.NativeInputEventBuffer*)
UnityEngineInternal.Input.NativeInputSystem:NotifyUpdate (UnityEngineInternal.Input.NativeInputUpdateType,intptr)”
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
- ComputeBuffer readback fails when Render Graph is enabled
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
Resolution Note (fix version 1.8.0):
Error phrasing and type changed to a warning. Changes should be available in the 1.8.0-pre.3 release