Official Version 1.1 and General Update

Hey everyone,

Quick update on the state of affairs around input.

New Release

Version 1.1 verified of the Input System package is now live.

It includes a year of bugfixes and improvements. Some highlights:

• Easier button polling

Code (CSharp):

1. action.IsPressed()
2. action.WasPressedThisFrame()
3. action.WasReleasedThisFrame()

• Easier “any key” detection

Code (CSharp):

1. InputSystem.onAnyButtonPress
2.     .CallOnce(button => Debug.Log($"Button {button} pressed"));

• Saving and loading rebinds as JSON

Code (CSharp):

1. void SaveUserRebinds(PlayerInput player)
2. {
3.     var rebinds = player.actions.SaveBindingOverridesAsJson();
4.     PlayerPrefs.SetString("rebinds", rebinds);
5. }
6.  
7. void LoadUserRebinds(PlayerInput player)
8. {
9.     var rebinds = PlayerPrefs.GetString("rebinds");
10.     player.actions.LoadBindingOverridesFromJson(rebinds);
11. }

For a full list of changes, please see the CHANGELOG.

New Team

In the past, we had a number of resourcing problems. Over the past couple of months, a new team has formed.

• Håkan - Lead
  
  
• Gabe - Project Management
  
  
• Stefan - QA
  
  
• William - UX
  
  
• Dmytro - Developer
  
  
• Andrew - Developer
  
  
• Rene - Developer
  

New Future

While we will continue to work on stability and performance improvements, we consider usability and workflow improvements our one top priority going forward. While the current package offers many tools and pieces, we have a general lack of clarity and simplicity in how to put these tools and pieces to use.

Other than this, we do have a small number of oft-repeated feature requests (like the “SHIFT+B” and “B” binding problem) and incompatibilities (Unity Remote) that we consider pressing.

Instead of embarking on a long preview cycle, as we did with 1.1, we intend to instead roll out more frequent patch releases containing fixes. These updates will automatically be applied by the Unity package manager to the current 1.1 release.

 

Nice! However the package manager still shows me 1.0.2 as the latest version. When could we expect 1.1 hitting the package manager? I even see "[1.1.1] - 2021-09-03" in the change log already, yet no 1.1 in the package manager?

 

Thanks. I had to manually add by name "com.unity.inputsystem" for 1.1.1 to be visible.

 

It already pops up for me in 2021.2b10 for update as 'Release' version.

 

Is the pen pressure / tilt now available in the editor for editor tools?
Or is it play-mode only.

Thanks for the hard work!

 

There was improved pen support for IMGUI events being worked on some time ago from the editor side but looking into it, seems that hasn't yet made it out the pipes. It being part of

UnityEngine.Event

IMO is the "proper"/better way in this case than the input system serving the data.

As far as the input system is concerned, the edit mode support landscape is so far unchanged. The focus changes affected it tangentially (non-pointer/keyboard devices are now always routed to the game view by default) but for pens, shouldn't have much of an impact. There is still an open bug in that area and overall, edit mode support stands on somewhat shaky legs.

 

Thanks for the status update, I hope this will be all smooth sailing towards unity 2022

 

Using 2020LTS, not seeing 1.1.1 in the package manager either.

What is this "manifest" I need to edit? And what exactly should I add? Hopefully this will update itself soon?

 

Ah ok, it's straight up hardcoding the version in the manifest.json in the project. Upon reloading, Unity auto-installed it. I was a bit worried about doing that change but I guess it worked

 

Good luck to the new team.

 

The Gamepad Mouse Cursor Sample does not work at all when using version 1.1.1.
Also, version 1.0.2 is unusable for me because of "VirtualMouseInput not supporting UI scaling other than constant."

Did somebody manage to use VirtualMouseInput on 1.1.1 or does have a fix for the related problem on 1.0.2?

 

In the current iteration there is the possibility to directly access the state for a subset of inputs:

Code (CSharp):

1. Gamepad.current
2. Mouse.current

Is there anything similar planned (or maybe already implemented) for VR controllers and headsets (like the state access without callbacks)?

 

Is it intentional that calls on an Input Action to

ReadValue<T>()

do not work (i.e. always return zero) when called from

FixedUpdate()

in 1.1.0-pre.6 and 1.1.1, when Update Mode is set to "Process Events in Dynamic Update"?

It used to work in earlier versions, so if it's a regression, let me know and I'll file a report...

EDIT: I can't find any documentation of this change so I've filed a bug report anyway, in case it's a genuine regression. It's 100% reproducible for me, across multiple projects and Unity versions.

 

