You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2021. It is now read-only.
I'm having hell getting this working - I'm finding I can't get far into the setup guide as running psmovepair.exe is not working as expected. I have a move controller connected via the USB cable to a USB 3.0 port (also tried USB 2.0) and Windows recognises that the device is there, however running psmovepair.exe fails immediately, telling me that the Magnetometer is not yet calibrated and that my non-USB PSMove controller is being ignored. I'm not sure why the setup process is recognising the controllers are there (it clearly does, it gives me their mac address), but doesn't think they are USB?
The text was updated successfully, but these errors were encountered:
For now, use psmovepair.exe that you build from thp/psmoveapi repo. It's more up-to-date than what's here. That repo has some features that my fork (cboulay/psmoveapi) does not -- like a better psmovepair -- but it also has worse tracking. I don't have time to keep my fork up to date with the upstream repo while still maintaining my tracking changes. Sorry for the difficulty.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
I'm having hell getting this working - I'm finding I can't get far into the setup guide as running psmovepair.exe is not working as expected. I have a move controller connected via the USB cable to a USB 3.0 port (also tried USB 2.0) and Windows recognises that the device is there, however running psmovepair.exe fails immediately, telling me that the Magnetometer is not yet calibrated and that my non-USB PSMove controller is being ignored. I'm not sure why the setup process is recognising the controllers are there (it clearly does, it gives me their mac address), but doesn't think they are USB?
The text was updated successfully, but these errors were encountered: