This page has been translated automatically.
Video Tutorials
Interface
Essentials
Advanced
How To
UnigineEditor
Interface Overview
Assets Workflow
Settings and Preferences
Working With Projects
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Lighting
Landscape Tool
Sandworm
Using Editor Tools for Specific Tasks
Extending Editor Functionality
Built-in Node Types
Nodes
Objects
Effects
Decals
Light Sources
Geodetics
World Nodes
Sound Objects
Pathfinding Objects
Players
Programming
Fundamentals
Setting Up Development Environment
Usage Examples
C++
C#
UnigineScript
UUSL (Unified UNIGINE Shader Language)
Plugins
File Formats
Rebuilding the Engine Tools
GUI
Double Precision Coordinates
API
Containers
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Objects-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
IG Plugin
CIGIConnector Plugin
Rendering-Related Classes
Content Creation
Content Optimization
Materials
Material Nodes Library
Miscellaneous
Input
Math
Matrix
Textures
Art Samples
Tutorials
Warning! This version of documentation is OUTDATED, as it describes an older SDK version! Please switch to the documentation for the latest SDK version.
Warning! This version of documentation describes an old SDK version which is no longer supported! Please upgrade to the latest SDK version.

LeapMotionHand Class

Warning
The scope of applications for UnigineScript is limited to implementing materials-related logic (material expressions, scriptable materials, brush materials). Do not use UnigineScript as a language for application logic, please consider C#/C++ instead, as these APIs are the preferred ones. Availability of new Engine features in UnigineScript (beyond its scope of applications) is not guaranteed, as the current level of support assumes only fixing critical issues.
Notice
LeapMotion plugin must be loaded.

Hands are the main entity tracked by the Leap Motion controller. The controller maintains an inner model of the human hand and validates the data from its sensors against this model. This allows the controller to track finger positions even when a finger is not completely visible.

Notice
It is possible for movement or changes in position to be lost when a finger is behind or directly in front of the hand (from the point of view of the controller).

The Leap Motion software matches the internal model against the existing data. In some cases, the software can make an incorrect match – for example, identifying a right hand as a left hand.

The Hand class represents a physical hand detected by the Leap and provides access to its attributes describing the hand position, orientation, and movement.

LeapMotionHand Class

Members


int getId ( ) #

Returns the id of the hand.

Return value

ID of the hand

int getType ( ) #

Return value

Type of the hand:
  • 0 - left hand
  • 1 - right hand

float getPalmWidth ( ) #

Returns the width of the palm when the hand is in a flat position, in meters.

Return value

Width of the palm when the hand is in a flat position, in meters.

vec3 getPalmPosition ( ) #

Returns the coordinates of the position of the palm.
Notice
All coordinates are relative to the origin of the Leap Motion coordinate system.

Return value

Coordinates of the position of the palm.

vec3 getStabilizedPalmPosition ( ) #

Returns the modified palm position with some additional smoothing and stabilization applied. Smoothing and stabilization is performed in order to make this value more suitable for interaction with 2D content. The stabilized position lags behind the palm position by a variable amount, depending primarily on the speed of movement.
Notice
All coordinates are relative to the origin of the Leap Motion coordinate system.

Return value

Coordinates of the modified palm position with some additional smoothing and stabilization applied. Smoothing and stabilization is performed in order to make this value more suitable for interaction with 2D content. The stabilized position lags behind the palm position by a variable amount, depending primarily on the speed of movement.

vec3 getWristPosition ( ) #

Returns the coordinates of the position of the wrist.
Notice
All coordinates are relative to the origin of the Leap Motion coordinate system.

Return value

Coordinates of the position of the wrist.

vec3 getPalmVelocity ( ) #

Returns the rate of change of the palm position, in m/s.

Return value

Rate of change of the palm position, in m/s.

vec3 getPalmNormal ( ) #

Returns the coordinates of the normal vector to the palm. If a hand is flat, this vector will point downward, or "out" of the front surface of your palm.
Notice
All coordinates are relative to the origin of the Leap Motion coordinate system.

Return value

Coordinates of the normal vector to the palm.

vec3 getDirection ( ) #

Returns the normalized direction from the palm position toward the fingers.
Notice
All coordinates are relative to the origin of the Leap Motion coordinate system.

Return value

Normalized direction from the palm position toward the fingers.

mat4 getBasis ( ) #

Returns the orthonormal basis vectors for this Bone as a Matrix.

Basis vectors specify the orientation of a bone:

  • X - Perpendicular to the longitudinal axis of the bone; exits the sides of the finger.
  • Y (or up vector) - Perpendicular to the longitudinal axis of the bone; exits the top and bottom of the finger. More positive in the upward direction.
  • Z - Aligned with the longitudinal axis of the bone. More positive toward the base of the finger.

The bases provided for the right hand use the right-hand rule; those for the left hand use the left-hand rule. Thus, the positive direction of the x-basis is to the right for the right hand and to the left for the left hand. You can change from right-hand to left-hand rule by multiplying the z basis vector by -1.

You can use the basis vectors for such purposes as measuring complex finger poses and skeletal animation.

Notice
Converting the basis vectors directly into a quaternion representation is not mathematically valid. If you use quaternions, create them from the derived rotation matrix not directly from the bases.

Return value

Orthonormal basis vectors for this Bone as a Matrix.

int isValid ( ) #

Returns a value indicating if the hand contains valid tracking data.

Return value

1 if the hand contains valid tracking data; otherwise, 0.
Last update: 2021-12-13
Build: ()