Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice
  3. Dismiss Notice

[SOLVED] D-Pad UI Navigation works everywhere except Xbox GameCore

Discussion in 'Input System' started by BTStone, Feb 3, 2022.

  1. BTStone

    BTStone

    Joined:
    Mar 10, 2012
    Posts:
    1,430
    Hey support,

    using Unity 2019.4.31f1
    using Input System 1.0.2

    I'm working on a console multiplatform game which utilizes the new input system and we're about to go into submission for the consoles and everything works, except the DPad on Xbox with GXDK (GameCore)

    The problem:

    - DPad up and down is not working on Xbox Devkits (Xbox One and Xbox Series) when trying to navigating the UI

    This works though on all other platforms (PS4, PS5, Switch and PC) and the InputActionAsset is setup the same way for all platforms, so I really do not know what's going on here.

    After looking into the docs I checked out the InputDebugger and connected it to the DevKit via the Profiler and the Controller is correctly registered as a GXDK Controller and receives the D-Pad Down and Up events, but I although registering the input the UI navigation does not register the D-Pad up and down, only D-Pad right and left. The analog sticks work fine though for UI Navigation.

    IfI use the same controller for PC, it works without problems...

    This is the Input Action Asset:

    GdkInput.png

    Oh and updating the Input System at this stage is sadly out of the question. I tried that with a backed up version and it completely broke all of the input for all platforms, even InEditor.

    I'd appreciate the help since our publisher wants to submit asap in order to not miss the release date
    @Schubkraft @Rene-Damm
     
  2. BTStone

    BTStone

    Joined:
    Mar 10, 2012
    Posts:
    1,430
    Fixed. It was a bug with the DPAD Vector2 Y Values, was fixed in an updated GameCore InputSystem package.