111 lines
8.9 KiB
JSON
111 lines
8.9 KiB
JSON
{
|
|
"name": "com.unity.inputsystem",
|
|
"displayName": "Input System",
|
|
"version": "1.20.1",
|
|
"unity": "6000.0",
|
|
"description": "A new input system which can be used as a more extensible and customizable alternative to Unity's classic input system in UnityEngine.Input.",
|
|
"keywords": [
|
|
"input",
|
|
"events",
|
|
"keyboard",
|
|
"mouse",
|
|
"gamepad",
|
|
"touch",
|
|
"vr",
|
|
"xr"
|
|
],
|
|
"dependencies": {
|
|
"com.unity.modules.uielements": "1.0.0"
|
|
},
|
|
"_upm": {
|
|
"changelog": "### Fixed\n\n- Fixed the Input Actions editor window's unsaved-changes handling on close: it now uses the Editor's built-in save prompt (including on Editor quit), auto-saves pending changes when the window is closed with auto-save enabled, and prompts instead of silently dropping changes if an auto-save fails (e.g. version control refused the checkout). [UUM-154808](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-154808)\n- Fixed misaligned labels in the Input Actions editor properties pane. [UUM-154536](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-154536)\n- Fixed a single click producing two simultaneous touches when the Device Simulator view is open and \"Simulate Touch Input From Mouse or Pen\" is enabled in the Input Debugger; Touch Simulation now suppresses its events while a Device Simulator view is open [UUM-153420]\n- Fixed the search field in the \"Add supported device\" popup (Input System Package Settings > Supported Devices > \"+\") drawing flush against the popup's left edge with no left margin, unlike its right-side spacing; it is now inset to match [UUM-150217](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-150217)\n- Fixed the \"Supported Devices\" list in the Input System Package Settings sitting flush against the panel edge with no left/right margin, unlike the surrounding fields; it is now inset to line up with the other settings controls [UUM-150207](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-150207)\n- Fixed the Inspector help button for a selected `.inputactions` asset (\"Open Reference for Input Action Importer\") opening a missing documentation page; it now links to the Action Assets manual page [UUM-149518](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-149518)\n- Fixed an `OverflowException` when creating a control scheme (or other named item) whose all-numeric name exceeds `Int32.MaxValue`, which previously discarded the entered name and fell back to the default [UUM-145766](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-145766)\n- Fixed the Input Actions editor window logging a \"Failed to load asset\" exception on editor startup when its saved window layout was restored in a project where the referenced asset GUID did not resolve; the window now closes quietly instead [UUM-144318](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-144318)\n- Empty foldouts are no longer shown for processors and interactions that have no settings (e.g. \"Invert\") [UUM-144325](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-144325)\n- Fixed the Input Actions editor toolbar buttons being clipped when the Action Properties panel grew tall enough to show a scrollbar\n- Fixed the Control Schemes dropdown in the Input Actions editor continuing to display a deleted scheme's name after the last control scheme was removed, instead of resetting to \"No Control Schemes\" until the asset was saved or the editor reopened. [UUM-141563](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-141563)\n- Fixed the Input Debugger window (Window > Analysis > Input Debugger) being resizable arbitrarily small until its toolbar and device/action/layout tree view were no longer usably visible; it now enforces a minimum window size [UUM-137119](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-137119)\n- Fixed the Action Maps list in the Input Actions editor losing keyboard focus after deleting a map, so that Delete, Duplicate, and arrow-key navigation kept working on the auto-selected replacement map without requiring an extra click [UUM-147152](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-147152)\n- Fixed the Device Simulator plugin keeping the real mouse and pen disabled while working in other Editor windows. Conflicting native `Mouse`/`Pen` devices are now only disabled while the Simulator window is focused and re-enabled as soon as focus moves elsewhere [UUM-145509](https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-145509).\n- Fixed the Input Actions editor in Project Settings losi"
|
|
},
|
|
"upmCi": {
|
|
"footprint": "0f5d99efbc1f1aa6a17e3d41eea1018cce586908"
|
|
},
|
|
"documentationUrl": "https://docs.unity3d.com/Packages/com.unity.inputsystem@1.20/manual/index.html",
|
|
"repository": {
|
|
"url": "https://github.com/Unity-Technologies/InputSystem.git",
|
|
"type": "git",
|
|
"revision": "a934411756c8862cb0f54da514a9b7cc1c000a2b"
|
|
},
|
|
"samples": [
|
|
{
|
|
"displayName": "Custom Binding Composite",
|
|
"description": "Shows how to implement a custom composite binding.",
|
|
"path": "Samples~/CustomComposite"
|
|
},
|
|
{
|
|
"displayName": "Custom Device",
|
|
"description": "Shows how to implement a custom input device.",
|
|
"path": "Samples~/CustomDevice"
|
|
},
|
|
{
|
|
"displayName": "Custom Device Usages",
|
|
"description": "Shows how to tag devices with custom usage strings that can be used, for example, to distinguish multiple instances of the same type of device (e.g. 'Gamepad') based on how the device is used (e.g. 'Player1' vs 'Player2' or 'LeftHand' vs 'RightHand').",
|
|
"path": "Samples~/CustomDeviceUsages"
|
|
},
|
|
{
|
|
"displayName": "Gamepad Mouse Cursor",
|
|
"description": "An example that shows how to use the gamepad for driving a mouse cursor for use with UIs.",
|
|
"path": "Samples~/GamepadMouseCursor"
|
|
},
|
|
{
|
|
"displayName": "In-Game Hints",
|
|
"description": "Demonstrates how to create in-game hints in the UI which reflect current bindings and active control schemes. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/InGameHints"
|
|
},
|
|
{
|
|
"displayName": "InputDeviceTester",
|
|
"description": "A scene containing UI to visualize the controls on various supported input devices. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/InputDeviceTester"
|
|
},
|
|
{
|
|
"displayName": "Input Recorder",
|
|
"description": "Shows how to capture and replay input events. Also useful by itself to debug input event sequences.",
|
|
"path": "Samples~/InputRecorder"
|
|
},
|
|
{
|
|
"displayName": "On-Screen Controls",
|
|
"description": "Demonstrates a simple setup for an on-screen joystick.",
|
|
"path": "Samples~/OnScreenControls"
|
|
},
|
|
{
|
|
"displayName": "Rebinding UI",
|
|
"description": "An example UI component that demonstrates how to create UI for rebinding actions. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/RebindingUI"
|
|
},
|
|
{
|
|
"displayName": "Simple Demo",
|
|
"description": "A walkthrough of a simple character controller that demonstrates several techniques for working with the input system. See the README.md file in the sample for details. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/SimpleDemo"
|
|
},
|
|
{
|
|
"displayName": "Simple Multiplayer",
|
|
"description": "Demonstrates how to set up a simple local multiplayer scenario. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/SimpleMultiplayer"
|
|
},
|
|
{
|
|
"displayName": "Touch Samples",
|
|
"description": "A series of sample scenes for using touch input with the Input System package. This sample is not actually part of the package, but needs to be downloaded. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/TouchSamples"
|
|
},
|
|
{
|
|
"displayName": "UI vs. Game Input",
|
|
"description": "An example that shows how to deal with ambiguities that may arise when overlaying interactive UI elements on top of a game scene. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/UIvsGameInput"
|
|
},
|
|
{
|
|
"displayName": "Unity Remote",
|
|
"description": "An example with a simple scene for trying out the Unity Remote app. Requires the Universal Render Pipeline (URP) package to be installed for shader compilation.",
|
|
"path": "Samples~/UnityRemote"
|
|
},
|
|
{
|
|
"displayName": "Visualizers",
|
|
"description": "Several example visualizations of input controls/devices and input actions.",
|
|
"path": "Samples~/Visualizers"
|
|
}
|
|
],
|
|
"_fingerprint": "2436e68c60c469edbccef8f6b3c319b9441f4675"
|
|
}
|