Start SteamVR to see if two additional controllers show up (they should be blinking if your hands are not in the field of view of the Leap Motion, solid otherwise).
If you experience frequent crashes of SteamVR on exit and this bothers you, uninstall my driver. I will try to fix this ASAP, but at the moment I have no clue why SteamVR is crashing.
You're seeing an early version of this software. I've got positional tracking established now as well as hand pose tracking. Some experimental mappings of hand gestures to triggers and buttons were added:
Trigger:
Grip:
Trackpad:
Menu buttons:
Swapped hands?
when SteamVR confuses the left and right controller hands (which will be indicated by little hand icons shown near the bottom of the displayed Wand controllers), simply cross your hands the first time you bring them into view after starting SteamVR. This reverses the hand assignment and can improve the gaming experience for example in Audioshield.
I am working on allowing to freely map gestures to buttons in the steamvr.vrsettings config file in your Steam\config folder. However note that the "leap_gestures" section is currently not parsed yet. It's merely a sign of things to come.
There are other gestures detected currently, but not mapped to buttons. If you want to try these out, click on the application "gesture_checker.exe" in the directory C:\Program Files (x86)\SteamVR Leap Motion driver\leap\bin\Win32
Then I also recommend that you simultaneously bring up your Leap Motion's settings and from there start the diagnostic visualizer (the windowed version, not the VR one). Press "v" once to switch it to headmount optimized mode.
Now pull both windows side by side and bring a hand into view. The command prompt running the gesture_checker program should output a series of numbers next to the names of the gestures. A "1.0" means confidential detection, a "0.0" means no detection.
You can practise some gestures this way and also cross-check your pose in the Leap Motion diagnostic visualizer against the detection confidence.
// Finger gestures (these would not throw your hand's orientation off much)
TriggerFinger, // bend your index finger as if pulling a trigger
LowerFist, // grab with your middle, ring, pinky fingers
Pinch, // pinch with your thumb and index fingers
Thumbpress, // point the thumb towards the direction of your pinky
// Hand gestures (these would significantly change the orientation of your hand)
FlippingTheBird, // flip someone off with your middle finger
ILY, // pinky and index finger extended, middle and ring bent
Victory, // V shape with your index, middle fingers, other fingers curled
FlatHandPalmUp, // flat hand, palm points upwards (relative to alignment of Leap!)
FlatHandPalmDown, // flat hand, palm points downwards (relative to alignment of Leap!)
FlatHandPalmAway, // flat hand, palm points away from self (relative to alignment of Leap!)
FlatHandPalmTowards, // flat hand, palm points towards self (relative to alignment of Leap!)
ThumbUp, // thumb points up, remaining fingers form a fist
ThumbInward, // thumb points towards the left for the right hand and vice versa
// Two handed gestures
Timeout, // both Hands form a T shape, signals a Timeout in sports
TouchpadAxisX, // Touchpad emulation: index finger of other hand points towards palm
TouchpadAxisY, // Touchpad emulation: index finger of other hand points towards palm I am seeing SteamVR Server crash on shutdown a lot. This could be related to my driver, but I have not yet found the root cause for the crash.
The Brookhaven experiment seems to steal focus from StreamVR, so that Steam does not get any position tracking. Clicking on the SteamVR window restores tracking, but mutes the audio on Brookhaven. Meh.
Some games work better when no grip angle is added to the controller pose, other games actually require a steep angle to be playable (Brookhaven, Audioshield). We may have to add a feature to chose the preferred default pose at runtime.
Tracking is not quite reliable to always detect my trigger gestures. I think we will have to integrate small handheld controllers like the Wiimote or the Playstation Move Navigation controller in the future.
I do not think I will be able to get animated hands into the 3D view, as the render model you can assign to each controller is mostly a static object. There are some JSON files to map joystick axes and triggers to animated parts of the displayed controller. But the fingers do not directly map to joystick axes directly and hence cannot be shown. Also not all games make use of SteamVR's internal controller visualization.
The solution and project files are for Visual Studio 2015.
Under "Property Manager" in Visual Studio, expand any of the configurations and find "Paths". Right click and select "Properties" and then "User Macros". Modify the paths to match your setup. InstallDir will be created, and will be configured as an external driver path for SteamVR.
You will probably want to build Release x86. You can also build x64. The post-build step will install the binaries and copy the resources to the configured InstallDir and register that path with SteamVR.
After building, the InstallDir should be a complete binary distribution. To use it:
...
"steamvr" : {
"activateMultipleDrivers" : true
}
}```After starting SteamVR, you should see controllers blinking in the status window until you move your hands into the field of view.
You can use "vrcmd" (with no arguments) to see a list of devices to verify things are working. use "vrcmd" to verify things are loading:
Driver leap : 2 displays
leap (Serial number leap0_lefthand)
leap (Serial number leap0_righthand)
...You can also use "vrcmd --pollposes" (followed by an index number to limit the output) to see if things are working.
The code in this distribution is distributed under the terms of the LICENSE file in the root directory.
The compiled driver and the install directory use the Leap Motion Orion SDK. Use subject to the terms of the Leap Motion SDK Agreement available at https://developer.leapmotion.com/sdk_agreement.