NOTE: In an upcoming release of the Open SDK, we aim to support auto configuration of Hand Engine using a “command” OSC address which is listening on the Command Listening Port . Third party applications can send OSC messages to this address to toggle on/off OSC addresses they will receive data from. This allows their application to be setup without a user manually configuring the Hand Engine settings for the Open SDK.

OSC In Hand Engine

Hand Engine 3.1.2-Open-SDK-Beta or higher supports the retargeting of Hand Engine data into various character rig formats and ships with VRM model retargeting built in. Additional retargeting models for character rig types are loaded from JSON files located in the end-user’s local application data folder. Hand Engine creates an OSC client and dispatches OSC messages which can be received by OSC servers listening on specified ports (e.g. OSC servers built in Unity).

To perform duplex data transfer between to applications in OSC, both applications must implement an OSC server for listening to incoming OSC messages, and an OSC client for dispatching OSC messages. Use a different port for each app you wish to receive Open SDK data from Hand Engine. These ports can be adjusted in the Hand Engine Settings menu under Open SDK.

TIP: By default, Hand Engine sends OSC data out on port 9400 . Receiving apps that implement our Open SDK specification in this document can listen on this port using an OSC server and receive animation data for StretchSense gloves.

OSC Arguments

Hand Engine currently implements the signed integer (i), 32-bit float (f) and string (s) OSC argument types which are compatible with all OSC libraries.

NOTE: Null values are represented by -2147483648, so you can ignore these values as they indicate that the particular OSC argument is not to be used by your application.

Open SDK Core

The following functionality is intended to service both non-VR and VR integrations. It assumes that first time setup of gloves and performers has been configured either from within the Hand Engine application or via other OSC addresses.

OSC does not support enums natively. Instead, enums are transmitted as integer values in OSC messages. Developers are expected to implement their own typecasting of the OSC argument value to a structured enum that works with their chosen application framework or language. We recommend this approach as it will make applications easier to adapt for future API changes in future releases based on beta feedback.

INFO: Non-animation OSC messages are dispatched by Hand Engine every second, while animation OSC messages are dispatched as soon as new data is available.

NOTE: In this document, each point that has animation position, rotation and slider values provided by the Open SDK is meant to approximately be the end of the bone closest to the wrist for the purposes of animating a 3D hand in space or communicating the gesture state of the user’s hand. They follow OpenXR naming conventions and the points don’t necessarily align with an anatomical joint. Throughout this document we refer to these points as Bones .

Animation Data

The following case-sensitive OSC addresses have been implemented as part of the Open SDK Core. These are often referred to these by their short name in documentation and the short name is used as a label in the Hand Engine settings screen. Animation data on these addresses has been retargeted to a particular character rig format, as described in the Retargeting section of this document:

Where:

• performerId - the integer ID of the performer in Hand Engine you wish to get data for. The default performerId is 0 and subsequent performers added will be sequential. E.g. 1, 2, 3, 4, 5 etc.

• handedness - an integer representation of the hand you wish to get data for. We suggest setting up an enum in your application to represent the below possible values for handedness:

• 0 = Unknown (not used for getting data but can be used internally by your app if the hand state is not known.

• 1 = Left Hand
• 2 = Right Hand

• finger - a string representation of the finger you wish to get bone data for. Note that these are case sensitive and start with a capital letter:

• Thumb = bones belonging to the thumb

• Index = bones belonging to the index finger
• Middle = bones belonging to the middle finger
• Ring = bones belonging to the ring finger
• Little = bones belonging to the little finger (also known as the “pinky” finger in some animation or interaction systems)

animation/rotation OSC Message Structure

In order to avoid issues with gimbal lock that commonly occur when using Euler angles for animation, this message structure provides quaternion values, suitable for character and hand rigs with 3 bones in the fingers and 2 bones in the thumb. Alternately proximal and intermediate bones can also be assigned to rigs with only 2 bones per finger.

The following Hand Engine remapping target profiles can be used with the animation/rotation OSC message data. Selecting the appropriate one of these are required for the quaternion data to be correctly retargeted to the hand rig in the application consuming the data:

• RAYNOS-chan_1.0.4-Studio.json / RAYNOS-chan_1.0.4-Fidelity.json - Compatible with VRM based models from VRoid Hub or the Sony Mocopi SDK (found under RAYNOS-chan\Retargeting\Hand Engine Retargeting Models in the Sony Mocopi sample in StretchSense Plugin for Unity 3.2.0-RC3 or higher).

animation/rotation OSC Message Argument Order

Each message has 13 arguments that are structured with the following indexes when accessing data for the 3-bone animation/rotation OSC address. You can each arguments data by calculating the correct offset using the index below. Most OSC libraries will do this calculation, so you will just need to provide the index and argument type when reading the data.

animation/rotationWithMetacarpals OSC Message Structure

These are suitable for character and hand rigs with 4 bones per finger and 3 bones in the thumb, commonly used in high-end animation or OpenXR. Unreal Engine 5 also uses 4 bones in its Manny, Quinn and MetaHuman character rigs.

The following Hand Engine remapping target profiles can be used with the animation/rotationWithMetacarpals OSC message data. Selecting the appropriate one of these are required for the quaternion data to be correctly retargeted to the hand rig in the application consuming the data:

• HTC-VIVE-Wave-Hands-Studio.json / HTC-VIVE-Wave-Hands-Fidelity.json - Compatible with the VIVE-Wave SDK’s OpenXR hand model (found under Retargeting\Hand Engine Retargeting Models in the VIVE-Wave sample in StretchSense Plugin for Unity 3.2.0-RC3 or higher).

Animation RotationWithMetacarpals Data OSC Message Formats

Each message has 17 arguments that are structured with the following indexes when accessing data for the 4-bone animation/rotationWithMetacarpals OSC address. You can each arguments data by calculating the correct offset using the index below. Most OSC libraries will do this calculation, so you will just need to provide the index and argument type when reading the data.

Animation Rotation Data OSC Arguments

The below descriptions are for arguments in the animation/rotation and animation/rotationWithMetacarpals OSC addresses.

Hand diagrams below are from Unity’s XR Hands package documentation Hand data model | XR Hands | 1.5.0-pre.1 (unity3d.com):

Metacarpal Rot.	Timecode	Metacarpal Rotation Quaternion X	Metacarpal Rotation Quaternion Y	Metacarpal Rotation Quaternion Z	Metacarpal Rotation Quaternion W
OSC type	integer	float	float	float	float
Language Type	int32 signed	float32 signed	float32 signed	float32 signed	float32 signed
Format	hhmmssfff	x float value to 17 d.p	y float value to 17 d.p	z float value to 17 d.p	w float value to 17 d.p
Example	134255043	-0.1692586	-0.1232476	-0.06889943	0.9754032
Validation	Min: 0, Max: 2147483647	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1
Notes	fff in the format represents a 3-digit frame number for the given second. INFO: Hand Engine supports up to 120FPS data for Pro Fidelity gloves, and 60FPS for Studio gloves.	Quaternion x value of the Proximal bone of the finger.	Quaternion y value of the Proximal bone of the finger.	Quaternion z value of the Proximal bone of the finger.	Quaternion w value of the Proximal bone of the finger.

Proximal Rot.	Timecode	Proximal Rotation Quaternion X	Proximal Rotation Quaternion Y	Proximal Rotation Quaternion Z	Proximal Rotation Quaternion W
OSC type	integer	float	float	float	float
Language Type	int32 signed	float32 signed	float32 signed	float32 signed	float32 signed
Format	hhmmssfff	x float value to 17 d.p	y float value to 17 d.p	z float value to 17 d.p	w float value to 17 d.p
Example	134255043	-0.1692586	-0.1232476	-0.06889943	0.9754032
Validation	Min: 0, Max: 2147483647	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1
Notes	fff in the format represents a 3-digit frame number for the given second. INFO: Hand Engine supports up to 120FPS data for Pro Fidelity gloves, and 60FPS for Studio gloves.	Quaternion x value of the Proximal bone of the finger.	Quaternion y value of the Proximal bone of the finger.	Quaternion z value of the Proximal bone of the finger.	Quaternion w value of the Proximal bone of the finger.

Intermediate Rot.	Intermediate Rotation Quaternion X	Intermediate Rotation Quaternion Y	Intermediate Rotation Quaternion Z	Intermediate Rotation Quaternion W
OSC type	float	float	float	float
Language Type	float32 signed	float32 signed	float32 signed	float32 signed
Format	x float value to 17 d.p	y float value to 17 d.p	z float value to 17 d.p	w float value to 17 d.p
Example	0	-0.1936401	0	0.9810718
Validation	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1
Notes	Quaternion x value of the Intermediate bone of the finger. WARNING: The thumb does not have this bone.	Quaternion y value of the Intermediate bone of the finger. WARNING: The thumb does not have this bone.	Quaternion z value of the Intermediate bone of the finger. WARNING: The thumb does not have this bone.	Quaternion w value of the Intermediate bone of the finger. WARNING: The thumb does not have this bone.

NOTE: The thumb has one fewer bone than the other fingers because thumbs do not have an intermediate bone.

Distal Rot.	Distal Rotation Quaternion X	Distal Rotation Quaternion Y	Distal Rotation Quaternion Z	Distal Rotation Quaternion W
OSC type	float	float	float	float
Language Type	float32 signed	float32 signed	float32 signed	float32 signed
Format	x float value to 17 d.p	y float value to 17 d.p	z float value to 17 d.p	w float value to 17 d.p
Example	0	-0.1936401	0	0.9810718
Validation	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1	Min: -1, Max: 1
Notes	Quaternion x value of the Distal bone of the finger.	Quaternion y value of the Distal bone of the finger.	Quaternion z value of the Distal bone of the finger.	Quaternion w value of the Distal bone of the finger.

animation/position OSC message structure

This message structure provides rotation values, suitable for character and hand rigs with 3 bones. The proximal and intermediate bones can also be assigned to rigs with only 2 bones per finger.

It is primarily used for determining the bone positioning for applications and animation tools that are based on fixed points in space for every tracked body part, in relation to the root bone of your character rig’s hands (e.g. wrist).

For most use-cases we recommend using data from the animation/rotation or animation/rotationWithMetacarpals OSC addresses instead.

NOTE: These positions are not retargeted and are based on a fixed internal hand model within Hand Engine, so further processing is required in your application to adjust the bone lengths for your character rig.

Animation Position Data OSC Message Format

Proximal Position	Timecode	Proximal Position X	Proximal Position Y	Proximal Position Z
OSC Argument Index	0	1	2	3
OSC type	integer	float	float	float
Language Type	int32 signed	float32 signed	float32 signed	float32 signed
Format	hhmmssfff	x position value to 17 d.p	y position value to 17 d.p	z position value to 17 d.p
Example	134255043	-0.07707334	-0.0002944469	0.0228914
Validation	Min: 0, Max: 2147483647
Notes	fff in the format represents a 3-digit frame number for the given second. INFO: Hand Engine supports up to 120FPS data for Pro Fidelity gloves, and 60FPS for Studio gloves.	X position value of the Proximal bone of the finger.	Y position value of the Proximal bone of the finger.	Z position value of the Proximal bone of the finger.

Intermediate Position	Intermediate Position X	Intermediate Position Y	Intermediate Position Z
OSC Argument Index	4	5	6
OSC type	float	float	float
Language Type	float32 signed	float32 signed	float32 signed
Format	x position value to 17 d.p	y position value to 17 d.p	z position value to 17 d.p
Example	-0.03520012	-0.000001430511	0
Validation
Notes	X position value of the Intermediate bone of the finger.	Y position value of the Intermediate bone of the finger.	Z position value of the Intermediate bone of the finger.

NOTE: The thumb has one fewer bone than the other fingers because thumbs do not have an intermediate bone.

Distal Position	Distal Position X	Distal Position Y	Distal Position Z
OSC Argument Index	7	8	9
OSC type	float	float	float
Language Type	float32 signed	float32 signed	float32 signed
Format	x position value to 17 d.p	y position value to 17 d.p	z position value to 17 d.p
Example	-0.02065659	-0.000000834465	0
Validation
Notes	X position value of the Distal bone of the finger.	Y position value of the Distal bone of the finger.	Z position value of the Distal bone of the finger.

Animation Slider All

The current glove state is expressed by Hand Engine as float values ranging from -1 to 1 for the bend of the bone and splay of the fingers of the end-user’s hand. It is possible to derive basic hand poses from this data in your receiving application by testing these against minimum and maximum ranges for each slider.

Animation Slider Types

The following terms and features are used when working with animation sliders:

The GloveRevision argument of the Animation Slider All OSC Message contains the string value of the glove revision which can be checked to determine whether or not to read the additional control rig slider values supported by that glove.

For glove revisions that don’t support Bend3 sliders on certain fingers, such as Studio Gloves, the OSC arguments for these will be sent as an integer value -2147483648 (the minimum supported value for int32 data type). These values should be interpreted as being null and discarded or ignored by your application.

Storing Ignored Slider Values

Since a value of 0 is considered a valid value when determining the state of a bone, your application may opt to store ignored bone values as NaN. Many strongly typed languages require integers to have a value (they can't be null) but this can cause issues if you try and perform arithmetic or logical operations on a NaN value. Programming languages have options for testing for NaN like the C# Double.IsNaN(Double) method which could be used when testing control rig slider data for a specific hand gesture.

StretchSense Studio Glove Sliders

The Studio Glove supports up to 12 control rig sliders but does not include values for the Distal bone bend or individual finger splay. Aggregate splay for the entire hand is available by reading the GlobalSplay OSC argument and ThumbSplay is also available. See Animation Slider Types.

StretchSense Pro Fidelity Glove Sliders

The Fidelity Glove supports the full 21 control rig sliders, including Distal bone and per-finger splay.
See Animation Slider Types.

Animation Slider All OSC Message Format

NOTE: In rare cases it’s possible to overdrive some of the sensors, creating negative values in the control rig sliders. For gloves with individual finger SPLAY, like the Fidelity glove, the SPLAY value can go into the negative range for some fingers. If using control rig sliders to animate a character or hand rig, you may need to apply smoothing and avoid using value clamping to avoid stuttering or jumping between certain hand poses if a bone spends extended time clamped at a 0 value.

NOTE: Some rig slider ranges are impossible for certain end-users to achieve due to their hand shape or disability, so if detecting gestures using control rig sliders, use a customizable threshold of 10-20% and test across a range of users to find a range that works well for your population.

INFO: Control rig slider ranges and value curves can vary between StretchSense glove revisions and sizes, despite the normalization performed by Hand Engine. Consider also testing your application gestures across a range of users, including snug and loose-fitting glove sizes. You may wish to further process control rig slider data, so the curve of the data is consistent when driving your application state if you need to support multiple glove types.

TIP: Use Bend1 and Bend2 control rig sliders for reliable finger bend across all glove types.

Performer Information

The following device OSC addresses have been implemented as part of Open SDK Core which contain device OSC messages for all performers configured in Hand Engine:

• /v1/performer/all

Performer OSC Message Format

Device Information

Each glove and dongle’s status can also be received to show important information like the BatteryLevel, Handedness and if both gloves are connected to the dongle.

The following device OSC addresses have been implemented as part of Open SDK Core which contain device OSC messages for all devices connected to Hand Engine:

• /v1/device/dongle/status - Status for each USB dongle connected to Hand Engine.
• /v1/performer/glove/status - Status for each glove that is connected to a performer in Hand Engine.

Glove Revision Types

The GloveRevision OSC Argument contains these possible values as string OSC types:

Device Dongle Status

/v1/device/dongle/status returns all the dongles connected to Hand Engine.

Device Dongle Status OSC Message Format

Performer Glove Status

/v1/performer/glove/status returns all gloves connected to staged performers. In later versions of the Open SDK an additional route will be added to get all gloves connected to Hand Engine, including gloves that are not currently assigned to a performer.

Performer Glove Status OSC Message Format

Retargeting

The diagram shown in the Open SDK Core API Diagram section shows accepted OSC message arguments for each OSC address when receiving animation data for one or more calibrated performers.

Retargeted animation data is sent via OSC as each glove data packet comes in from the hardware.

Retarget From JSON During Live Animation

The Animation Bone OSC address will apply a retargeting model based on a currently selected retargeting model of the respective hand. retargeting models are imported by Hand Engine as JSON files from C:\Users\{YOUR_USER}\AppData\Local\Programs\HandEngine-3.0.11-PRO\assets\retargeting where YOUR_USER is the name of your Windows user.

A user can select which retargeting model they want using a dropdown beside each hand in the Hand Engine main screen.

INFO: In a future version of Hand Engine, new custom retargeting models will be created by end users, developers or technical artists using StretchSense provided tools.

Open SDK Core API Diagram

These are the core OSC addresses needed for an application to receive glove data and provide a good user experience.

Download Open SDK UML API Diagram.drawio

OSC API Message Order of Operations

OSC messages may be received out of order, so all /v1/animation/* messages include a timecode OSC argument. This allows you to timecode sync the resulting messages if you are processing them as part of a larger motion capture system or need accuracy. For most live performance use-cases and for XR the messages should be processable by your application in a timely manner and any delay will be imperceivable by the end user, as long as messages are processed on the background thread.

Open SDK Implementation Guide

Preparing Hand Engine

Note that some Open SDK toggle settings may be unavailable in your version of Hand Engine, depending on your licence entitlements.

1. Open Hand Engine 3.1.2-Open-SDK-Beta or later.
2. Open the Hand Engine Settings Menu.
3. Under Open SDK, toggle on Enabled.

4. Close the settings menu. 5. Connect the USB dongle to your PC. 6. Turn on your gloves by pressing the power button on each glove once. 7. Wait for the gloves to start blinking blue at regular intervals. 8. For the left glove, select it from the dropdown menu. 9. If using a VRM character rig in your application, ensure the Retargeting Model is setdefault-retargeting-revg for Studio Gloves or default-retargeting-revf for Fidelity gloves. 10. Click Calibrate under the left glove.

11. Perform the calibration routine for each pose as prompted:

    12. Repeat steps 8-11 for the right-hand glove.

Preparing Your Application

1. Choose an OSC library that supports multi-threading for your desired programming language (see the OSC Libraries list below). In some procedural programming languages like C for embedded systems and microcontrollers, or plugins for 3D animation software only have a single thread, so real-time performance may be reduced.
2. Follow your OSC library instructions to setup a server listening on 0.0.0.0 (all addresses), port 9400.

Receiving Animation Rotation Data

Receiving Animation Rotation Data for 3-Bone Hands

1. Set your Retargeting Model for the left hand that matches the 3-bone character rig you will be applying the rotation data to (e.g. RAYNOS-chan.1.0.4). It will automatically show you the options available for your connected glove.

2. Bind to the server to listen for the /v1/animation/{performerId}/{handedness}/{fingerName}/rotation OSC address, substituting the following variables in the address:

3. performerId: 0 (the default/first performer)

4. handedness: 1 (left hand)
5. fingerName: Index
6. Alternately, if using an OpenXR compatible hand rig, bind to the server to listen for the /v1/animation/{performerId}/{handedness}/{fingerName}/rotationWithMetacarpals OSC address, substituting variables as above and using the HTC-VIVE-Wave-Hands retargeting model.

Storing Animation Rotation Data

If your OSC library supports processing incoming OSC messages on the background thread, setup handler functions to take these messages and store them in a way that is accessible by your main thread.

TIP: Using the background thread to process data will help avoid overloading the main rendering thread if lots of OSC messages come in at once. This avoids choppy or lagging animation as you perform hand movements in real-time using StretchSense gloves.

Animation Rotation Data Class List [Status: Recommended]

This is the preferred approach.

1. Create an immutable data class instance representing the Animation Rotation Data Message Format.
2. Set the class properties to represent the serialized data, including the performerId (used to later match the data back to the performer assigned to your animated character when the data is processed on the main thread). If you are planning to sync the data with other full body tracked data sources that use a timecode, you must also store the timecode OSC argument from the OSC message.
3. Create an instance of this class every time a message comes in and read each OSC argument according to the Animation Rotation Data Message Format table, storing the argument in the data class.
4. Store this data class instance using the handedness, fingerName and bone name as the key for later reference e.g. LeftThumbProximal.

Lookup table

This is an approach that works with functional programming languages or plugin scripting languages with simpler data types.

1. Create a struct, dictionary or similar multidimensional array, with the handedness and fingerName as the key for later reference.
2. Store the full data in an array with the data in the same order as the OSC message arguments, making sure to include the performerId and timecode.

Applying Animation Rotation Data

1. Ensure you have a method of mapping the character or hand rig bones to your received bone data. Store this as a lookup table/dictionary/struct to avoid searching your game or animation engine object hierarchy.

2. Every frame in your game engine or animation software’s animation loop, read the latest values from the stored animation data. 3. (optional) filter the data so it matches the current timecode if you are wanting the animation to sync with another timecode source. 4. For each bone in your character or hand rig, read the list of data classes containing each bones information and find the matching data class instance for the current bone. 5. Apply the data to the bone transform in the game or animation engine.

TIP: Some engines like Unity support efficient and parallel ways to apply data, like using the Unity jobs system to adjust Transform rotations in the background thread , so consider using this where possible. Note that these jobs may be run out of order or in parallel, so they are mainly intended for real-time applications and are perfect for XR apps where application frame rate is critical for a good user experience.

Timecode Syncing Animation

1. Use the same approach for Applying Animation Rotation Data, but on every frame only get data that matches the current timecode for each bone.
2. Apply all bone data to your character or hand rig, along with any extra motion capture data such as body or face tracking in the same frame to ensure everything syncs together.

NOTE: You may need powerful PC hardware to ensure all tracking sources can be processed at the desired frame rate, especially for higher rates like 120FPS.

WARNING: It can be hard to hit a 120FPS frame rate on standalone XR headsets with the timecode syncing approach, especially when performed on the main thread. Drop older frames behind the current frame / implement frame skipping with this approach, otherwise the animation of the character or hand rig will lag behind your physical movements.

Receiving Animation Position Data

The same approach to receiving animation rotation data can be applied to the position data for each bone. For some animation systems they rely on positions of each bone instead of rotations in order to calculate frame animation for a character rig.

NOTE: The position data is based on fixed model bone lengths that are the same regardless of what retargeting model has been selected in Hand Engine. The lengths do not change based on StretchSense glove size worn by the end-user, so you cannot infer the hand size or proportions from the animation positions received of each bone.

1. Use /v1/animation/{performerId}/{handedness}/{fingerName}/position instead of the animation rotation OSC address.
2. Process, store and apply the data using the same approach as the animation rotation guide. You may opt to store positional data in the same class, or postprocess the data into a final immutable object once both position and rotation data is received.

INFO: The GloveID from animation/slider/all or performer/glove/status contains information about the size of the glove which can be used to infer the size of the end-user's hand. You could use this to adjust character rig bone lengths, so the user’s hand is more accurately represented in XR apps. This is especially important in AR apps where the virtual representation of the user’s hand needs to align closely with their real-world hand size for immersion.

Receiving Control Rig Data

Hand Engine sends additional data about the current state of the hand in a simple format that can be used for adjusting the application’s state for the character or hand rig.

Gesture Recognition Using the Control Rig

There are a number of ways to use animation control rig data in your application or plugin:

XR Gestures

In XR applications, the control rig slider values have parity with gesture systems offered by other AR/VR frameworks and can drive the same functionality if a translation layer is created to map these to inputs. For example, the Unity XR Interaction System (XRI) v3.0 or higher supports Input Readers which allow the manual manipulation of the XRI state for selecting or activating objects (e.g. picking up or dropping XRGrabInteractables). While it is possible to integrate with XRI v2.5.x it requires several workarounds due to its reliance on Unity Input System Actions to drive application state, with no easy mechanism for simulating Input System Actions programmatically.

For a basic gesture recognition system within your application, it’s recommended to only detect up to 3 gestures on a single hand. We recommend the following single-handed gestures:

• Open hand - all sliders close to zero or a level with a relaxed hand pose
• Closed hand - Bend1 sliders at a threshold indicating all fingers are bent. Optionally also check the sliders for the thumb, but you will need to tweak these so it is comfortable for the user and so the gesture can be held reliably, especially when using the gesture to hold objects in the user's hand.
• Index point - Bend1 slider for index finger close to zero at a comfortable level. Other finger sliders for Bend1 should be similar to the Closed hand gesture.

To accommodate different users hand range of motion we recommend setting generous slider thresholds when detecting gestures as there may be some variance depending on the user’s calibration or the fit of their glove.

You will also need to debounce rapid changes in gestures in your application if gestures are too similar and wherever possible, give the detected gestures context by using a different gesture set while holding specific objects (e.g. a trigger pull gesture driven by Bend1 of the index finger that animates and activates a trigger while holding a pistol).

Multi-handed gestures can also be implemented as per the above method, but by checking both hands at once. This allows for a larger possible gesture space for driving behavior in your XR app.

TIP: A more advanced native gesture system is coming in future versions of Hand Engine that will be available in the Open SDK.

Desk Capture for Animation

In animation programs, a plugin could use the control rig sliders to automatically select a hand gesture from a library to add as a keyframe, allowing gestures to be animated quickly outside of a mocap stage in post-production and having the consistency and precision, no matter which artist is producing the animation.

Driving Animation Controllers or Visual Scripting Node Graphs

Unity and other animation software supports driving animations using a node graph-based approach. This allows technical artists and animations to have greater control over animation blending based on incoming data. Each control rig slider exposed from animation/slider/all can be mapped to a finger bone rotation to drive the overall blending of an animation.

Aggregating multiple Bend sliders together can be used to animate the bend of a finger, with the animation graph providing final adjustment to avoid issues with mesh penetration or variable bone lengths. This also allows the gloves to drive characters with less than 5 fingers.

Some examples of this include:

• Controlling the movements of anthropomorphic humanoid characters ears, tails etc.
• Animating characters with more than two arms or tentacles, where the arm bend of extra appendages is partially driven by the pinky/little and ring fingers.
• Driving walk cycles of quadrupedal animal characters.
• Animating feet containing 3, 4 of 5 phalanges.

Receiving Other Hand Engine Data

Other data can be received and handled from Hand Engine in a similar way to animation rotation data. This includes animation positional data (for bone lengths), dongle/glove data and performer data. Take the same approach to storing this data in data objects or a lookup table in the background thread, then apply this in your main thread.

Here are some ideas for how to use the data. We show an example of this in our Open SDK OSC sample in the StretchSense Plugin for Unity:

• Create a list of all the connected gloves in Hand Engine and visualize the handedness and current battery level. This can help a user see how much charge is left in each glove without needing to look at the Hand Engine application.
• If you’re receiving data for multiple performers, visualize a list of the performers from Hand Engine and show which gloves and dongles are connected to each. Show the glove and dongle connection status and battery level as above.
• Use the data from /v1/animation/slider/all to make a gesture recognition system for your application. Show an effect when the user makes a peace gesture or a thumbs up.

Open SDK Performance Considerations

• Running more than 1 performer in Hand Engine with all the Open SDK OSC addresses toggled on may negatively impact the performance of your app. Turn off the OSC addresses your application doesn’t need. In a future Open SDK update we will allow these to be toggled programatically so your application can configure itself on start.

• The most expensive OSC addresses to listen to are as follows due to the high rate of messages transmitted based on the StretchSense glove model used:

• animation/rotation (60-120Hz per hand, with 5 OSC messages per hand)

• animation/rotationWithMetacarpals (60-120Hz per hand, with 5 OSC messages per hand)
• animation/position (60-120Hz per hand, with 5 OSC messages per hand)
• animation/slider/all (60-120Hz per hand, with 1 OSC message per hand)

• StretchSense glove models transmit at different rates, also dependent on your PCs CPU load:

• Pro Fidelity: ~120Hz

• Studio: ~60Hz

OSC Libraries

• TypeScript - node-osc - OSC client/server implementation in NodeJS / TypeScript [Status: recommended]
• Python - python-osc - OSC client/server implementation in Python

• Unity C#

• virtual-cast/OscCore: A performance-oriented OSC library for Unity (github.com). This library avoids garbage collection related issues that other Unity C# libraries have. [Status: Recommended]

• ValdemarOrn/SharpOSC: Full implementation of Open Sound Control in C# .NET 3.5 (github.com) This is a lower-level library that supports more types and implements the full OSC spec but requires extra boilerplate.

Original Confluence page