Latest version of the InputSystem 1.1.1 the stickAction of the VirtualMouseInput always returns 0,0 delta.

Debugging looks like the OnAfterInputUpdate is only called once after moving the joystick and so the deltaTime value is always 0

Creating a copy of the class in the project (i.e. in a custom namespace) and using that class fixes the problem - looks like there's a bug with the event callbacks.

 

I copied the class but it still did not worked. deltaTime is always 0, but for me it's because every other frame the stick value is always 0 for some reason.
I added some debug logs with frame counter to test it and here is the result.



First time stick value is non zero, so the m_lastTime is saved and because on the first run it is equal to currentTime then deltaTime is 0. On the second run it should enter the else and calculate non zero deltaTime. However, because the stick value is zero, the m_lastTime is reset and nothing happens.

 

I gave up on the new Input System, after an hour of trying to solve the problems, I gave up.

I bought ReWired, after 30 minutes to learn how to use it, everything I needed was working perfectly. Best investment I ever made.

 

I found the issue is the input system is managing states with 'Editor' in the mix causing the values to be unset...


Debugging looks like the OnAfterInputUpdate is called from the 'Dynamic' / 'Fixed' state update but then also called by a 'Editor' state update.
In the 'Editor' state update the value is 0,0 - which causes the VirtualMouse to reset.

With Dynamic it looks like they are 1:1 Dynamic update to Editor update so the virtual mouse never moves.

Would be good if Unity provided a better callback that included the state so we can 'ignore' the editor update callback. Or at the very least allow us to query the current InputSystem state so we can ignore if it's in 'Editor'.

Because it's been made internal the only way to fix this is to copy the package internally and fix the internal scope limitation.

Also as a note 'defaultUpdateType' doesn't make a lot of sense for a member name that returns the 'currentUpdateType'??


Below code fixes the issue (but you have to patch the package, meaning adding it manually to your packages folder):

Code (CSharp):

1. private void UpdateMotion()
2.         {
3.             if (m_VirtualMouse == null)
4.                 return;
5.             #if UNITY_EDITOR
6.  
7. if(UnityEngine.InputSystem.InputSystem.s_Manager.defaultUpdateType ==
8. InputUpdateType.Editor
9.                 ||
10. UnityEngine.InputSystem.InputSystem.s_Manager.defaultUpdateType ==
11. InputUpdateType.None)
12.                 return;
13.             #endif

 

@RodGreen, could this be the reason why sometimes the Cinemachine Orbit camera doesn't respond to X-axis mouse delta inputs when using the Input System Input Provider with 1.1.1? The delta values read by ReadValue are almost always zero, although sometimes glitch to non-zero values, but then "stick" at zero again. I've noticed that alt-tabbing away/back to the Editor makes it work, sometimes, for a few seconds perhaps, but it's highly intermittent and I'm having a lot of trouble figuring out what causes it to come and go.

It was working fine in 1.1.0-pre.5 and earlier.

EDIT: nope, I tried your change to

UpdateMotion

and it didn't resolve my issue (assuming it got recompiled?). Must be something else then...

EDIT2: reverted back to 1.1.0-pre.5 and it's all working again - definitely something wrong with 1.1.1. Note my previous post about ReadValue in FixedUpdate being broken too - perhaps related, not sure yet...

EDIT3: I've determined that my Cinemachine problem is the same problem I mentioned earlier in this thread where ReadValue in FixedUpdate returns zero values. I was seeing intermittent failure in Cinemachine because the Brain was set to Update Mode "Smart Update" which flicks between Late Update (when it works) and Fixed Update (when it doesn't) at its own discretion. If I change the Brain to Late Update then it works fine, and if I change it to FIxed Update then it is 100% broken.

At this point I'm kind of surprised that nobody else has reported this FixedUpdate issue yet...

 

Before in the Input Debugger there was the option: Lock Input to the Game Window

In the current release I can't find that option anymore, is this option now somewhere else?

It allowed having the input to be captured even if the game view wasn't focused. The new settings in the Input System Package (Editor -> Play Mode Input Behaviour -> All Devices Input Always Goes To Game View) seems not to work for me.

 

You have to copy the package to your local packages folder to make the change, Unity detects the change if you make it in the Library folder and reverts it.

Bug report 1367553.
Dynamic Update doesn't work - fixed update is slightly broken as there's a random 0,0 - inserted into the mix every few callbacks.
The way to test is to create a VirtualMouseInput component, and see the value is always 0,0 - you can check this with basic debugging or implement a control mapping, that uses it and poll the value.

 

