Forum Replies Created
-
Posts
-
I face the same issues with Kinect 360 and PS Move. Positional offset and controllers swapping sides or also having a positional offset. Sorry Greg, but this is far from “no complex configuration”. I am not atech noob and I have been working on it for more than a month and I still have no working controller tracking.
I appreciate your work and your quick responses to questions in this forum. But I am really disappointed, because the software does not perform as announced.Have you done the room setup in Steam VR? This improved the offset for me.
And be aware that you must keep a distance of 1,5m from the sensor in order to be tracked.Maybe that helps…
I also have many issues and this is one of them. Have you tried to do the room setup in Steam VR? This improved it for me, though still not being perfect.
Happens to me as well. But only if I use the Move Controllers. Once I turn them off everything is fine. This started with the latest update.
I finally found the solution. I replaced the Kinect to a higher position. And further away. It seems that Kinect needs like 1,5m distance to track.
In The Lab positioning is also fucked up. The controllers appear behind me to the right and below the ground surface.
And it’s becoming weirder.
When I open the steam menu in Steam VR Home the position and orientation is alright. When I opened Google Erath it worked as well. Just in the Steam VR Homescreen everything is fucked up.
Any idea?This fixed the pointing direction. But the virtual controllers are still located behind my back in Steam VR Home.
I guess it is related to Kinect not working properly. I can’t calibrate because when performing step 1 of the calibration process it tells me that Kinect isn’t tracking.Is the touchpad emulation of the Move Controllers better than the thumbsticks on whatever 5$ vr gamepad?
It’s weird. It always fails at “Daydream Device (&1594dd15&) – error when registering for notifications: Unreachable”
I doubt that it is a Windows issue since you aren’t having this problem. Maybe I’ll just buy 2 5$ controllers and see if they work.
I re-paired the controller and the logs look better. But I still can’t use it. The preview doesn’t show any reaction.
As I have no Kinect yet, but a Leap Motion, I set the tracking to Leap Motion and assigned the daydream controller to the left controller.
Hi!
I face similar issues with my (original) Daydream controller.
Today I installed the latest Driver4VR software.
In Windows 10 Bluetooth menu it is listed as paired (not connected!). Driver4VR recognizes it, but none of it’s input. The preview tab looks like in the image ecou2508 posted before.
Shouldn’t the controller’s button input be recognized without connecting the Kinect?
I also installed AntiMicro to see if the Daydream controller is recognized. Unfortunately it can’t see it at all.
It seems that for some reason the computer doesn’t want to accept the Daydream controller. Any idea how to fix this?Next week I will get my Kinect and would be happy to use it with the daydream controller.