Hey,
The Input Team would like to announce that Input System 1.14.1 has been released.
The version will be available through the package manager in the upcoming versions of 2022.3, 6.0, 6.1 and 6.2 Editors.
Alternatively you can add it by:
Updating through the package manager when the option is available
Adding it by name (Package Manager → “+” → “Install Package By Name” → And entering this line to the name field “com.unity.inputsystem” and the version as 1.14.1
Directly editing the manifest file in your project’s directory → packages/manifest.json and adding this line: “com.unity.inputsystem”: “1.14.1”
This version focuses on the various important bug fixes as well as adding support for Xbox controllers over USB on macOS.
For more details about all the improvements and fixes in the package please see the package changelog.
This behaviour is incredibly irritating that you cannot disable input action maps if they were set as project wide inputs and also the behaviour that they are activated only in editor is extremly weird
Any chance the Xbox impulse trigger can be supported in the future? There is the IXboxOneRumble and SetMotorSpeeds in the documentation, but it doesnt same to be implemented. Thanks😁
It would be nice if Unity could provide a Job/Burst-compatible API just to read raw values out of actions. That way, the Job/Burst crowd can roll their own job-ified input logic without needing to stick to the main thread. By the way, we don’t actually need any of the Action callback-y stuff at all, so don’t let that stop you or even the dynamic modification of maps, bindings and so on be done from burst; just reading the raw values would already be very useful. And I can’t think of a reason not to support that.
Also, this work having to be done on the main thread is usually a minor inconvenience but… can graduate to an actual problem in a few cases — especially in high-perf-requirement game genres such as, in my own case, fighting games.
Do you guys have any plans in the books for something like this? If so, could you provide a non-comital ETA (just a ballpark)? If not, could you tell us why that is of low priority/value to you guys (this would point to a hesitancy to make the package more compatible with DOTS so it’d be nice to know what that is about )?
)?