From e7a07863eed9a25cc1655a10da9dd3879580c557 Mon Sep 17 00:00:00 2001 From: Mamadou Babaei Date: Tue, 24 Feb 2026 10:26:41 +0100 Subject: [PATCH] add a caution alert regarding calling send haptics repeatedly in rapid succession --- .../sghapticscomponent/README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Handbook/src/advanced-topics/roll-your-own-hand-manipulation-system/sghapticscomponent/README.md b/Handbook/src/advanced-topics/roll-your-own-hand-manipulation-system/sghapticscomponent/README.md index d5dea25b..3f5fdf92 100644 --- a/Handbook/src/advanced-topics/roll-your-own-hand-manipulation-system/sghapticscomponent/README.md +++ b/Handbook/src/advanced-topics/roll-your-own-hand-manipulation-system/sghapticscomponent/README.md @@ -250,6 +250,23 @@ The component works using a **queue-based system**: - `true`: Indicates message has been successfully sent to SenseCom. - `false`: Failed to send haptics. +> [!CAUTION] +> Avoid calling `Send Haptics` repeatedly in rapid succession. +> +> For optimal performance, queue all required haptic commands first +> (Force-Feedback, Vibro, Wrist, etc.), then call `Send Haptics` +> **once per logical update cycle**. +> +> Continuously queueing commands and flushing them every frame (or multiple +> times per frame) increases device communication frequency and computational +> overhead. It may also cause Bluetooth instability and, in extreme cases, lead +> to the glove disconnecting. +> +> Instead, batch multiple haptic updates together and send them in a single +> compiled message whenever possible. This reduces processing cost, lowers +> communication load, and results in more stable and efficient haptic +> performance. + ### Supports Custom Waveform Checks whether the glove supports **custom waveform vibration** at a specific location.