RegisterReadingCallback not receiving input without focus for GameInputKindGamepad when SetFocusPolicy is set to GameInputEnableBackgroundInput

[OverInfrared]

Registering a reading callback works without focus on keyboard and mouse. But if I set it up for GameInputKindGamepad. You can see controller input coming through if you poll GetCurrentReading on kind gamepad.

To Reproduce

1. SetFocusPolicy to GameInputEnableBackgroundInput
2. Register a reading callback for GameInputKindGamepad
3. Check get current reading to see if your controller input is actually coming through.
4. Witness no callback.

Expected behavior
The gamepad input should come through on the callback just like others (keyboard and mouse)

What I'm running
Microsoft Windows 11 Pro
Version 10.0.26100 Build 26100 old :(
GameInput 2.1.26100.6068

[lsalvadormsft]

@OverInfrared thanks for the report! I believe I was able to reproduce this bug. If a device is connected AFTER the SetFocusPolicy call, then that XInput device does not receive input in the background.

We will track this issue for a future release. In the meantime, are you able to get around your issue by calling SetFocusPolicy after your device callback?

I was not able to reproduce the loss of reading callbacks in the background. Would I be able to ask you what parameters and filters you are using?

[tristam92]

Hi @lsalvadormsft ,
I'm not an original poster, however we do have same issue in our codebase with repro.
I tried your suggested solution and it's no luck unfortunatelly. Controller still returns empty reading, when app isn't in focus. KB and mouse tho work fine.

[OverInfrared]

m_pGameInput->RegisterReadingCallback( nullptr, GameInputKindGamepad, this, &OnReadingCallback, &g_inputToken);

I'm just using a regular GameInputKindGamepad with a sometimes working OnReadingCallback

[OverInfrared]

" I believe I was able to reproduce this bug. If a device is connected AFTER the SetFocusPolicy call, then that XInput device does not receive input in the background."

Interesting I will try if this seems to fix it.

[OverInfrared]

This appears to be fixed in 2.2.26100.6114

[tristam92]

Seems like it's an issue again for 3.1.26100.6879
However in 3.0.26100.6154 it works correctly.

For 3.1 sometimes issue not appears, if you switch order of RegisterDeviceCallback and SetFocusPolicy calls, and then reconnect controller. With next connection it then can be read properly. If app re-launched, you have to reconnect controller again.

[lsalvadormsft]

@tristam92 are you running a windowless app? If so, we added a fix to version 3.3 that might have resolved your particular scenario. Apologies to ask you to validate again, but can I ask you to test if this version fixes it for you?

Thanks!