A spatial node representing a spatially-tracked controller. This is a helper spatial node that is linked to the tracking of controllers. It also offers several handy passthroughs to the state of buttons and such on the controllers. Controllers are linked by their ID. You can create controller nodes before the controllers are available. If your game always uses two controllers (one for each hand), you can predefine the controllers with ID 1 and 2; they will become active as soon as the controllers are identified. If you expect additional controllers to be used, you should react to the signals and add XRController3D nodes to your scene. The position of the controller node is automatically updated by the [XRServer]. This makes this node ideal to add child nodes to visualize the controller. As many XR runtimes now use a configurable action map all inputs are named. $DOCS_URL/tutorials/vr/index.html Returns a [Vector2] for the input with the given [code]name[/code]. This is used for thumbsticks and thumbpads found on many controllers. Returns the hand holding this controller, if known. See [enum XRPositionalTracker.TrackerHand]. Returns a numeric value for the input with the given [code]name[/code]. This is used for triggers and grip sensors. Returns [code]true[/code] if the button with the given [code]name[/code] is pressed. The degree to which the controller vibrates. Ranges from [code]0.0[/code] to [code]1.0[/code] with precision [code].01[/code]. If changed, updates [member XRPositionalTracker.rumble] accordingly. This is a useful property to animate if you want the controller to vibrate for a limited duration. Emitted when a button on this controller is pressed. Emitted when a button on this controller is released. Emitted when a thumbstick or thumbpad on this controller is moved. Emitted when a trigger or similar input on this controller changes value.