This is a project that I created as a starter for creating procedural meshes with the Leap Motion.
It requires the software you're using to support it. There's some games for it over on itch.io and the Leap Motion site, but I think the people who really benefit by having one are developers who are looking to experiment with hand presence. All that being said, the demos are really cool, it's fascinating to experience, but if you're a cash strapped individual who is thinking of buying one because it's going to take the place of your controllers in all your VR interactions, that's not what it's for and you may want to pass.... Unless you can find one on sale.
With the release of the Orion assets we're looking to rebuild a lot of these resources with better functionality and cleaner implementations from a developer point of view. Porting the old Widgets over isn't simple because the new assets are built on our LeapC API.
We just launched a roadmap survey; would really appreciate if you let us know how you'd like to use Widgets, as it helps to drive our roadmap: https://www.surveymonkey.com/r/Y3HKRXS
Have you tried RiftCat VRidge? I assume WebVR works fine with a Vive so it should work with VRidge. It's free to use in sessions of ~~>10~~ <10 minutes so there's no harm trying it. VRidge works (more or less) fine with Leap Motion.
I was able to validate hardware virtualization is enabled in my machine's bios. I was also able to validate via CPU ID that the AVX extension was supported and enabled in the physical machine.
Here is what I ended up with: https://www.screencast.com/t/SKhhCvWnK
The Orion V4 leapmotion service reads my LMC hardware info. The GUI flashes all green (connected) for 1 second and something errors out that isn't getting logged.
I did install the drivers from the installation folder which caused the LMC to go from a "camera" to a "usb device" listed as Leap Motion Controller. (See screenshot above)
This happens on both of my physical machines and in a pristine virtual machine.
I'm running out of ideas.
https://www.mediafire.com/?sbu6e468h8vbzq5
Here it is. It is just a .java file, so you can run it through jGrasp (tested) or eclipse (not sure about that). Right index finger draws when forward a bit, shows where the paintbrush is when farther back. Left index finger changes color when forward by moving up and down. I know this is a shitty explanation, and I will try to put up a video later showing exactly how it works.
Active would just have a little brick on the end. https://www.amazon.com/AmazonBasics-Active-Extension-Cable-Female/dp/B01L81WQ2O
For 2.0, you may not need it. Cable length without active parts can be 5 meters (16 feet).
I use this 15 Foot Cable from Cable Matters, it works quite nicely.
http://www.amazon.com/Leap-Motion-Developer-Bundle-VR-AZ/dp/B00SKWR4PE
This is the one I ordered, it comes with a mount. But does this bundle come with the longer usb and the updated tape so it can be used with the cv1.
Wireless USB transmitters exist, but A) they're expensive, B) they're finicky, and C) they're pretty slow and the latency would be way too high to be usable for most applications. I imagine latency would be the biggest killer.
The only way a wireless Leap Motion is happening(and to be usable) is with a whole new version of the hardware with a wireless radio that can handle the latency needs for the Leap. Different uses will obviously call for varying degrees of latency before the experience is muddled, so I don't know what type of wireless tech it'd take to achieve those needs. BT4.2? Wi-fi Direct? Something proprietary?