-
Notifications
You must be signed in to change notification settings - Fork 148
Frequently Asked Questions
Frequently Asked Questions
Check out the wiki for detailed setup instructions.
Thanks for offering! The best place to look is the Issues page and look for issues labeled "help wanted". Generally any issue is up for grabs, but if it doesn't have a "help wanted" label, post to the issue asking first if it's ok to work on it so that you don't end up colliding with someone else's work. Similarly, if you start work on an issue, post to the issue that you are doing so and take the "help wanted" label off the issue. Feel free to post questions to the issues. Project owners get e-mailed when the issues change.
If the FAQ, the wiki, or the list of resolved issues fail to answer your question join us in the the PSMoveService Google Group. There are several people there who have experience debugging problems with the PSMoveService. With your help, we can make the troubleshooting wiki more extensive!
I would recommend starting a discussion on the PSMoveService Google Group first about the feature. It'll get more visibility there. And it's possible that someone might already have a solution for you. If after some discussion it sounds like there is some new work needed we'll have you file a new issue on the issues page. If it's not a request I can get to right away, I'll throw a "help wanted" label on it.
Always post bugs to the Issues page and apply the "bug" label. Ideally the more information a bug has the easier it is for us to fix. Depending on the kind of bug any of the following might be useful to include in the writeup and/or attach in a zip:
- Steps on what you did that led to the crash
- The config files in %appdata%\PSMoveService
- The log file for the service or the config tool
- Callstack
- Screenshot
- Video
With multi-cam support is it possible to set it up similar to the Lighthouse system for full 360 degree tracking?
Yes and no. The multicam calibration tool, older version shown here, allows you to compute the positions of multiple PS EYE cameras connected to your PC. When two cameras see a controller you can triangulate the position to get better depth-sensing. More cameras also give you better tracking area, which is a bit narrow for the PS EYE (75 degree FOV). However there are some definite limitations:
- The PS Eye camera has a resolution of 640x480, which effectively limits the max tracking distance to between 5-6 feet depending on lighting conditions.
- In practice, with multiple cameras attached to your PC, it's very easy to saturate the bandwidth on your usb bus. As a rule of thumb you should have no more than two cameras per root usb hub. You can tell how many usb root hubs you have in Windows by going to the Device Manager and looking under the "Universal Serial Bus controllers" section. Keep in mind that an Oculus tracker is also a camera that will eat up quite a bit of USB bandwidth as well. I once managed to get 5 cameras running at once on my PC but that involved a lot of shuffling around USB ports and experimentation.
- Each camera has its own set of lighting settings to be adjusted. Right now this process is pretty manual, see video here. So the more cameras you add the more of a configuration pain you're signing up for.
So basically all of this is to say, yes it possible to get full 360 degree tracking, but it's not a trivial amount of setup. Even once it works, it won't be anywhere near as good as the Vive. So make sure to calibrate your expectations accordingly.
Long story short: not without a substantial amount of additional work. See discussion for the challenges and other commercial solutions for solving large volume tracking.
Yes. Check out the PSMoveSteamVRBridge project on GitHub.
No. Perhaps you could help write it? I have a task for it here: https://github.com/cboulay/PSMoveService/issues/44