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
Guido Sanchez edited this page Jun 27, 2016 · 18 revisions

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

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. Reselect the camera and then install "libusb-win32" overtop of of "libusbk"
  6. It may hang. If so just restart and then reinstall the libusb-win32 driver. Once I did that it worked perfectly.

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)

  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.

Controller isn't pairing to PC (Win 10, ASUS USB-BT 400 adapter)

  1. Download the driver for the asus usb-bt 400 directly from their site instead to using the driver from their CD
  2. Disable Win 10 Disable Driver Signature Verification/Enforcement
  3. Temporarily disable any anti-virus to make sure it's not interfering
Clone this wiki locally