Forum Replies Created
2018-10-18 at 22:13 in reply to: Pimax4k+PSmoveService+PSmoveSteamBridge+Driver4VR freeze #5544
Is there any reason why you are not using PSMoveService for head tracking, or driver4vr for controller tracking?
Wouldn’t it be easier to just use PSMoveServices head tracking when you already got a working PSMove setup?
Getting a second Kinect for colour tracking would be really cool. My PC should be able to handle that, or I will make it able to handle it.
I am guessing that once you get a second Kinect to properly connect to a computer, implementing a simple algorithm to use the data of two Kinects together should be fairly straight forward; At least with colour tracking.
- This reply was modified 1 year, 7 months ago by MotoFckr9k.
I was told that and putting my feet further apart helped. It is still a pretty weird thing.
I guess you are right there. Putting a standard offset in and having the ability to change it might be enough. That would also make it less complicated for the end user as they can just leave the standard instead of having to do more calibration.
The question would of course be: How would we find out which offset we need? I guess if you can get coordinates of both the hmd and the controller, you could calculate their relative position using angles. The rift can even accurately show rotation so that could help too.
The touch controllers need an oculus rift to work. Or rather they send their rotational data to the rift. I don’t know if the tracking points of the controllers can light up regardless.
This is a common bug in VRChat. Try putting the feet further apart when calibrating. That always fixed it for me.
Apparently they removed the magnetometer in the newer versions of the psmove. Means that there isn’t anything preventing rotational drift. Though they probably removed it because the magnetometer was frequently fucked up by magnetic fields from speakers for example. (the oculus and its touch controllers are also strongly magnetic)