-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Update] Support Tundra Tracker with timing quirks
Support the Tundra Tracker (Haptic Tundrakes?) via… 1. Microseconds instead of milliseconds for "triggerHapticPulse()" Scale up from milliseconds via a time-based multiplier for the legacy, deprecated "triggerHapticPulse()" method. Set Tundra Trackers back to a multiplier of 1.0 elsewhere, matching the behavior of Vive Trackers. This could be replaced with support for the IVRInput system instead of using the deprecated triggerHapticPulse() function. 2. Limit pulse length to 4000 µs / 4 ms Tundra Trackers have a limit of around 4000 µs (4 ms) per pulse, so the update loop must run more frequently to stay within that maximum duration for a single pulse. Queue a time-based forced pulse and warn once if attempting to send a haptic pulse exceeding the max pulse length for the tracker (if set). Usually this shouldn't happen - strength values of up to 100% would result in pulses scaled up to the pulse limit. However, there are two notable cases: A. "Identify" button triggers a 500 ms pulse B. Velocity calculation can result in a strength that exceeds 1.0 This should (hopefully) match the Vive Tracker behavior. NOTE: Velocity calculation currently appears to do almost nothing with Tundra Trackers unless the multiplier is set to around 50, which then breaks normal Proximity and Identify-button haptics pulses. Tested setup: * 4x pancake vibration motors Thinner than LRAs shipped with Tundra IO Boards, fits in stock base * 4x Tundra Trackers Left/right foot, waist, chest * Default multiplier, default strengths Also tested Velocity strength set to 60% - 100% * Proximity and Velocity set to "Linear" pattern "Throb" works too, but feels a bit weak
- Loading branch information
1 parent
0d5e8b7
commit 1a6749f
Showing
3 changed files
with
108 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters