What is the status of InputSystem 1.4.0?

[kyubuns]

I encountered the bug in InputSystem 1.3.0, searched and found the fix in 1.4.0.
I was going to update to 1.4.0, but I still can’t select it, although on CHANGELOG.md it says it was released on 2022-04-10.
What is the status of InputSystem 1.4.0?

[ilikeshiny]

It’s currently listed as “Pre-release” on Github: Release 1.4.0 · Unity-Technologies/InputSystem · GitHub

You can try using it for yourself by downloading the “Source code (zip)” from that github link, extracting it, then in Unity going to: Package Manager → Plus Button → Add Package From Disk → /InputSystem-1.4.0/Packages/com.unity.inputsystem/package.json

Fwiw: The 1.4.0 update does not work properly in my project. It throws a bunch of “Type of instance in array does not match expected type” errors, IndexOutOfRange exceptions when trying to resolve bindings, and completely broke controls in my game other than for UI navigation. Hopefully they fix it before it’s officially “Released”.

[kyubuns]

Thank you!
I will try Pre-release.

[rubendariohh]

@kyubuns

Thank you!
I will try Pre-release.

Hi!. Did you have issues with the 1.4 pre release too?

[Jasozz]

@rubendariohh

Hi!. Did you have issues with the 1.4 pre release too?

I did - I tried out 1.4.0 and 1.4.1, as I -really- need Mouse Wheel Up/Down to be rebindable separately, and neither worked properly for me. They seemed to completely break certain inputs for me, like WASD would only register maybe 1 in 10 presses. Reverted back to 1.3.0 and it works just fine.

[ChichoRD]

It seems like it is not being released yet due to some major code changes that differ from the 1.3.0 as it is my personal case of use:
I was looking for the changelog in which the posibility of making radial fills with button prompts is possible. That is as here is said in 1.4.0. Hence I downloaded it since I cannot use the package manager with that version yet.
However adding said functionality to my project via upgrading removed another key action in my game (being able to register double Vector2 presses to perform a dash).

I hope an official stable release comes soon.
Otherwise I was wondering if it is possible to combine different scripts of the input system from differerent versions, in my case the whole input system 1.4.0 with whatever handled the multitap interaction in 1.3.0.

[Bearsauce]

@ilikeshiny

Fwiw: The 1.4.0 update does not work properly in my project. It throws a bunch of “Type of instance in array does not match expected type” errors, IndexOutOfRange exceptions when trying to resolve bindings, and completely broke controls in my game other than for UI navigation. Hopefully they fix it before it’s officially “Released”.

I updated to 1.4.1 and I am now also constantly getting “Type of instance in array does not match expected type” (PlayerInput.cs:1735) errors on scene changes. Did you come up with any solution other than rollback?

[ilikeshiny]

@Bearsauce

I updated to 1.4.1 and I am now also constantly getting “Type of instance in array does not match expected type” (PlayerInput.cs:1735) errors on scene changes. Did you come up with any solution other than rollback?

Nope, I rolled back to 1.3.0 and am just waiting for the official 1.4.x release.

[dmytro_at_unity]

https://packages.unity.com/com.unity.inputsystem says 1.4.1 is publicly available, so you should be able to put 1.4.1 into manifest.json in your projects. We’re working on promoting it to released Unity versions.

[MarsCitizen_1]

1.4.1 Still suffers from a major issue that prevents it as a viable option for local multiplayer projects:

(These links below all discuss the same pool of issues)
Vote on this bug!

Unity IssueTracker - Colors of buttons change when using multiple Multiplayer...

Discussions:

Input System 1.3.0 released: more fixes

The 1.3.0 update introduced several funky things when doing split screen local multiplayer. Selectables coloring settings goes right in the trash. Disabled vs Normal is not obeyed correctly. Almost everything starts showing up as disabled by default. Happens once you have more than 1 PlayerInput w/ their own canvases. An issue I'll describe in better detail another time. Again, multiple players, multiple canvases: when new Selectables are instantiated on Player X's canvas, Player Y loses curr…

[Case 1402627] MultiplayerEventSystem breaks interaction and button visuals

Hey, so using Input system 1.3.0, Unity 2021.2.7 The MultiplayerEventSystem is breaking interaction and visual state of buttons contained underneath “playerRoot” objects. Here’s a video showing the issue: [multiplayer input] Basically, when 2+ players are joined. Only the last player is able to navigate and interact with buttons under its associated playerRoot. The first player is unable to interact at all. Also, the visual state of all buttons seems to be in a constant change b…

[Case 1400904] Second multiplayer event system breaks Transition Color Tint

The second multiplayer event system makes the buttons darker. And another effect - the buttons flash when the windows folder is on top of the game. When I manually turn off second multiplayer event system - the colors are restored. When I change button transition from Color Tint to none - shading disappears. It looks like all colors are applied at once (Normal, Highlighted, Pressed, Selected, Disabled) Windows 10 21H2 Unity 2020.3.27f1 Input System 1.3.0 Universal RP 10.8.1[7869394--999…

tldr;

• Button visual states flash/flicker frequently.

• Selectable elements seem to simultaneously have “Disabled” and “Normal” interaction states active. Color schemes are not obeyed, Dropdowns look silly with a disabled BG color on every item.

• Players can lose selected UI GameObject when other players’ canvas objects update.

[Zephni]

After reverting back to 1.3.0 which fixes the issues some have mentioned above, it now gives me a different error when using:

InputSystem.onAnyButtonPress.Call(ctrl => {/* Do something with button press */});

Is this just yet another bug with the input system? I also tried v1.4.1 but that has the same issues as 1.4.2 as far as I can see.

[emredesu]

@Zephni

After reverting back to 1.3.0 which fixes the issues some have mentioned above, it now gives me a different error when using:

InputSystem.onAnyButtonPress.Call(ctrl => {/* Do something with button press */});

Is this just yet another bug with the input system? I also tried v1.4.1 but that has the same issues as 1.4.2 as far as I can see.

Yep, this bug was confirmed by Unity and was fixed with 1.4.1. I’m having the same issue with the onAnyButtonPress event (also on 1.3.0), seems like we don’t have much of an option other than waiting until Unity fixes the issues within the current version.

[nehvaleem]

Answering the question in the thread title: broken.

[avataris-io]

@dmytro_at_unity

https://packages.unity.com/com.unity.inputsystem says 1.4.1 is publicly available, so you should be able to put 1.4.1 into manifest.json in your projects. We’re working on promoting it to released Unity versions.

Hey!
When do you plan to resolve errors regarding resolving bindings? It would be great to have it fixed because it makes a lot of problems.
We experienced a lot of issues with the new Input system 1.4.x, so we will switch back to 1.3.0. It’s also buggy, but at least it’s more stable and you don’t need to restart unity after each going to play mode, because InputSystem stops working.