Does Google Cardboard SDK work with Unity 5?

0
votes

I have converted my working project from Unity into Unity 5 and now the stereoscopic display doesnt work.

It seems like the stereoscopic effect doesnt work. The display is split in the middle, and the shader is applied, but it seems like there is only once camera. Like there are no eye cameras.

The weirdest thing is that everything works perfectly in the editor, but when I run it on device it seems like the cameras are disabled.

I went through and tried everything in the "known issues" in Cardboard SDK Release Notes, but nothing works.

Has anyone succesfully run a Cardboard game on Unity 5?

2
c#unity3dgoogle-cardboard
Do you mean that there is only one view of the scene and it is broken into two pieces by the dividing line? – smd
Yes, that's what I mean – Martin Jasso
I answered you here: stackoverflow.com/questions/29211684/… – smd
try running the app and checking the logs via adb. I have made a Cardboard game on Unity 5, but I had another problems - the game randomly displayed textures or lightmaps instead of the stereo cameras. Otherwise everything worked fine. – K.L.

2 Answers

1
votes

Yes, I have done. Mine isn't big one but has major things that can be said to be using UNITY features as well. I cant predict your problem as such but Answer to this post is certainly YES.

0
votes

I don't think that anyone has posted this yet, but it appears that the SDK is currently broken in Unity 5.

From: Cardboard SDK Release Notes

Unity 5 rendering issues: As of Unity build 5.0.0f4, the following steps should be taken to fix or ameliorate any rendering issues, such as an all-black screen, flashing textures, or non-stereo views:

Enable the Development Build option in the Build dialog. This seems to fix various rendering glitches, like flashing textures.

The root cause of the rendering glitches is under analysis, with assistance from Unity.

I have also found that the app has rendering issues when it initially runs when you hit "Build and Run". Closing the app from the task switcher and restarting seems to resolve the issue.