@dmytro_at_unity In case it's helpful, I included a repro project in bug report 1367556 that might help you track this down. It's not specifically related to VirtualMouseInput but from what I'm reading here there are definitely some similarities around zero values being read in Fixed Update. My case is more general I think.

 

VirtualMouseInput only supports Overlay... If you use a camera it does not work. Is this expected to be fixed in the near future?

 

I looked up "com.unity.inputsystem", but it does not show up in the package manager.
Unity is
2021.1.21f1
2020.3.15f2

Do I need to install it from somewhere else?
Also, am I displaying it incorrectly?

 

You can do it this way:
https://forum.unity.com/threads/cannot-upgrade-to-beta-versions.1143701/#post-7343153
Obviously, use the proper version string.

 

Thank you for helping!
I'll try that right away!

 

FWIW, you can also install it via the "Install package by git url" option and type "com.unity.inputsystem@1.1.1". This works for any of the tagged versions, just change the version string after the @.

It should probably be listed here too, as promised here, but maybe I expect too much.

 

WasPressedOnThisFrame is great....however, I have a Vector2 WASD input setup. So if you press A, hold it while you press D, it will register as 'released'. Not really breaking my code but just gotta put this out there

 

When will the Dualsense (PS5 Controller) support come? It's been a year since the console came out and the support didn't land yet.

And it's completely mapped wrong when connected via cable -Wired- on Windows PC, however, it works fine if connected via Bluetooth -Wireless-, and also mapped wrong on Android 11 -Samsung Galaxy S20+ 5G- Wired and Wireless.

 

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

 

Ok, yeah, there are git hub packages and all that stuff, however, they got issues, even the most advanced one among them -Unisense- still has critical issues and not all features are supported; Besides, we want it to be from Unity Team End themselves which will have it integrated and built-in to the Input System directly into the Unity Editor itself.

 

Just incase this thread gets looked at for feedback, please also add high definition mouse input, this is important for any modern first or third person shooter to match the responsiveness of other games and engines.

https://docs.microsoft.com/en-us/wi...s/taking-advantage-of-high-dpi-mouse-movement

Some discussion:
https://forum.unity.com/threads/new...1-4WkVn14FhRIHX-6DsHp2w9bV7eJ_eI#post-7553461

 

This. Players complain about it and all we can do is tell them it's Unity's fault.

 

https://assetstore.unity.com/packages/tools/input-management/incontrol-14695

Incontrol has ps5 controller support if you really need it today

 

Migrating the entre game to a different input system is not an option in our case.

 

That's cool, thank you! But, is touchpad movement support (like in PS5 Astro's Playroom game where you roll the ball with touchpad) implemented yet? if not, when?

 

How would I do this for any other virtual devices? I want to create my own virtual mouse and control it with my own code but cannot because of this bug, however s_Manager is only accessible internally, and the settings have an update mode but I cannot tell if that is related.

 

I'm also experiencing this, need to downgrade for now I think. Wish I could participate in the Beta, these are really helpful additions!

 

Could we, pretty please with cherry on top, get the combination?

Code (csharp):

1. InputSystem.AnyButtonIsPressed();
2. InputSystem.AnyButtonWasPressedThisFrame();
3. InputSystem.AnyButtonWasReleasedThisFrame();

Systems that do "please press any button" are generally outside of the normal flow of the game (menu, demo booth version, special cutscenes), and having a system hooked up can be a bit of a drag. It's very convenient to just stick a behaviour in there that checks if

Input.anyKeyDown

, so the new input system having that in addition to the callback would make things easier.

 

I was using version 1.0.2 and updated to version 1.1.1 today to get access to Save and Load BindingsOverrideAsJson method that was added in Experiemental Preview 3...

However since the update, my move(vector2) isnt working anymore...
If I press any keys, it always returns 0.0... if i dont touch the keyboard, it returns null

(sprint, look, etc. all still works.. only the vector2 stopped working)

I tried adding an "if" condition (see below in the screenshot), but now it only returns 0.0 no matter if i press any of the "Move" Keys or not...

Any help or tips would be greatly appreciated!

 

Here is my actions input assets as requested
hummm... unity doesnt allow for this type of file to be uploaded... (added to zip)
I put both the MyActions.inputactions as well as InputSystem.inputsettings.asset since im unsure which is needed
Let me know if i can assist with anything else or if you figure out what is wrong!
(Especially since it was working absolutely fine before the 1.1.1 update)

EDIT : I also tried making a new MOVE2 action set, mapping it to UHJK and trying it... but it had the same issue that all vector2 returned 0.0

Thanks a lot for your time!

 

hahah YES my readvalue was indeed in the fixed update...

I changed it to update... and its now working again.... wow... thanks for figuring that out!!!