2019.3.0f5 + Rewired + iOS13.3

Hi,

Has anyone else experienced Unity not returning inputs for joystick button 0 (pause) on controllers on iOS?

On the Nimbus and PS4 controllers, the menu, center button 1 and 2 no longer return any inputs regards of what it’s been mapped to.

Unity 2019.2 worked as expected and triggers pause or other map keys I can assign.

I ran the debugger scene for rewired and axis 18 is being triggered for Options on the PS4 controller and Menu on the Nimbus.

I’m still using the old Input System in the player settings, all the other buttons work on the controller and I tested mapping pause to R2 and that pauses the game, so I can rule out any change of code.

Thanks for any assistance.
Cheers.

This is a new Unity bug.

See this message for discussion links:
https://discussions.unity.com/t/551703 page-119#post-5430417

See these two messages for a workaround:
https://discussions.unity.com/t/551703 page-119#post-5430810
https://discussions.unity.com/t/551703 page-119#post-5438304

1 Like

For all those experiencing problems on iOS and tvOS with Start/Menu buttons, Unity has apparently fixed the underlying issue in various versions of Unity.

It does not appear they have fixed it in the 2019.2 branch. I have no information about whether or not they will do this.

It won’t be backported to 2019.2 since that version is no longer being supported. TECH releases only receive updates until the next TECH release has been released. https://blogs.unity3d.com/2018/04/09/new-plans-for-unity-releases-introducing-the-tech-and-long-term-support-lts-streams/

1 Like

Another update. Looks like they fixed the button bug but broke Left Stick X with the fix. (Or perhaps the left stick was already broken as well before but not fixed? Not sure.)

A customer reported Left Stick X not working anymore on iOS/tvOS 13 2019.3.4f1, which is the version in which the Pause/Menu button fix was made according to the bug tracker.

[A workaround was posted here]( Rewired - Advanced Input for Unity page-119#post-5438304) by @Benzor . I cannot understand why this fix would have anything to do with the left stick X value since these lines of code he commented out are related to buttons. It looks like there’s a button/axis id mixup somewhere deeper in the code