04.03 Unity, Unreal, ROS, C++, and Python Integration Workflow

Open manual menu

Business Customer / Developer Integration Manual
4.3 Unity, Unreal, ROS, C++, and Python Integration Workflow

4.3 Unity, Unreal, ROS 2, C++, and Python Integration Workflow

Run a minimum example from a fixed version before moving to the target technology stack. For complete commands, APIs, and sample code, use the corresponding GitHub v0.1.0 directory.

Implementation Process

Download a fixed version.
Use the v0.1.0 tag or ZIP instead of depending directly on the main branch.
Verify basic communication.
Run the Python example or protocol validation first to confirm the receivers, COM ports, and glove data.
Select the target technology stack.
Follow the README in the corresponding directory to configure the environment and run its minimum example.
Integrate the customer application.
Implement data mapping, interaction logic, multi-device management, and error handling.
Complete acceptance.
Archive the version baseline, test steps, results, and evidence.

Technology Entry Points

Unity

Unity 2022.3 LTS desktop projects and a local UPM package.

Open Unity Directory

Unreal Engine

Unreal Engine 5.6 Win64 Runtime plugin.

Open Unreal Directory

ROS 2

ROS 2 Humble messages and driver.

Open ROS 2 Directory

C++

C++17 Windows COM-port reference implementation and C API.

Open C++ Directory

Python

Python 3.9 or later, including dual-glove and haptic examples.

Open Python Directory

Avoid Mixing Versions and Capabilities

Do not mix different tags, commits, or project-specific deliveries. The presence of an interface in the SDK does not mean the current SKU includes the corresponding hardware capability. Motion data, haptic feedback, and button capabilities are defined by the order.

Next Step

Continue to 4.4 Project Validation, Delivery, and Version Management.