Official Version 1.1 and General Update

Will there ever be a mobile app to "test game" that works with the new input system? Is there anything planned? Or is it just an abandoned way of doing things? Because "Unity Remote 5" only works for old input system..

 

If you read the first post, they consider not being compatible with Remote "pressing". What that means in practice is hard to say.

 

https://github.com/Unity-Technologies/InputSystem/commit/9b58cee86ff42c7999fb451d5d6e2bef5ce7400f

 

So, will this be part of 1.1.2?

 

Also I have a suggestion for Unity:

Suggestion: "Unity Remote 5" has a number "5", if this indicates to the old version "Unity 5", I think it should be removed and renamed to something fancier and more modern; Just a suggestion though.

 

I think improving the docs should be priority.
I find the most useful page is Migrating from the old input system | Input System | 1.0.2 (unity3d.com) just because it nicely lists everything I might be looking to do.

 

I don't know if this already possible somehow, but I figured it's worth asking: would it be possible to run an InputAction's Processors on InputAction.ReadValue even when none of its bindings are actuated? From my testing it looks like it always returns the default value now if you aren't triggering any of the bindings.

My use case is that I want to remap the value from 0 => 1 to 1 => 0, but since it's not actually running my custom RemapProcessor when none of the bindings are pressed, it always returns 0.

 

I upgraded my project to 2021.2f1, is there a way to get this working as there appear to be no option to downgrade from InputSystem 1.1.1 and 1.1.2 might not be out for a while?

 

I was using FixedUpdate in Input settings, changing to DynamicUpdate fixed some of the controls but broke some of the others, guess I'll have to make a workaround until the update comes

 

Another thing that has bothered me for ages: the thumbstick on my Oculus Touch Controller, and I think XR Controllers in general, are mapped as a Vector2Control instead of a StickControl like on normal gamepads, which would allow you to map actions to up / down / left / right more easily without additional code.



EDIT: another minor thing: you can't find an axis attached to another control in the binding path browser if they fall under 'optional controls'. For example the XR Controller has most of its controls under 'optional controls', so I don't see thumbstick/x in the list of available bindings. However if I just enter the path manually (<XRController>{RightHand}/thumbstick/x) it works.

 

this precisely was my experience too. however i'm now using gamecore and this seems to need a bit more knowledge and i'd like to give InputSystem another go as this is natively supported.

the difference i found was that on rewired i could have it fire event when a controller pressed a join button, i could receive this event and know what player this was, and act accordingly in my lobby.

i'm now writing a new lobby from the ground up with UGS in mind, and it would be quite cool to either get my issues addressed, or some example of how things should work which the docs dont provide.

things like the UI input module, i added some events to the UI actions like 'NextPage' and 'PrevPage' bound to shoulder buttons, this is a UI event to switch pages, but the input module does not have these actions, and they don't seem to show up.



it also seems that the player input manager is somewhat fixed on one plan, and if you don't follow that plan then you cant just make a different version as everything is in protected-level code and you cant access the underlying functions.

hopefully all this recent info means i'll get some kind of resolve when i try and re-implement this.