Platform-specific settings

iOS/tvOS

Motion Usage Governs access to the pedometer on the device. If you enable this setting, the Description field becomes editable. The text you enter into the Description field is added to your application's Info.plist.

Editor

Play Mode Input Behavior

Play Mode Input Behavior determines how input is handled in the Editor when in play mode. Unlike in built players, in the Unity Editor the input back-ends keep running for as long as the Editor is active, regardless of whether a Game View window is focused or not. This setting determines how input should behave when focus is not on any Game View – and thus Application.isFocused is false and the player considered to be running in the background.

Setting	Description
Pointers And Keyboards Respect Game View Focus	Only Pointer and Keyboard Devices require the Game View to be focused. Other Devices will route their input into the application regardless of Game View focus. This setting essentially routes any input into the game that is, by default, not used to operate the Editor UI. So, Devices such as gamepads will go to the application at all times when in play mode whereas keyboard input, for example, will require explicitly giving focus to a Game View window. This setting is the default.
All Devices Respect Game View Focus	Focus on a Game View is required for all Devices. When no Game View window is focused, all input goes to the editor and not to the application. This allows other EditorWindows to receive these inputs (from gamepads, for example).
All Device Input Always Goes To Game View	All editor input is disabled and input is considered to be exclusive to Game Views. Also, Background Behavior is to be taken literally and executed like in players. Meaning, if in a certain situation, a Device is disabled in the player, it will get disabled in the editor as well. This setting most closely aligns player behavior with editor behavior. Be aware, however, that no EditorWindows will be able to see input from Devices (this does not effect IMGUI and UITK input in the Editor in general as they do not consume input from the Input System).

Input Action Property Drawer Mode

Determines how the Inspector window displays InputActionProperty fields.

This setting is not shown in the Edit > Project Settings window, it is instead only available in the Debug mode of the Inspector window of an Input Settings asset. See the Unity Manual page for working in the Inspector under section Toggle Debug Mode.

Setting	Description
Compact	Display the property in a compact format, using a minimal number of lines. Toggling between a reference to an input action in an asset and a directly serialized input action is done using a dropdown menu.
Multiline Effective	Display the effective action underlying the property, using multiple lines. Toggling between a reference to an input action in an asset and a directly serialized input action is done using a property that is always visible. This mode could be useful if you want to see or revert prefab overrides and hide the field that is ignored.
Multiline Both	Display both the input action and external reference underlying the property. Toggling between a reference to an input action in an asset and a directly serialized input action is done using a property that is always visible. This mode could be useful if you want to see both values of the property without needing to toggle Use Reference.