diff options
Diffstat (limited to 'doc/classes/ARVRServer.xml')
| -rw-r--r-- | doc/classes/ARVRServer.xml | 50 |
1 files changed, 25 insertions, 25 deletions
diff --git a/doc/classes/ARVRServer.xml b/doc/classes/ARVRServer.xml index 6f5a76943f..af1a1b0fff 100644 --- a/doc/classes/ARVRServer.xml +++ b/doc/classes/ARVRServer.xml @@ -1,10 +1,10 @@ <?xml version="1.0" encoding="UTF-8" ?> <class name="ARVRServer" inherits="Object" category="Core" version="3.2"> <brief_description> - This is our AR/VR Server. + The AR/VR server. </brief_description> <description> - The AR/VR Server is the heart of our AR/VR solution and handles all the processing. + The AR/VR server is the heart of our AR/VR solution and handles all the processing. </description> <tutorials> </tutorials> @@ -17,12 +17,12 @@ <argument index="1" name="keep_height" type="bool"> </argument> <description> - 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. + 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. </description> </method> <method name="find_interface" qualifiers="const"> @@ -31,7 +31,7 @@ <argument index="0" name="name" type="String"> </argument> <description> - 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. + 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. </description> </method> <method name="get_hmd_transform"> @@ -47,21 +47,21 @@ <argument index="0" name="idx" type="int"> </argument> <description> - Get the interface registered at a given index in our list of interfaces. + Gets the interface registered at a given index in our list of interfaces. </description> </method> <method name="get_interface_count" qualifiers="const"> <return type="int"> </return> <description> - Get the number of interfaces currently registered with the AR/VR server. If your 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 [code]true[/code]. + Gets 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 [code]true[/code]. </description> </method> <method name="get_interfaces" qualifiers="const"> <return type="Array"> </return> <description> - Returns a list of available interfaces with both id and name of the interface. + Returns a list of available interfaces the ID and name of each interface. </description> </method> <method name="get_last_commit_usec"> @@ -86,7 +86,7 @@ <return type="Transform"> </return> <description> - Gets our reference frame transform, mostly used internally and exposed for GDNative build interfaces. + Gets the reference frame transform. Mostly used internally and exposed for GDNative build interfaces. </description> </method> <method name="get_tracker" qualifiers="const"> @@ -95,22 +95,22 @@ <argument index="0" name="idx" type="int"> </argument> <description> - Get the positional tracker at the given ID. + Gets the positional tracker at the given ID. </description> </method> <method name="get_tracker_count" qualifiers="const"> <return type="int"> </return> <description> - Get the number of trackers currently registered. + Gets the number of trackers currently registered. </description> </method> </methods> <members> - <member name="primary_interface" type="ARVRInterface" setter="set_primary_interface" getter="get_primary_interface"> + <member name="primary_interface" type="ARVRInterface" setter="set_primary_interface" getter="get_primary_interface" default="null"> </member> - <member name="world_scale" type="float" setter="set_world_scale" getter="get_world_scale"> - Allows you to adjust the scale to your game's units. Most AR/VR platforms assume a scale of 1 game world unit = 1 meter in the real world. + <member name="world_scale" type="float" setter="set_world_scale" getter="get_world_scale" default="1.0"> + 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. </member> </members> <signals> @@ -118,14 +118,14 @@ <argument index="0" name="interface_name" type="String"> </argument> <description> - Signal send when a new interface has been added. + Emitted when a new interface has been added. </description> </signal> <signal name="interface_removed"> <argument index="0" name="interface_name" type="String"> </argument> <description> - Signal send when an interface is removed. + Emitted when an interface is removed. </description> </signal> <signal name="tracker_added"> @@ -136,7 +136,7 @@ <argument index="2" name="id" type="int"> </argument> <description> - 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. + Emitted when a new tracker has been added. If you don't use a fixed number of controllers or if you're using [ARVRAnchor]s 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. </description> </signal> <signal name="tracker_removed"> @@ -147,19 +147,19 @@ <argument index="2" name="id" type="int"> </argument> <description> - 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). + 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). </description> </signal> </signals> <constants> <constant name="TRACKER_CONTROLLER" value="1" enum="TrackerType"> - Our tracker tracks the location of a controller. + The tracker tracks the location of a controller. </constant> <constant name="TRACKER_BASESTATION" value="2" enum="TrackerType"> - Our tracker tracks the location of a base station. + The tracker tracks the location of a base station. </constant> <constant name="TRACKER_ANCHOR" value="4" enum="TrackerType"> - Our tracker tracks the location and size of an AR anchor. + The tracker tracks the location and size of an AR anchor. </constant> <constant name="TRACKER_ANY_KNOWN" value="127" enum="TrackerType"> Used internally to filter trackers of any known type. |