Skip to content
This repository has been archived by the owner on May 3, 2021. It is now read-only.

Troubleshooting (Windows)

Jump to bottom
HipsterSloth edited this page Mar 29, 2017 · 18 revisions

(RiftCat/VRidge) PS move controller is oriented/positioned wrong in SteamVR

###VRidge setup notes from zelmon64

  1. Start and connect VRidge
  2. Start SteamVR
  3. Start PSMoveService
  4. Start calibration and ensure your HMD is looking forward
  5. Place the mat with the poses 4 and 5 to the front
  6. Finish and close calibration
  7. Restart SteamVR NOTE: You must restart SteamVR for the new alignment to take effect.

Following that should result in the forward directions being aligned.

PSMoveService isn't starting

Getting "EXCEPTION - PSMoveService - boost::interprocess::intermodule_singleton initialization failed" in the logs

You might also be missing a windows event that boost needs to compute system up-time, see boost issue #12137 for details.

  1. Reboot your machine
  2. Open zadig and reinstall the libusb driver for the cameras if the libusb driver is no longer associated
  3. Try re-running the service

You might be running CCleaner. If so:

  1. Go to C:\Users\<username>\AppData\Roaming and delete the PSMoveService folder (backup/rename first)
  2. Go to C:\ProgramData\boost_interprocess and delete everything in there
  3. Open CCleaner, go to Options, Exclude, Add, and then under Driver or Folder enter C:\ProgramData\boost_interprocess\
  4. Reboot
  5. Open zadig and reinstall the libusb driver for the cameras if the libusb driver is no longer associated
  6. Try re-running the service

Controller isn't showing up at all

  1. Make sure the controller is actually turned on (red light at the bottom of the controller is on)
  • If not, press the PS button. The red light should blink and then go solid
  1. Make sure the video feed is working
  • Open the "Test Video Feed" option in "Tracker Settings" menu in PSMoveConfigTool.exe
  1. Make sure the tracking is stable
  • Open the "Test Tracking" option in the "Tracker Settings" menu in PSMoveConfigTool.exe

Phantom controllers showing up in controller list (Win10)

In Win10, make sure to used the windows default bluetooth driver for your bluetooth adapter, rather than the driver that comes with the adapter. Some have reported issues with phantom controller listings show up (2 controllers listed when only one is connected). Reverting to the windows default bluetooth driver fixed this issue for them.

Crash on connecting PS Move Controller

In some instances the controller can get into a weird pairing state in Win10. Try the following from Issue #173:

  1. Connect the PS Move to a PS3 or PS4 or another PC again
  2. Remove everything motion controller entry from the Bluetooth list and the device manager in Win10
  3. Deleted the controller profiles from the %appdata%/PSMoveService folder
  4. Used different USB Ports directly from the backside of the computer (no usb hubs in-between) when re-pairing

Controller position is noisy in SteamVR

NOTE: If you only have one PS3EYE you will get some jitter in the direction away from the camera. This can be addressed by adding a second camera so that the system can triangulate the controller position. If you are having wild jitter in all directions, then follow these steps.

  1. Verify that the instability is coming from the tracking
  • Open the "Test Tracking" option in the "Tracker Settings" menu in PSMoveConfigTool.exe
  1. Make sure your color filters are appropriate for your current lighting environment
  1. If you are next to a window make sure there aren't any bright spots in the video frame.

Cameras aren't showing up using libusb driver

If you see "libusb: error [winusbx_claim_interface] could not access interface 0: [87] The parameter is incorrect." in the PSMoveService log window try these steps. This typically occurs the very first time you try running the service.

  1. Open Zadig usb driver utility
  2. From the options menu launch select "List all devices"
  3. From the device list drop down select "USB Camera-B4.09.24.1 (Interface 0)"
  4. From the driver drop down select "libusbk", NOT "libusb-win32"
  5. Install "libusbk".
  6. Reselect the camera and then select "libusb-win32"
  7. Install "libusb-win32"
  8. It may hang. If so just kill and restart Zadig, then reinstall the libusb-win32 driver.
  9. Run test_camera.exe to see if that fixed the issue.

General weird camera behavior (clean camera driver reinstall)

Some people have reported issues where PSMoveService.exe will start but then out shortly after trying to open the tracking cameras. This typically seems to either be an issue with windows getting confused about which usb driver to use for the camera or there being too many usb devices on a given hub. In one case an XBox 360 controller on the same hub seemed to interfere with the camera.

  1. First try moving the PS3Eye to a different USB hub, then try re-running PSMoveService.exe
  2. If that doesn't help you night need to clean out old driver/usb port mappings using USBDeview from NirSoft
  3. Unplug the PS3Eye camera
  4. Open USBDeview as admininistrator
  5. Sort the devices by the "VendorID" colomn.
  6. Look for VendorID 1415 (Nam Tai E&E Products Ltd), ProductID 2000 (PS3Eye)
  7. Peruse the same tips Oculus provides for not saturating their cameras.

  1. Select all of the VID 1415/PID 2000 entries then right click and select "Uninstall Selected Devices"

  1. Close USBDeview and plug the PS3Eye camera back in
  2. Re-open USBDeview, sort by VendorID again and look for the 1415 vendor ID

  1. There should only be 4 entries now and the service names should be "usbccgp", "WinUSB", and "usbaudio". These are the default Windows drivers.
  2. Open Zadig usb driver utility
  3. From the options menu launch select "List all devices"
  4. From the device list drop down select "USB Camera-B4.09.24.1 (Interface 0)"
  5. From the driver drop down select "libusb-win32 (v 1.2.6.0)"

  1. Click the Install Driver option
  2. There should be a few second delay and then it should say "driver installed successfully"
  3. Go back to USBDeview and look at the "Service Name" entry for "USB Camera-B4.09.24.1 (Interface 0)". It should now say "libusb0" and not "WinUSB".

  1. Finally, try re-running PSMoveService.exe and then launching 'PSMoveConfigTool.exe' to test the video feed.

Controller isn't pairing to PC (Win 10, Any bluetooth adapter)

  1. If you're having trouble pairing, calibrating, etc., charge the PSMove controller fully (overnight) before attempting again.
  2. Try pairing them on a PS3, Mac, or Linux. If it won't pair there then the problem is the controllers.
  3. Some bluetooth dongles seem incompatible. I have an ASUS BT-400 that works for me.

Help! A solution for my problem isn't listed!

Join us in the the PSMoveService Google Group to ask your question. There are several people there who have experience debugging problems with the PSMoveService. With your help, we can make the troubleshooting wiki more extensive!

Clone this wiki locally