Common Problems
Port in use (Leap Motion/Ultraleap, VSeeFace)
By default, Intiface uses port 12345. Unfortunately, Leap Motion also uses port 12345 by default (and it also reserves 12346 through 12354 too). This means that if Leap Motion is running, RUMP will fail to start its built-in Intiface Engine. You'll also get errors if anything that tries to talk to or listen to Leap Motion is running (so even if you shut down Leap Motion, you'll still get errors if VNyan is still set to use Leap Motion).
In order to use RUMP at the same time as these other programs, you'll need to change the Intiface client port. To do this, in the RUMP folder, go to the folder /resources/config/
, open settings.json
, and change the "clientConnection" port from 12345 to something else. Leap Motion also reserves the next ten ports, so you'll need to set the new port to 12355 or higher to avoid errors. Note that this is the port that Intiface mods will need to connect to, so if you change this, you'll have to make sure to change the target port in mods too!
If you're getting this issue despite using Leap Motion, you may have some other software using port 12345. It's impossible to make a comprehensive list of everything that might conflict, but here's some things to look at if you're having this issue and don't want to just change the RUMP port:
- If you're using VSeeFace as part of your tracking setup, be aware that it always listens for Leap Motion, and there's no way to actually disable that. But if you're not actually using Leap Motion with it, you can get it to at least change to some other port. To do this, go into the VSeeFace options and turn on "Leap Motion V4 Compatibility (restart required)", then close and reopen VSeeFace. That'll make it stop hogging port 12345, at least.
- Wondershare, a program used for downloading files from your phone, also uses port 12345, and always runs unless you explicitly disable it.
- If you need further help troubleshooting this, Intiface has a troubleshooting page for port issues that gives some more information about how to track down and resolve a port conflict issue.