Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Standalone Input Module + Xbox ONE controller not working in the build (working in the editor)

Discussion in 'Windows' started by HandMadeGame, Aug 10, 2016.

  1. HandMadeGame

    HandMadeGame

    Joined:
    Oct 27, 2010
    Posts:
    11
    Hello there,

    I'm getting this issue since a while ago - not sure what happened. I'm using Event System + Standalone Input Module to navigate in uGUI menu using Xbox ONE controller.
    The controller works fine in the editor, but not in the build. The only part that is not working is the navigation with Standalone Input Module - XInput related scripts works fine.

    If I run the build, turn off the controller, and turn on again, it works. I've searched the log, and it shows the message below when it works.
    Joystick connected ("Controller (Xbox One For Windows)").
    Somehow it seems like Unity's not initializing the connected controller at startup?

    I've been using Unity 5.3.5f1, and I tried in 5.4.0f3 without luck.

    Thanks!

    -Jake
     
  2. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,875
    Any chance you're using Windows 10 Redstone build?
     
  3. HandMadeGame

    HandMadeGame

    Joined:
    Oct 27, 2010
    Posts:
    11
    Hmm...? I can't check it now, but Windows 10 just updated itself a lot. Could that be the issue?
     
    Last edited: Aug 10, 2016
  4. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,875
  5. HandMadeGame

    HandMadeGame

    Joined:
    Oct 27, 2010
    Posts:
    11
    Thanks. It seems like the issue. Which number do you mean to type? Is it for reverting windows version?
    I tried ver 10.0.10586 (version number), but it doesn't work.
     
  6. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,875
    10.0.10586 should work...If it would be 10.0.14393 then you might have that bug.