add a caution alert regarding calling send haptics repeatedly in rapid succession
This commit is contained in:
+17
@@ -250,6 +250,23 @@ The component works using a **queue-based system**:
|
|||||||
- `true`: Indicates message has been successfully sent to SenseCom.
|
- `true`: Indicates message has been successfully sent to SenseCom.
|
||||||
- `false`: Failed to send haptics.
|
- `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
|
### Supports Custom Waveform
|
||||||
|
|
||||||
Checks whether the glove supports **custom waveform vibration** at a specific location.
|
Checks whether the glove supports **custom waveform vibration** at a specific location.
|
||||||
|
|||||||
Reference in New Issue
Block a user