Server for AR and VR features.
The AR/VR server is the heart of our Advanced and Virtual Reality solution and handles all the processing.
|void||center_on_hmd ( RotationMode rotation_mode, bool keep_height )|
|ARVRInterface||find_interface ( String name ) const|
|Transform||get_hmd_transform ( )|
|ARVRInterface||get_interface ( int idx ) const|
|int||get_interface_count ( ) const|
|Array||get_interfaces ( ) const|
|int||get_last_commit_usec ( )|
|int||get_last_frame_usec ( )|
|int||get_last_process_usec ( )|
|Transform||get_reference_frame ( ) const|
|ARVRPositionalTracker||get_tracker ( int idx ) const|
|int||get_tracker_count ( ) const|
Emitted when a new interface has been added.
Emitted when an interface is removed.
Emitted when a new tracker has been added. If you don't use a fixed number of controllers or if you're using ARVRAnchors for an AR solution, it is important to react to this signal to add the appropriate ARVRController or ARVRAnchor nodes related to this new tracker.
Emitted when a tracker is removed. You should remove any ARVRController or ARVRAnchor points if applicable. This is not mandatory, the nodes simply become inactive and will be made active again when a new tracker becomes available (i.e. a new controller is switched on that takes the place of the previous one).
The primary ARVRInterface currently bound to the
Allows you to adjust the scale to your game's units. Most AR/VR platforms assume a scale of 1 game world unit = 1 real world meter.
This is an important function to understand correctly. AR and VR platforms all handle positioning slightly differently.
For platforms that do not offer spatial tracking, our origin point (0,0,0) is the location of our HMD, but you have little control over the direction the player is facing in the real world.
For platforms that do offer spatial tracking, our origin point depends very much on the system. For OpenVR, our origin point is usually the center of the tracking space, on the ground. For other platforms, it's often the location of the tracking camera.
This method allows you to center your tracker on the location of the HMD. It will take the current location of the HMD and use that to adjust all your tracking data; in essence, realigning the real world to your player's current position in the game world.
For this method to produce usable results, tracking information must be available. This often takes a few frames after starting your game.
You should call this method after a few seconds have passed. For instance, when the user requests a realignment of the display holding a designated button on a controller for a short period of time, or when implementing a teleport mechanism.
Finds an interface by its name. For instance, if your project uses capabilities of an AR/VR platform, you can find the interface for that platform by name and initialize it.
Returns the primary interface's transformation.
Returns the interface registered at a given index in our list of interfaces.
Returns the number of interfaces currently registered with the AR/VR server. If your project supports multiple AR/VR platforms, you can look through the available interface, and either present the user with a selection or simply try to initialize each interface and use the first one that returns
Returns a list of available interfaces the ID and name of each interface.
Returns the absolute timestamp (in μs) of the last
ARVRServer process callback. The value comes from an internal call to OS.get_ticks_usec.
Returns the reference frame transform. Mostly used internally and exposed for GDNative build interfaces.
Returns the positional tracker at the given ID.
Returns the number of trackers currently registered.
© 2014–2020 Juan Linietsky, Ariel Manzur, Godot Engine contributors
Licensed under the MIT License.