04.02 Get the SDK and Prepare Your Environment
Open manual menu
4.2 Get the SDK and Prepare Your Environment
The public Commercial Edition SDK can be downloaded directly. For a production project, fix the SDK tag, hardware SKU, and runtime environment before validating the minimum data path.
SDK Downloads
SDK v0.1.0
Review the directories, README files, and platform documentation for the fixed version.
Download the Complete SDK
Download the v0.1.0 Release archive containing prebuilt files, platform directories, and documentation.
SHA-256: a03d26bce54c41087e8c9ac44936e484f5fb2b0c31c007b739f191b85a776f17
Chinese Quick Start
Check the receivers, COM ports, and minimum data path first.
Development Environments
| Technology | Current SDK Environment |
|---|---|
| C++ | C++17, Windows COM ports; includes a reference implementation and C API. |
| Python | Python 3.9 or later on Windows; requires pyserial. |
| Unity | Unity 2022.3 LTS desktop projects; installed from a local package through Unity Package Manager. |
| Unreal Engine | Unreal Engine 5.6 on Win64; provided as a Runtime plugin. |
| ROS 2 | ROS 2 Humble on Linux; includes message and driver packages. |
Fix the Version for Production Projects
Use the v0.1.0 tag or a commit confirmed by both parties. Do not use the continuously changing main branch as the production baseline. Record the version, download date, and source.
Project Information Checklist
| Category | Information Required |
|---|---|
| Hardware | Planned SKU, quantity, Standard or Haptic Feedback Edition, and button-module requirements |
| Target Platform | Operating system, architecture, Unity, Unreal Engine, ROS 2, C++, or Python, including exact versions |
| Use Case | Capabilities to be read or controlled, number of users, and whether multiple glove pairs share the same environment |
| Data Requirements | Update behavior, coordinate or skeleton-processing requirements, and the input expected by the customer application |
| Acceptance Result | The minimum successful result and test environment |
| Delivery Management | Technical contact, project schedule, confidentiality, and distribution requirements |
Contact HIGVR
If you use another runtime environment, require a custom interface, or need project-specific deliverables, send the information above to service@higvr.com.
Next Step
Continue to 4.3 Development Integration Workflow.