This is our AR/VR Server.
|void||center_on_hmd ( int rotation_mode, bool keep_height )|
|ARVRInterface||find_interface ( String name ) const|
|ARVRInterface||get_interface ( int idx ) const|
|int||get_interface_count ( ) const|
|Array||get_interfaces ( ) const|
|Transform||get_reference_frame ( ) const|
|ARVRPositionalTracker||get_tracker ( int idx ) const|
|int||get_tracker_count ( ) const|
|void||set_primary_interface ( ARVRInterface interface )|
Signal send when a new interface has been added.
Signal send when an interface is removed.
Signal send 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 and add the appropriate ARVRController or ARVRAnchor node related to this new tracker.
Signal send 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 AR/VR Server is the heart of our AR/VR solution and handles all the processing.
This is a really 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 its often the location of the tracking camera.
This method allows you to center our tracker on the location of the HMD, it will take the current location of the HMD and use that to adjust all our tracking data in essence realigning the real world to your players current position in your game world.
For this method to produce usable results tracking information should be available and this often takes a few frames after starting your game.
You should call this method after a few seconds have passed, when the user requests a realignment of the display holding a designated button on a controller for a short period of time, and when implementing a teleport mechanism.
Find an interface by its name. Say that you’re making a game that uses specific capabilities of an AR/VR platform you can find the interface for that platform by name and initialize it.
Get the interface registered at a given index in our list of interfaces.
Get the number of interfaces currently registered with the AR/VR server. If you’re game supports multiple AR/VR platforms you can look through the available interface and either present the user with a selection or simply try an initialize each interface and use the first one that returns true.
Returns a list of available interfaces with both id and name of the interface.
Gets our reference frame transform, mostly used internally and exposed for GDNative build interfaces.
Get the positional tracker at the given ID.
Get the number of trackers currently registered.
Changes the primary interface to the specified interface. Again mostly exposed for GDNative interfaces.
© 2014–2018 Juan Linietsky, Ariel Manzur, Godot Engine contributors
Licensed under the MIT License.