Sudo launchctl load /Library/LaunchDaemons/. Sudo launchctl unload /Library/LaunchDaemons/ If the Leap daemon needs to be restarted, type in ~/Library/Application\ Support/Leap\ Motion/config.json Also, make sure that your firewall settings allow you to receive the Leap Motion data on port 6437. %AppData%\Roaming\Leap Motion\config.json In versions 1.2 and higher, you need to configure your Leap Motion config.json file and add "websockets_allow_remote": trueĪt the time of this writing, the file is stored in these locations: I just updated to Linux Mint 17 to solve the problem.
With version 2 of the Leap Motion software in Linux Mint 13, I was having trouble with dependencies when trying to run the Leap Motion visualizer. If you also use WebSockets to connect to the localhost IP address (127.0.0.1) at port 6437, you should now be receiving tracking data from both controllers. Use WebSockets to connect to that IP adress at port 6437. When you do this, you will see the IP address for the VM. Within your VM, set the network option to host-only and run the operating system's network interface configurator by typing in An easy way to retrieve data from both controllers is to create a web application - on your host computer - that uses the WebSocket protocol. The Leap Motion service/daemon uses TCP to send the tracking data to the 127.0.0.1 IP address (localhost) at port 6437. At this point, you should use Leap's diagnostic visualization software to make sure that each machine is receiving data from the devices. Before choosing what operating system to use, remember to read the current minimum system requirements for the Leap software.Īfter installing the Leap Motion controller software (version 1) on the VM and the host machine, connect the two Leap Motion controllers to your computer, and make sure that your VM takes control/connects to one of them. With my setup, I installed VMware Player with Linux Mint 13 (Maya) as the operating system. To get around this, you can set up a virtual machine (VM) on your computer (host).
At the moment, Leap Motion does not officially support using two or more Leap Motion controllers on the same computing device. This is a problem with VR, but can be a worse one with AR, if we can see the real world with full field of view but the virtual objects only with limited field of view, then those objects will be.