Unity: Cardboard VR doesnt work after updating to 2017.3.1f1 - unity3d

I am developing a VR game for Android but the VR mode doesnt start up. When I used 2017.3.0f0 everything works like a charm. The game starts in VR mode and I can rotate the camera. I just activated the Cardboard support in the Player Settings. I didnt have to enable the VR mode in any script. Now the game starts like a normal Android game with one camera and no gyroscope sensor support. Does anyone have a solution? Please help me. :(
Best regards Niklas Englmeier

currently I'm using Unity 2017.3.1f1 and works fine with Google VR SDK version 1.120.0, I know that the version 1.110.0 doesn't work, which version of SDK are you using? Did you place the MainCamera as child of an any GameObject and use GvrEditorEmulator? Unity 2017.3.1f1 using Google VR SDK 1.120.0

Related

Why is my unity app crashing when I start another one?

I'm trying to create a multiplayer scene with VR in Unity using a HTC Vive and steamVR. But I can't test my app on a single computer. I do a "build and run" then my app start but when I click on play in the unity interface, the built app crashes. I don't why. I observed that this phenomenon exists when I add the [CameraRig] prefab from the Steam VR plugin which is essential for the VR
Could you help me please ?
Thank you

Can SteamVR 2.2 be used to develop an app for Oculus Quest in Unity3D?

I am developing an app for Oculus Quest, but want to use the SteamVR 2.2 Input System instead of the Oculus OVR. More specifically, I want to use the SteamVR hands and SteamVR_Skeleton_Poser.
I tried just using the Interaction Example sample scene, but my hands are flickering all over the place! If I switch the renderModelprefab to the hand prefab on the "Hand" component, it stops the flickering, but then I get the errors of not having the renderModel class.
My Quest also only shows a blank screen when I build and run the sample!?
Is there a way to get SteamVR working for Oculus Quest?
If you want to deploy natively for oculus quest(android), this will not work. You can have your app running on a PC and streamrender to oculus quest while using steamvr.

Unity Steam VR launches incorrect

I've programmed a virtual reality game for the HTC Vive in Unity. I used Steam VR.
If I play the game on Unity, everything runs perfectly. It runs also perfectly if I build it. But if I copy my build to another computer, nothing's working.
It looks like this:top right corner
Does anyone no how to solve this?.
My Vive is setup correctly and other games are working just fine.
Thank you
Roman
Make sure before each build that OpenVR is set as first target in the player settings and not "None" (sometimes Unity changes it).
On the other computers, they should obviously have Steam and SteamVR installed
Since Steam workflow is to launch games from Steam Library,which launch SteamVR automaticly. make sure the SteamVR app is launched before launching your .exe.

Google Tango glitching in the build (Unity 5.6.1)

I've made an ARKit app that I was porting to Google Tango. The build works but the augmented object keeps tiling itself when it is visible on the mobile phone. Like this:
There aren't any errors popping up either. It just .. glitches like that.
I made an empty scene with some random object and that works perfectly fine. In the same project so the build settings are fine I think. And the "Tango Manager" and "Tango Camera" settings are similar on both the scenes.
Anyone face something like this? Or has any solution to this?
You can check out the app from this link: 4 Stroke Engine AR
So for those who are stuck at this (maybe), what solved it for me was to use Unity 5.3.1f to make the build.
I guess Tango SDK for Unity wasn't updated for 5.6. It isn't there for any version above that either.

Google Cardboard SDK demo head tracking inversed?

I upgraded my new Google Cardboard Unity game to the newer SDK, but now the head tracking is inversed:
The camera is upside down. Even the demo scene is the same way.
Has anyone been having the same issue? Thanks in advance!
It's a bug in v0.4.10. You can work around it in a few different ways:
Turn off Native Distortion Correction
Go back to v0.4.9
Use Unity 5