Gvr-unity-sdk: Unable to see/use 6DoF Controllers in or outside of app.

[sebastianherscher]

Summary:

Using the 6DoF controller development kit, I am unable to see or use the controllers in the Daydream menu or inside the provided Unity demo scene. I've followed all instructions listed on g.co/6dofsetup and have successfully paired the controllers. I still see the 3DoF controller in all apps and in the outside menu.

Found using:

• Google VR SDK version: v1.180.0
• Unity version: 2018.2.14f1
• Viewer manufacturer & model: Google Lenovo Mirage Solo + 6DoF Development Controllers

Steps to reproduce the issue:

1. Build Hello6DoFControllers app to Mirage Solo.
2. Connect 6DoF faceplate and pair 6DoF controllers.
3. Launch Hello6DoFControllers app.

Workarounds: None so far.

Additional comments: I realize this may not be the most correct avenue for feedback for this (may be a controller/OS issue instead of the Unity SDK), but the FAQ and Troubleshooting sections of the 6DoF controllers is still pretty bare. Thank you for understanding!

[jadware]

same issue

note that the 3d models for the 6dof controllers are present in the Beta/Models folder but not referenced anywhere in the sample scene or code

[sousv]

I'm also experiencing this issue. I tried power cycling, re-pairing both controllers, edited the Android Manifest file a few times. Nothing I do seems to have any affect on the headset detecting the 6dof controllers.

[jadware]

@sousv @sebastianherscher are you able to get the 6dof controllers working in anything, even non-unity? I cannot get them to appear anywhere.

[sousv]

@jadware No I haven't seen it working on the daydream menu either. Has anyone tried to use the NDK to install the 6dof controller app? https://developers.google.com/vr/develop/experimental/6dof-getting-started-android-ndk

I was going to try that but it'll take some time and I'm a bit busy. Hopefully someone responds to this thread with a simple solution.

[jadware]

I had difficulty compiling the ndk examples with the provided project file, will try again tonight

[sousv]

@jadware I compiled NDK example successfully just now and it still doesn't work. I'm gonna have to put this on hold. I think there's a critical step that's missing like paring the 6-dof controllers to the headset. Hopefully someone updates us if they get it to work successfully.

[jadware]

@sousv Ahh ok, thanks for letting me know
Yes, it does seem like there's an OS or daydream service update that's still needed

I'll post updates once I kick things around a bit

[sniejadlik]

I am seeing the same issue, have followed the guide exactly and even reinstalled the google vr for unity package completely. No luck seeing either of the 6dof controller, just the standard daydream clicker.

[sniejadlik]

@jadware I compiled NDK example successfully just now and it still doesn't work. I'm gonna have to put this on hold. I think there's a critical step that's missing like paring the 6-dof controllers to the headset. Hopefully someone updates us if they get it to work successfully.

The controllers are showing as paired. They get paired to the faceplate not the headset. I was even able to pair "google shaker" to the device which I am assuming was the code name for these but it didn't do anything. There has to be some device update that is needed or something.

[sousv]

I contacted google about this issue with a bug report yesterday. They told me they found the issue and are working on a fix. They also told me they'll update me as soon as a fix is rolled out. I was able to reach them at [email protected]

[sniejadlik]

@sousv Thanks! Hopefully they roll it out soon as I am assuming this is affecting everyone that has the devices.

[CubicVR]

We contacted through [email protected] as well. Initially we didn't have the latest OTA (which is 181126, we were stuck at an October build) and they pushed a force update from their side which worked and we updated. However it did not solve the issue. This morning they asked for a bug report which we provided. Waiting for a response now...

[NidhiRathi1]

Thank you for bringing this issue to our attention. We are working on a fix now, and should have a status update and a new release next week.

[rusmaxham]

This is a VR Services level issue that will be resolved very soon with an auto-pushed update to VR Services. We will comment and close this issue when the update is pushed.

[NidhiRathi1]

A new build is available to resolve the pairing issue. Please update your device and ensure it is on OVR1.181126.005.

Updating your device:

• Devices should update automatically
• You can force update through Settings > System > System Update
• Device must be on wifi and have minimum 40% battery charge for update to start

Checking build number:

• Settings > System > About Device > Build Number

[CubicVR]

It works! Thank you all at Google VR.

[jadware]

for me as well, works great!

[sniejadlik]

Worked flawlessly, thank you!