godot-docs-l10n/sphinx/templates/tutorials/xr/xr_action_map.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2014-present Juan Linietsky, Ariel Manzur and the Godot community (CC BY 3.0)
# This file is distributed under the same license as the Godot Engine package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Godot Engine latest\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../docs/tutorials/xr/xr_action_map.rst:4
msgid "The XR action map"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:6
msgid "Godot has an action map feature as part of the XR system. At this point in time this system is part of the OpenXR module. There are plans to encompass WebXR into this in the near future hence we call it the XR action map system in this document. It implements the built-in action map system of OpenXR mostly exactly as it is offered."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:12
msgid "The XR action map system exposes input, positional data and output for XR controllers to your game/application. It does this by exposing named actions that can be tailored to your game/application and binding these to the actual inputs and outputs on your XR devices."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:17
msgid "As the XR action map is currently part of the OpenXR module, OpenXR needs to be enabled in your project settings to expose it:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:22
msgid "You will then find the XR Action Map interface in the bottom of the screen:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:27
msgid "Godot's built-in input system has many things in common with the XR action map system. In fact our original idea was to add functionality to the existing input system and expose the data to the OpenXR action map system. We may revisit that idea at some point but as it turns out there were just too many problems to overcome. To name a few:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:34
msgid "Godot's input system mainly centers around button inputs, XR adds triggers, axis, poses and haptics (output) into the mix. This would greatly complicate the input system with features that won't work for normal controllers or contrast with the current approach. It was felt this would lead to confusion for the majority of Godot users."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:39
msgid "Godot's input system works with raw input data that is parsed and triggers emitting actions. This input data is made available to the end user. OpenXR completely hides raw data and does all the parsing for us, we only get access to already parsed action data. This inconsistency is likely to lead to bugs when an unsuspecting user tries to use an XR device as a normal input device."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:46
msgid "Godot's input system allows changes to what inputs are bound to actions in runtime, OpenXR does not."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:48
msgid "Godot's input system is based on device ids which are meaningless in OpenXR."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:50
msgid "This does mean that a game/application that mixes traditional inputs with XR controllers will have a separation. For most applications either one or the other is used and this is not seen as a problem. In the end, it's a limitation of the system."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:56
msgid "The default action map"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:58
msgid "Godot will automatically create a default action map if no action map file is found."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:61
msgid "This default map was designed to help developers port their XR games/applications from Godot 3 to Godot 4. As a result this map essentially binds all known inputs on all controllers supported by default, to actions one on one. This is not a good example of setting up an action map. It does allow a new developer to have a starting point when they want to become familiar with Godot XR. It prevents having to design a proper action map for their game/application first."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:70
msgid "For this walkthrough we're going to start with a blank action map. You can delete the \"Godot action set\" entry at the top by pressing the trash can icon. This will clear out all actions. You might also want to remove the controllers that you do not wish to setup, more on this later."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:77
msgid "Action sets"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:80
msgid "Before we dive in, you will see the term XR runtime used throughout this document. With XR runtime we mean the software that is controlling and interacting with the AR or VR headset. The XR runtime then exposes this to us through an API such as OpenXR. So:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:86
msgid "for Steam this is SteamVR,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:87
msgid "for Meta on desktop this is the Oculus Client (including when using Quest link),"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:88
msgid "for Meta on Quest this is the Quest's native OpenXR client,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:89
msgid "on Linux this could be Monado, etc."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:91
msgid "The action map allows us to organize our actions in sets. Each set can be enabled or disabled on its own."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:94
msgid "The concept here is that you could have different sets that provide bindings in different scenarios. You could have:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:98
msgid "a ``Character control`` set for when you're walking around,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:99
msgid "a ``Vehicle control`` set for when you're operating a vehicle,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:100
msgid "a ``Menu`` set for when a menu is open."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:102
msgid "Only the action set applicable to the current state of your game/application can then be enabled."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:105
msgid "This is especially important if you wish to bind the same input on a controller to a different action. For instance:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:109
msgid "in your ``Character control`` set you may have an action ``Jump``,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:110
msgid "in your ``Vehicle control`` set you may have an action ``Accelerate``,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:111
msgid "in your ``Menu`` set you may have an action ``Select``."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:113
msgid "All are bound to the trigger on your controller."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:115
msgid "OpenXR will only bind an input or output to a single action. If the same input or output is bound to multiple actions the one in the active action set with the highest priority will be the one updated/used. So in our above example it will thus be important that only one action set is active."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:120
msgid "For your first XR game/application we highly recommend starting with just a single action set and to not over-engineer things."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:123
msgid "For our walkthrough in this document we will thus create a single action set called ``my_first_action_set``. We do this by pressing the :button:`Add action set` button:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:129
#: ../../docs/tutorials/xr/xr_action_map.rst:218
msgid "The columns in our table are as follows:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:137
#: ../../docs/tutorials/xr/xr_action_map.rst:226
msgid "Col"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:138
#: ../../docs/tutorials/xr/xr_action_map.rst:227
msgid "Value"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:139
#: ../../docs/tutorials/xr/xr_action_map.rst:228
msgid "Description"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:140
#: ../../docs/tutorials/xr/xr_action_map.rst:229
msgid "1"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:141
msgid "my_first_action_set"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:142
msgid "This is the internal name of the action set. OpenXR doesn't specify specific restrictions on this name other then size, however some XR runtimes will not like spaces or special characters."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:145
#: ../../docs/tutorials/xr/xr_action_map.rst:234
msgid "2"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:146
msgid "My first action set"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:147
msgid "This is a human-readable name for the action set. Some XR runtimes will display this name to the end user, for example in configuration dialogs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:150
#: ../../docs/tutorials/xr/xr_action_map.rst:239
msgid "3"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:151
msgid "0"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:152
msgid "This is the priority of the action set. If multiple active action sets have actions bound to the same controller's inputs or outputs, the action set with the highest priority value will determine the action that is updated."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:158
msgid "Actions"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:160
msgid "In the XR action map, actions are the entities that your game/application will interact with. For instance, we can define an action ``Shoot`` and the input bound to that action will trigger the ``button_pressed`` signal on the relevant :ref:`XRController3D <class_xrcontroller3d>` node in your scene with ``Shoot`` as the ``name`` parameter of the signal."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:166
msgid "You can also poll the current state of an action. :ref:`XRController3D <class_xrcontroller3d>` for instance has an ``is_button_pressed`` method."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:170
msgid "Actions can be used for both input and output and each action has a type that defines its behavior."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:173
msgid "The ``Bool`` type is used for discrete input like buttons."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:174
msgid "The ``Float`` type is used for analogue input like triggers."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:176
msgid "These two are special as they are the only ones that are interchangeable. OpenXR will handle conversions between ``Bool`` and ``Float`` inputs and actions. You can get the value of a ``Float`` type action by calling the method ``get_float`` on your :ref:`XRController3D <class_xrcontroller3d>` node. It emits the ``input_float_changed`` signal when changed."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:183
msgid "Where analogue inputs are queried as buttons a threshold is applied. This threshold is currently managed exclusively by the XR runtime. There are plans to extend Godot to provide some level of control over these thresholds in the future."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:188
msgid "The ``Vector2`` type defines the input as an axis input. Touchpads, thumbsticks and similar inputs are exposed as vectors. You can get the value of a ``Vector2`` type action by calling the method ``get_vector2`` on your :ref:`XRController3D <class_xrcontroller3d>` node. It emits the ``input_vector2_changed`` signal when changed."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:194
msgid "The ``Pose`` type defines a spatially tracked input. Multiple \"pose\" inputs are available in OpenXR: ``aim``, ``grip`` and ``palm``. Your :ref:`XRController3D <class_xrcontroller3d>` node is automatically positioned based on the pose action assigned to ``pose`` property of this node. More about poses later."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:201
msgid "The OpenXR implementation in Godot also exposes a special pose called ``Skeleton``. This is part of the hand tracking implementation. This pose is exposed through the ``skeleton`` action that is supported outside of the action map system. It is thus always present if hand tracking is supported. You don't need to bind actions to this pose to use it."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:208
msgid "Finally, the only output type is ``Haptic`` and it allows us to set the intensity of haptic feedback, such as controller vibration. Controllers can have multiple haptic outputs and support for haptic vests is coming to OpenXR."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:213
msgid "So lets add an action for our aim pose, we do this by clicking on the ``+`` button for our action set:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:230
msgid "aim_pose"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:231
msgid "This is the internal name of the action. OpenXR doesn't specify specific restrictions on this name other then size, however some XR runtimes will not like spaces or special characters."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:235
msgid "Aim pose"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:236
msgid "This is a human-readable name for the action. Some XR runtimes will display this name to the end user, for example in configuration dialogs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:240
msgid "Pose"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:241
msgid "The type of this action."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:243
msgid "OpenXR defines a number of bindable input poses that are commonly available for controllers. There are no rules for which poses are supported for different controllers. The poses OpenXR currently defines are:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:248
msgid "The aim pose on most controllers is positioned slightly in front of the controller and aims forward. This is a great pose to use for laser pointers or to align the muzzle of a weapon with."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:252
msgid "The grip pose on most controllers is positioned where the grip button is placed on the controller. The orientation of this pose differs between controllers and can differ for the same controller on different XR runtimes."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:256
msgid "The palm pose on most controllers is positioned in the center of the palm of the hand holding the controller. This is a new pose that is not available on all XR runtimes."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:261
msgid "If hand tracking is used, there are currently big differences in implementations between the different XR runtimes. As a result the action map is currently not suitable for hand tracking. Work is being done on this so stay tuned."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:266
msgid "Let's complete our list of actions for a very simple shooting game/application:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:270
msgid "The actions we have added are:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:272
msgid "movement, which allows the user to move around outside of normal room scale tracking."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:273
msgid "grab, which detects that the user wants to hold something."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:274
msgid "shoot, which detects that the user wants to fire the weapon they are holding."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:275
msgid "haptic, which allows us to output haptic feedback."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:277
msgid "Now note that we don't distinguish between the left and right hand. This is something that is determined at the next stage. We've implemented the action system in such a way that you can bind the same action to both hands. The appropriate :ref:`XRController3D <class_xrcontroller3d>` node will emit the signal."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:284
msgid "For both grab and shoot we've used the ``Bool`` type. As mentioned before, OpenXR does automatic conversions from an analogue controls however not all XR Runtimes currently apply sensible thresholds."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:288
msgid "We recommend as a workaround to use the ``Float`` type when interacting with triggers and grip buttons and apply your own threshold."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:291
msgid "For buttons like A/B/X/Y and similar where there is no analogue option, the ``Bool`` type works fine."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:295
msgid "You can bind the same action to multiple inputs for the same controller on the same profile. In this case the XR runtime will attempt to combine the inputs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:299
msgid "For ``Bool`` inputs, this will perform an ``OR`` operation between the buttons."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:300
msgid "For ``Float`` inputs, this will take the highest value of the bound inputs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:301
msgid "The behavior for ``Pose`` inputs is undefined, but the first bound input is likely to be used."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:304
msgid "You shouldn't bind multiple actions of the same action set to the same controller input. If you do this, or if actions are bound from multiple action sets but they have overlapping priorities, the behavior is undefined. The XR runtime may simply not accept your action map, or it may take this on a first come first serve basis."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:310
msgid "We are still investigating the restrictions around binding multiple actions to the same output as this scenario makes sense. The OpenXR specification seems to not allow this."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:314
msgid "Now that we have our basic actions defined, it's time to hook them up."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:317
msgid "Profiles"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:319
msgid "In OpenXR controller bindings are captured in so-called \"Interaction Profiles\". We've shortened it to \"Profiles\" because it takes up less space."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:322
msgid "This generic name is chosen because controllers don't cover the entire system. Currently there are also profiles for trackers, remotes and tracked pens. There are also provisions for devices such as treadmills, haptic vests and such even though those are not part of the specification yet."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:327
msgid "It is important to know that OpenXR has strict checking on supported devices. The core specification identifies a number of controllers and similar devices with their supported inputs and outputs. Every XR runtime must accept these interaction profiles even if they aren't applicable."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:332
msgid "New devices are added through extensions and XR runtimes must specify which ones they support. XR runtimes that do not support a device added through extensions will not accept these profiles. XR runtimes that do not support added input or output types will often crash if supplied."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:339
msgid "As such Godot keeps meta data of all available devices, their inputs and outputs and which extension adds support for them. You can create interaction profiles for all devices you wish to support. Godot will filter out those not supported by the XR runtime the user is using."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:344
msgid "This does mean that in order to support new devices, you might need to update to a more recent version of Godot."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:347
msgid "It is however also important to note that the action map has been designed with this in mind. When new devices enter the market, or when your users use devices that you do not have access to, the action map system relies on the XR runtime. It is the XR runtime's job to choose the best fitting interaction profile that has been specified and adapt it for the controller the user is using."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:354
msgid "How the XR runtime does this is left to the implementation of the runtime and there are thus vast differences between the runtimes. Some runtimes might even permit users to edit the bindings themselves."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:358
msgid "A common approach for a runtime is to look for a matching interaction profile first. If this is not found it will check the most common profiles such as that of the \"Touch controller\" and do a conversion. If all else fails, it will check the generic :ref:`\"Simple controller\" <doc_xr_action_map_simple>`."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:364
msgid "There is an important conclusion to be made here: When a controller is found, and the action map is applied to it, the XR runtime is not limited to the exact configurations you set up in Godot's action map editor. While the runtime will generally choose a suitable mapping based on one of the bindings you set up in the action map, it can deviate from it."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:370
msgid "For example, when the Touch controller profile is used any of the following scenarios could be true:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:373
msgid "we could be using a Quest 1 controller,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:374
msgid "we could be using a Quest 2 controller,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:375
msgid "we could be using a Quest Pro controller but no Quest Pro profile was given or the XR runtime being used does not support the Quest Pro controller,"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:377
msgid "it could be a completely different controller for which no profile was given but the XR runtime is using the touch bindings as a base."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:380
msgid "Ergo, there currently is no way to know with certainty, which controller the user is actually using."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:384
msgid "Finally, and this trips up a lot of people, the bindings aren't set in stone. It is fully allowed, and even expected, that an XR runtime allows a user to customise the bindings."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:388
msgid "At the moment none of the XR runtimes offer this functionality though SteamVR has an existing UI from OpenVRs action map system that is still accessible. This is actively being worked on however."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:393
msgid "Our first controller binding"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:395
msgid "Let's set up our first controller binding, using the Touch controller as an example."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:397
msgid "Press \"Add profile\", find the Touch controller, and add it. If it is not in the list, then it may already have been added."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:402
msgid "Our UI now shows panels for both the left and right controllers. The panels contain all of the possible inputs and outputs for each controller. We can use the ``+`` next to each entry to bind it to an action:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:408
msgid "Let's finish our configuration:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:412
msgid "Each action is bound the given input or output for both controllers to indicate that we support the action on either controller. The exception is the movement action which is bound only to the right hand controller. It is likely that we would want to use the left hand thumbstick for a different purpose, say a teleport function."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:418
msgid "In developing your game/application you have to account for the possibility that the user changes the binding and binds the movement to the left hand thumbstick."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:421
msgid "Also note that our shoot and grab boolean actions are linked to inputs of type ``Float``. As mentioned before OpenXR will do conversions between the two, but do read the warning given on that subject earlier in this document."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:426
msgid "Some of the inputs seem to appear in our list multiple times."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:428
msgid "For instance we can find the ``X`` button twice, once as ``X click`` and then as ``X touch``. This is due to the Touch controller having a capacitive sensor."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:432
msgid "``X touch`` will be true if the user is merely touching the X button."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:433
msgid "``X click`` will be true when the user is actually pressing down on the button."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:435
msgid "Similarly for the thumbstick we have:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:437
msgid "``Thumbstick touch`` which will be true if the user is touching the thumbstick."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:438
msgid "``Thumbstick`` which gives a value for the direction the thumbstick is pushed to."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:439
msgid "``Thumbstick click`` which is true when the user is pressing down on the thumbstick."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:441
msgid "It is important to note that only a select number of XR controllers support touch sensors or have click features on thumbsticks. Keep that in mind when designing your game/application. Make sure these are used for optional features of your game/application."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:449
msgid "The simple controller"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:451
msgid "The \"Simple controller\" is a generic controller that OpenXR offers as a fallback. We'll apply our mapping:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:456
msgid "As becomes painfully clear, the simple controller is often far too simple and falls short for anything but the simplest of VR games/applications."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:459
msgid "This is why many XR runtimes only use it as a last resort and will attempt to use bindings from one of the more popular systems as a fallback first."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:463
msgid "Due to the simple controller likely not covering the needs of your game, it is tempting to provide bindings for every controller supported by OpenXR. The default action map seems to suggest this as a valid course of action. As mentioned before, the default action map was designed for ease of migration from Godot 3."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:469
msgid "It is the recommendation from the OpenXR Working Group that only bindings for controllers actually tested by the developer are setup. The XR runtimes are designed with this in mind. They can perform a better job of rebinding a provided binding than a developer can make educated guesses. Especially as the developer can't test if this leads to a comfortable experience for the end user."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:477
msgid "This is our advice as well: limit your action map to the interaction profiles for devices you have actually tested your game with. The Oculus Touch controller is widely used as a fallback controller by many runtimes. If you are able to test your game using a Meta Rift or Quest and add this profile there is a high probability your game will work with other headsets."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:486
msgid "Binding Modifiers"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:488
msgid "One of the main goals of the action map is to remove the need for the application to know the hardware used. However, sometimes the hardware has physical differences that require inputs to be altered in ways other than how they are bound to actions. This need ranges from setting thresholds, to altering the inputs available on a controller."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:495
msgid "Binding modifiers are not enabled by default and require enabling in the OpenXR project settings. Also there is no guarantee that these modifiers are supported by every runtime. You will need to consult the support for the runtimes you are targeting and decide whether to rely on the modifiers or implement some form of fallback mechanism."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:501
msgid "If you are targeting multiple runtimes that have support for the same controllers, you may need to create separate action maps for each runtime. You can control which action map Godot uses by using different export templates for each runtime and using a custom :ref:`feature tag <doc_feature_tags>` to set the action map."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:507
msgid "In Godot, binding modifiers are divided into two groups: modifiers that work on the interaction profile level, and modifiers that work on individual bindings."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:512
msgid "Binding modifiers on an interaction profile"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:514
msgid "Binding modifiers that are applied to the whole interaction profile can be accessed through the modifier button on the right side of the interaction profile editor."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:519
#: ../../docs/tutorials/xr/xr_action_map.rst:586
msgid "You can add a new modifier by pressing the :button:`Add binding modifier` button."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:522
msgid "As Godot doesn't know which controllers and runtimes support a modifier, there is no restriction to adding modifiers. Unsupported modifiers will be ignored."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:527
msgid "Dpad Binding modifier"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:529
msgid "The dpad binding modifier adds new inputs to an interaction profile for each joystick and thumbpad input on this controller. It turns the input into a dpad with separate up, down, left and right inputs that are exposed as buttons:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:537
msgid "Inputs related to extensions are denoted with an asterix."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:539
msgid "In order to use the dpad binding modifier you need to enable the dpad binding modifier extension in project settings:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:544
msgid "Enabling the extension is enough to make this functionality work using default settings."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:546
msgid "Adding the modifier is optional and allows you to fine tune the way the dpad functionality behaves. You can add the modifier multiple times to set different settings for different inputs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:552
msgid "These settings are used as follows:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:554
msgid "``Action Set`` defines the action set to which these settings are applied."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:555
msgid "``Input Path`` defines the original input that is mapped to the new dpad inputs."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:556
msgid "``Threshold`` specifies the threshold value that will enable a dpad action, e.g. a value of ``0.6`` means that if the distance from center goes above ``0.6`` the dpad action is pressed."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:559
msgid "``Threshold Released`` specifies the threshold value that will disable a dpad action, e.g. a value of ``0.4`` means that if the distance from center goes below ``0.4`` the dpad action is released."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:562
msgid "``Center Region`` specifies the distance from center that enabled the center action, this is only supported for trackpads."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:564
msgid "``Wedge Angle`` specifies the angle of each wedge. A value of ``90 degrees`` or lower means that up, down, left and right each have a separate slice in which they are in the pressed state. A value above ``90 degrees`` means that the slices overlap and that multiple actions can be in the pressed state."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:569
msgid "``Is Sticky``, when enabled means that an action stays in the pressed state until the thumbstick or trackpad moves into another wedge even if it has left the wedge for that action."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:572
msgid "``On Haptic`` lets us define a haptic output that is automatically activated when an action becomes pressed."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:574
msgid "``Off Haptic`` lets us define a haptic output that is automatically activated when an action is released."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:579
msgid "Binding modifiers on individual bindings"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:581
msgid "Binding modifiers that are applied to individual bindings can be accessed through the binding modifier button next to action attached to an input:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:589
msgid "As Godot doesn't know which inputs on each runtime support a modifier, there is no restriction to adding modifiers. If the modifier extension is unsupported, modifiers will be filtered out at runtime. Modifiers added to the wrong input may result in a runtime error."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:594
msgid "You should test your action map on the actual hardware and runtime to verify the proper setup."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:598
msgid "Analog threshold modifier"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:600
msgid "The analog threshold modifier allows you to specify the thresholds used for any analog input, like the trigger, that has a boolean input. This controls when the input is in the pressed state."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:604
msgid "In order to use this modifier you must enable the analog threshold extension in the project settings:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:609
msgid "The analog threshold modifier has the following settings:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:613
msgid "These are defined as follows:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:615
msgid "``On Threshold`` specifies the threshold value that will enable the action, e.g. a value of ``0.6`` means that when the analog value gets above ``0.6`` the action is set to the pressed state."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:618
msgid "``Off Threshold`` specifies the threshold value that will disable the action, e.g. a value of ``0.4`` means that when the analog value goes below ``0.4`` the action is set in to the released state."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:621
msgid "``On Haptic`` lets us define a haptic output that is automatically activated when the input is pressed."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:623
msgid "``Off Haptic`` lets us define a haptic output that is automatically activated when the input is released."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:627
msgid "Haptics on modifiers"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:629
msgid "Modifiers can support automatic haptic output that is triggered when thresholds are reached."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:633
msgid "Currently both available modifiers support this feature however there is no rule future modifiers also have this capability. Only one type of haptic feedback is supported but in the future other options may become available."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:639
msgid "Haptic vibration"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:641
msgid "The haptic vibration allows us to specify a simple haptic pulse:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:645
msgid "It has the following options:"
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:647
msgid "``Duration`` is the duration of the pulse in nanoseconds. ``-1`` lets the runtime choose an optimal value for a short pulse suitable for the current hardware."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:649
msgid "``Frequency`` is the frequency of the pulse in Hz. ``0`` lets the runtime choose an optimal frequency for a short pulse suitable for the current hardware."
msgstr ""

#: ../../docs/tutorials/xr/xr_action_map.rst:651
msgid "``Amplitude`` is the amplitude of the pulse."
msgstr ""