Skip to content
Hapbeat devtools
EN

Installation Requirements

The Hapbeat Unity SDK can be installed directly from a Git URL via the Unity Package Manager (UPM). No .unitypackage download or manual copy is required.

Requirements

Section titled “Requirements”
  • Unity 2022.3 LTS or later (tested on Unity 6000.3.12f1)
  • Git installed on your PC and available on PATH (required because Unity runs git clone internally)
  • A network environment where Wi-Fi UDP broadcast can reach devices on the same network
  • Active Input Handling: “Both” / “Old” / “Input System Package” — all are supported

Installation

Section titled “Installation”

1. Add via Git URL in Package Manager

Section titled “1. Add via Git URL in Package Manager”
  1. In Unity Editor, open Window → Package Manager
  2. Click + in the top-left → Install package from git URL...
  3. Paste the following URL and click Add:
https://github.com/Hapbeat/hapbeat-unity-sdk.git

To pin a specific version, append a tag:

https://github.com/Hapbeat/hapbeat-unity-sdk.git#v0.1.0

2. Updating

Section titled “2. Updating”
  • Package Manager → Select Hapbeat SDK → Click Update if shown in the right panel
  • For tag-pinned URLs: edit #vX.Y.Z in Packages/manifest.json and save — Unity auto-reimports

3. Create the SDK Folder (optional, convenient on first setup)

Section titled “3. Create the SDK Folder (optional, convenient on first setup)”

Run Hapbeat → Setup → Create HapbeatSDK Folder to generate:

Assets/HapbeatSDK/
  Kits/        ← Haptic waveforms and manifest.json (Studio integration target)
  Scenes/      ← Generated scenes
  EventMaps/   ← EventMap.asset

This is generated automatically when using the sample Build menu, so you rarely need to run it explicitly.

Samples

Section titled “Samples”

Select Hapbeat SDK in Package Manager → Import from the Samples tab in the right panel:

SampleContentsRequirements
Basic ExampleMinimal combination of Trigger × 3 + Helper + Dispatcher + StatusOverlay. Test with Space/R/F/S/C keysDevice + Studio or Helper running
ShowcaseFull SDK feature showcase with 5 zones (Bowling / Door / Fishing / Stream Console / Target Range). Works with keyboard and mouse — no XR requiredSame
XR HelpersFilters for XR Interaction Toolkit integration (XRGrabFilter / XRSocketFilter)Only for projects with XRI installed

Samples are unpacked to Assets/Samples/Hapbeat SDK/<version>/<sample>/. Open the scene (Scenes/*.unity) immediately after import and hit Play to verify — no additional build steps required.

Verifying the Setup

Section titled “Verifying the Setup”
  1. Launch Hapbeat Studio or Hapbeat Helper and confirm your device appears online
  2. In Unity, open Assets/HapbeatSDK/Scenes/BasicExample.unity
  3. Enter Play mode
  4. Press Space for a one-shot stream, F for a Command (Fire) — if the device vibrates, you’re set (R = Stream loop, S = Stop all, C = Ping)

If the UI shows Pong: RTT=...ms, the SDK ↔ device connection is established.

Build Notes

Section titled “Build Notes”
  • iOS / Android: Works out of the box (UDP socket available)
  • Quest (Android): INTERNET permission is automatically added to the manifest
  • WebGL: UDP sockets are not available. Hapbeat communication does not work in WebGL builds

Troubleshooting

Section titled “Troubleshooting”
SymptomSolution
Pasting the URL in Package Manager does nothingVerify Git is on PATH (git --version must work from the command line)
Hapbeat → Build Samples → ... does not appearCheck that the corresponding Sample has been imported. Re-importing an older Sample applies the latest Editor scripts
No haptic feedback during PlayCheck that Studio/Helper is running and the device is online; verify that the Group setting in HapbeatConfig matches the device
Space / R / F keys have no effectCheck Edit → Project Settings → Player → Active Input Handling — if set to Input Manager (Old) only, change it to Both or Input System Package (Unity 6 default is Both)
Compile errors like 'InputSystem' does not existA stale import may remain. Delete the relevant Sample under Assets/Samples/Hapbeat SDK/ and re-import

Next Steps

Section titled “Next Steps”