Official Input System 1.5.0 released

https://github.com/Unity-Technologies/InputSystem/pull/1578

When can this be merged? Been open for a while now

 

Just wanted to say I appreciate you all keeping the package public on Github! It's really nice to be able to see all the work you're doing.

The Input System is a fantastic system, glad to see the updates!

 

Are there plans to add support for haptics for Xbox, PS4, and Switch Pro controllers on macOS? I can see that macOS supports them natively - connecting them to my Mac and then pressing "Identify" will make them vibrate - so system support shouldn't be an issue.

 

Is the problem with multi screen UI going to be fixed?

https://forum.unity.com/threads/new...t-work-updated-with-dual-screen-game.1395433/
https://forum.unity.com/threads/can...second-display-with-new-input-system.1330467/
https://forum.unity.com/threads/managing-multiple-touchscreens-setup.842233/#post-8794906
https://forum.unity.com/threads/coo...y-connecting-multiple-touch-monitors.1396216/

 

This update broke the MultiplayerEventSystem for me. As in, the class itself doesn't compile (can't be added as a component) and any prefabs that had the component are borked. Any ideas? (This came from updating the proj to 2022.2.6 - manually downgrading the input package to 1.4.4 fixes it)

 

For my VR project the opt in optimizations make it slower in editor. Haven't tested in build

 

Performed a lot worse for me in VR (input took up to 5x with optimizations compared to without with standalone VR).
Bug report made: IN-33567

 

Great, thanks for the reply/info!

 

@Schubkraft Is this going to be fixed soon, sir? https://forum.unity.com/threads/new-input-system-processors-not-appearing-always.911015/

 

Also provided more info on performance improvements

 

O well. I was looking for a solution where I have an action that uses gamepads and I need A on the Switch pro controller to trigger BUT I need South on all other gamepads to trigger but not on the switch pro controller. I don't want to duplicate all actions just for the switch.

I was hoping to use that to stop this issue. Is there not an official solution?

 

Looks good, but why do the changes have to be enabled by some strange string-based feature flags system which literally nothing else in Unity uses, and requires you to write a script that gets executed every time your game runs? Why not have a scriptable object based configuration file with tickboxes, or some options in project settings to keep it consistent with every other system in Unity? Making things like this obscure hurts discoverability and unless someone sees this thread specifically they're probably never going to discover it. It seems like almost every new Unity feature or package uses a completely different approach to configuring itself. (Eg HDRP, URP, Input System) Why not unify all settings to use a common approach?

Personally I don't understand why you wouldn't just want these optimisations/caching enabled all the time. What advantages are there to leaving them disabled?

 

Right now vr performance suffers with the optimizations, and maybe some other platforms.
I do agree why it can't just be a checkbox in a scriptable object or just in the input system settings in project settings

 

Updated to 1.5.0 by updating Unity from 2022.2.2f1 to 2022.2.8f1. Can no longer view .inputactions files along with the following errors:

Code (CSharp):

1. InvalidOperationException: Failed to add object of type `InputActionReference`. Check that the definition is in a file of the same name and that it compiles properly.
2. UnityEngine.InputSystem.Editor.InputActionImporter.OnImportAsset (UnityEditor.AssetImporters.AssetImportContext ctx) (at ./Library/PackageCache/com.unity.inputsystem@1.5.0/InputSystem/Editor/AssetImporter/InputActionImporter.cs:130)
3.  
4. Asset import failed, "Assets/InputMaster.inputactions" > InvalidOperationException: Failed to add object of type `InputActionReference`. Check that the definition is in a file of the same name and that it compiles properly.
5.  

This applies to all existing .inputactions files and any new ones I create. Downgrading to 1.4.4 fixes it for now.

 

Hi ! Did you have the opportunity to see this bug ?

https://forum.unity.com/threads/stack-overflow-on-build-due-to-input-system-1-5-0.1404538/

I can't launch my game anymore on my PC because of this bug in the input system 1.5.0. I can't even make a bug report because it's only happening on build and only on my computer (tested on 10+ other computers).

 

Hi @Schubkraft. Any plan to start working on making all Input System APIs burst and job compatible very soon specifically for mobile platform i.e Android and iOS to better support dots project? Currently at android platform I get 2ms+ just for input which is insanely slow caused by input can't schedule as job. I hope the APIs can support both burst and job but if can't yet at least make it able to schedule as job.

 

So please, have in mind the workaround that I've found: using both old and new input system in one game.
https://forum.unity.com/threads/new...d-with-dual-screen-game.1395433/#post-8825950

 

Just want to make sure I'm getting this right.
Games built with the new input system will not have haptics on ARM/Silcon based Macs?
And that this shortcoming is not really on your to-do list?

 

Please help!!!
I have had my On-screen stick working without any problems until now. However, in the last few days, the stick that complements the On-screen stick suddenly stopped working, and when I disable InputSystem in Inspector, it works fine.
Then I upgraded to 2022.2.6f1 and set InputSystem to 1.50. However, I still have the same problem.
How can I improve it? I would like to know.

 

@Schubkraft Hi,I have a basic problem.
Suppose the shortcut key of function A is Alt+K, and the shortcut key of function B is K. When I press Alt+K, both functions A and B are triggered. How can I avoid this situation?

 

Can someone in Unity team answer to this please ? https://forum.unity.com/threads/inv...-add-object-of-type-inputactionasset.1416816/

I can make a repro case or a bug report because it only happens on my computer, even on empty new projects. It seems very similar to this post https://forum.unity.com/threads/input-system-1-5-0-released.1397758/#post-8843890 but in my case, 1.5.0 doesn't have the problem, it's only in 1.5.1.

 

You need to enable this guy in Project Settings -> Input System Package



It's not on by default. When enabled, the most complex action will win.

 

Is it true that there is another revamp of the new Input System happening behind the scenes for over a year now? If it is true, is there any info on that, or has it already been merged into 1.5, or is it just a baseless rumor?

 

Doesn't work.

New Input system + UI + Split Screen.

UI navigation doesn't work when the second player joins.

Unity Version: 2022.3.0f1 LTS.

 

Bug report form - where is it, how to report it? I don't have time for this. I don't have time for this.

I report here and you should handle it.

When the second player joins in the split screen mode, he is not able to navigate in UI with the d-pad.

I tested in on multiple unity versions, multiple PC with different xbox gamepads.

Multiplayer event system -> first selected is selected to the first button, the the root to player canvas.

It only works for single user.

 

Multiplayer event system - UI navigation doesn't work with Xbox gamepad. I tested it on multiple Unity version, on different PCs, with different Xbox gamepad. Issue always the same.

Only when I set to explicit it works, but it is the floppy design. I populate the list with buttons dynamically and there a multiple of them. IT SHOULD WORK AUTOMATICLY JUST LIKE WITH THE KEYBOARD.