Bug Mouse can't click UI after update to 1.1.1

Hello!

So, recently I've updated Input System 1.0.2 => 1.1.1 and that fixed the issue where actions with hold interaction won't call more than once. Even update haven't affect any of serializes, it caused strange mouse behavior.

First, any mouse interaction with UI still visible but clicks won't call it's onClick events. It's strange at least because all button transition states still visible, even Pressed state while clicking. Also, onClick event calling correctly while using keyboard and gamepad navigation, problem is only present while mouse clicking. I've checked is UI click action set correctly and serialized into Input System UI Input Module, everything seems fine so I have no idea what can cause problem. Also, mouse clicks for ingame actions works correctly.

Second, mouse look won't work untill I press any of key that moves character (some other actions like attack won't make camera look work). That also affecting camera look on gamepad's stick. I'm using Cinemachine Free Look with Cinemachine Input Provider. Before update to 1.1.1, camera look worked instantly after entering Playmode.

 

For your second issue, do you have Cinemachine set to Smart Update mode? Try setting it to Late Update instead and see if that makes a difference. Please report back.

 

Thank you! Adding CinemachineBrain and setting it's update mode to LateUpdate fixed the issue.

About the first issue, it's still an actual problem.

 

No problem. There's definitely a serious issue with Input System 1.1.1 and FixedUpdate polling of input devices. I've reported several issues and even brought it up on the release thread, but I've yet to see anyone from Unity acknowledge it yet. I'm really surprised it's not causing almost everyone serious problems...

 

So I've resolved my first problem just by changing mouse click action type from "Button" to "Pass Through" => "Button" and checked "Initial State Check".

 

It didn't solve a problem.
Does anyone have a solution. I mean.. come on Unity guys - that is a critical-problem situation.

EDIT: So I switched to default action asset in UI input model and it works (yay), but I am still confused, as my custom action asset worked flawlessly with a previous Input System.