Gamepads not detected when OpenXR is enabled

We have a similar problem. As soon as the MetaXR or OpenXR plugin is enabled, game pad stops working.

Did some debugging and saw that the event is received in the android main event loop but not being propagated to the game event loop since it is being processed in event predispatching. 

Our workaround for the problem is to skip preDispatchEvent for game pad A button events.

 And in a plugin call AddOculusGamePadSupport

#include <android_native_app_glue.h>
extern struct android_app* GNativeAndroidApp;
​
static void process_input( struct android_app* app, struct android_poll_source* source) {
    AInputEvent* event = NULL;
    while (AInputQueue_getEvent(app->inputQueue, &event) >= 0) {
        bool skip_predispatch
              =  AInputEvent_getType(event)  == AINPUT_EVENT_TYPE_KEY
              && AKeyEvent_getKeyCode(event) == AKEYCODE_BUTTON_A;
​
        if (!skip_predispatch && AInputQueue_preDispatchEvent(app->inputQueue, event)) {
            continue;
        }
​
        int32_t handled = 0;
        if (app->onInputEvent != NULL) handled = app->onInputEvent(app, event);
        AInputQueue_finishEvent(app->inputQueue, event, handled);
    }
}
​
static void AddOculusGamePadSupport() {
    GNativeAndroidApp->inputPollSource.process = &process_input;
}

 PS! The code will only work for button a events.

Thank you for that code! Finally some lights 🙂

If I want to support all buttons/axis, I've to make a big condition for skip_redispatch right?

https://github.com/Oculus-VR/UnrealEngine/issues/318 More information. You need to have a registered github account and access to the unreal source code to read the issue

Awesome!

Please post the link to the issue here so that we can follow the status of it.

OpenXR Plugin is constantly checking if the HMD is enabled. If in the app we execute the console command "bEnableHMD 0" the gamepad input starts to work (of course the screen goes black) and if we return to "bEnableHMD 1" the input is blocked again, but the OpenXR starts recognizing the gamepad partially, the nodes "Get Gamepad Controller Name" now correctly returns the model of the gamepad and the node "Is Controller Assigned to Gamepad" now returns "true", although the app stops receiving inputs, the vibration (FFB) continues to work normally (Which is a workaround for one of the problems).

oh.. I didn't know that it seems like MetaXRPlugin broke gamepad event... that's something new.
let me spread the word to the team to see what they think.
thanks!

"We’ve the same issue with de default OpenXR plugin without MetaXR"? oh.. that's interesting. 🙂 

Not sure which Epic engineer you talked to? I could talk to him/her directly as well.

Hello,

I just talked to a technical account manager of this issue and he told me that I'll talk about that to the team behind that. In the mean time, I've opened an issue "Case # 00706549: Gamepad are not detected on Android when VR is enabled".

I can confirm that if VR is disabled, gamepad input are working well. I've an hybrid game (flat/VR) that works with gamepad inputs on Android, but only works with controllers input on Meta Quest 3. I started to look at the code, and it' seems it's not blocked in the Java activity, but more deeply in the code, not sure where.

cool, I will sync w/ Epic on this next week.

thanks

fyi: I just synced w/ Epic side engineers quickly, and they tried gamepad in editor w/ latest main branch (Epic's main branch), it seemed work.

Any of you tried editor's vrpreview? or only mobile side? Also, VRTemplate has gamepad setup as well, did any of you try that to see if it works? We use VRTemplate as a very important test for our release. 

I need to work w/ our QA to repro this issue then, but the more information I could collect here, the easier from our side, 🙂 thanks!