Xbox One - Second controller(gamepad) not recognized

Development Programming & Scripting Multiplayer & Networking
, , , , , ,
1

Hello,

we are having an A-bug in our game on XboxOne, which we are unable to solve on our own and no-one in the Forums seems to be able to help either.
Hopefully someone from the Support team can help us, because the bug blocks our upcoming release.

We are quite certain the bug has something to do with the engine and not with our game in particular.
Here is the bug report:

Our game is a local multiplayer game for two to four players with no XboxOne live features. When launching the game only the first gamepad can give inputs to the engine.
Steps to reproduce:

  1. Connect two ore more gamepads to the XboxOne
  2. Launch the game with the first connected gamepad
  3. After the game has loaded and the first scene has been loaded, only the first gamepad works properly
  • The engine recognized the Num of gamepads connected (e.g. in the StableGamepads[] array), but the engine receives no inputs from them
  • Suspending the game/ refreshing gamepads etc. does not fix the issue

The bug does not occur and all gamepads work as intended when:

  • Pressing any button during the loading of the game on any of the other gamepads (which are not the first connected gamepad)
  • (Unreliably reproducible) Launching the game with any other controller than the first connected

What can we do to fix this? We desperately need a quick-fix, because we cannot submit the game to certification as it is right now (even a workaround would be greatly appreciated).

Cheers,
Tobias

2

Bump, we could really need help here.

3

Hi priareos,

We have had other users complain about similar issues. A bug has been logged here: Unreal Engine Issues and Bug Tracker (UE-41094)

You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.

Cheers,

4

Hi Ed,

Thank you for your answer! However, this seems to be similar, but is for PC only, right?
I think our issue is related to how the XboxOneInputInterface initializes gamepads, which is not the same as the XInputInterface.

5

The issue was reproduced on the XBoxOne however, this issue was reported with steps to reproduce in editor for ease of testing. A private comment was added regarding the use of XBoxOne.

If you still experience issues after a fix is released then we will investigate further. Keep in mind that a fix may not be issued quickly so I would recommend using another engine version that works (if at all possible).

6

Hi! This is still blocking any Xbox One release. I saw the issue was to be fixed in 4.16, but now it’s back to “unresolved” again. Could you please share any updates on this?

7

The reason you saw this is because we had issued a fix but then later realized that the fix was flawed and not ready for integration. This is currently being worked on and the fix date isn’t set. I can express the community interest for the devs since this is an important issue. Would you mind posting links to any forum posts or Anwer Hub posts with concerns for this?