Search Unity

New Input system and tvOS

Discussion in 'iOS and tvOS' started by JakeSimpson, Jan 22, 2020.

  1. JakeSimpson

    JakeSimpson

    Joined:
    Dec 4, 2019
    Posts:
    20
    Using Unity 2019.2.10f

    So we've gotten some input systems to work on tvOS in terms of attached controllers.

    The Xbox one controller and the nimbus connect to the tvOS device and the inputs, as defined by the input system, work fine on the latest tvOS (version 13.3). However, the PS4 controller does not work.

    The PS4, when bluetooth connected to a MacBook Pro, shows up inputs and works fine within the Unity Editor, but when the same PS4 Controller is attached to tvOS, and Unity is running on that device, no inputs work at all. We know the PS4 controller does with tvOS, since we can connect it, and it allows us to navigate the tvOS system just fine; it's just Unity that doesn't pass through the inputs.

    How do we get around this? Is there a work around? Is this fixed in a later version of Unity?

    Advice, please.
     
  2. rsofia

    rsofia

    Joined:
    Mar 24, 2016
    Posts:
    2
    I'm having the same problem. Did you find a solution?
     
  3. JakeSimpson

    JakeSimpson

    Joined:
    Dec 4, 2019
    Posts:
    20
    Yes. We bought the Rewired plugin and used that instead, because this hasn't been fixed in the latest release, which means Unity doesn't have that much interest in fixing this anytime soon.
     
  4. sas-dj

    sas-dj

    Joined:
    Sep 29, 2016
    Posts:
    4
    hi

    when you say the nimbus controller works on tvOS 13 , what profile did you use in the new input system

    thanks
     
  5. JakeSimpson

    JakeSimpson

    Joined:
    Dec 4, 2019
    Posts:
    20
    We gave up in the end, and reverted to using Rewired.

    However, there's no profile preset for nimbus on the input system.

    We used the generic gamepad profile - the Dpad and other controls map pretty much 1:1 to the Nimbus. It's the PS4 that doesn't map at all.
     
  6. EmberLuis

    EmberLuis

    Joined:
    May 22, 2019
    Posts:
    11
  7. BujuArena

    BujuArena

    Joined:
    Dec 6, 2014
    Posts:
    5
    This is fixed in the new release today of InputSystem 1.1.1. You can manually set the package version to 1.1.1 in your manifest.json. I couldn't figure out any other way to upgrade to it in the package manager, but setting it manually in the manifest.json file worked.