I've been working with the Google VR SDK for Unity but I've run in to some weird issues with adding a reticle, specifically using the GoogleVR prefab GvrReticle. Up until a couple weeks ago the reticle was lined up and looking fine in my projects but now I can't seem to get the reticle to work properly, both installed on device(iPhone or Android) or in the Unity preview mode. It appears slightly misaligned so that when you wear the device in it's headset you will get two dots instead of one reticle.
Even in a sample project that just includes the SDK and the barebones necessary for a reticle the result is the same(a double-vision reticle).
Has anyone else run into this problem or would know what might possibly be causing it?
I'm using the latest versions Unity(5.4.1f1) and googleVR(unity sdk v0.9.1) and I've tried doing builds on both PC and Mac with seemingly the same results. I've uploaded a sample project here: https://dl.dropboxusercontent.com/u/64965870/ReticleSample.zip
Had the same problem, solved with the new GoogleVR SDK Ver 1.10 (https://github.com/googlevr/gvr-unity-sdk)
try and replacing the current SDK with the newest, it's pretty easy to replace.
Related
I am new to unity 2021.2.10f and I have become stuck on getting a simple app working on a tablet /real hardware.
I am using unity 2021.2.10f my project is simply the built in
"3D Sample Scene(URP)" I did not change anything to it except added an icon to it (so I can see it in the tablet menu when it is installed on the android tablet)- the unity project can easily be
recreated-I could not upload it since it the project was large (more than 350MB) for my internet connection.
This is how the the unity project looks on my computer
enter image description here
When I compile this to an android apk I just get a pink/magenta screen (as shown below).
enter image description here
I also get the message below from the tablet.
enter image description here
After googling around for an answer I found out
this pink/magenta screen means it is a shader problem.After more googling for an answer it was recommended to tick or untick to reset the
~"Auto Graphic API" as a fix-but this did not work for me.
I also changed the color space from Gamma to linear-and again this did not work for me. My tablet is a Maitai MT107.
So my question is -how do I get this to work?
In previous years and using older versions of unity I have been able to get unity made apps to work perfectly on several different tablets (though not an MT-107).
Also the compiled version of this project does not
work in latest version of Bluestacks on Windows 10-it shows a blank black screen instead of a pink screen-may be it is related to that-
maybe if I can get it to work with the Bluestacks emulator it will work on real hardware-but I do not know what exactly the problem is that is stopping the app working on the MT107.
I figured it out using Shingo's comments.
My tablet only supports GL ES2 because
I ran CPU-Z to find that out.
I made a simple test program (just the default empty project with the blue sky) with
unity 2020 (NOT the latest version) when GL ES 2 is selected.
Here is the gotcha-it looks like ES2 was removed in the latest version
of Unity 2021.2.10f-but it can be selected in the following way.
I started off by making my test program in unity 2020 save and closed the project. I selected GLES 2, as shown below,in this older version of unity (NOT using "Auto Graphic API")
Then I re-opened it, this makes unity convert the project so it
works in the latest version of unity 2021.2.10f-then I can see the GLES 2 (depreciated) appears in the
latest version of Unity. The GLES2 option circled in blue shown below
-GLES 2 support does not appear in the project if the project is not converted from the older version of unity.
Now I can use the latest version of unity to use with a tablet that supports
only GLES 2 by adding to the empty test program to eventually write my complete program.
I am happy I can still use my tablet with unity because: it wasn't cheap to
buy and bought this year, if it works on this tablet it will work on a GLES3 tablet (because of backwards compatiability).
I am using Unity 2019.3.15f1 with the MRTK 2.4.0 for developing an augmented reality app on the HoloLens 2. Unfortunately, the stereoscopic rendering is not working correctly. There is a mismatch between the images rendered for the right and the left eye. You see two images of the scene, running the app on the HoloLens. It doesn`t matter if I am using the Remote Player or ruining a builded app on the HoloLens. In both cases there are two not matching rendered images for both eyes. The HoloLens is calibrated. Other Apps from the microsoft store, or the "Homemenu" at the HoloLens have no mismatch of the images. But if I am running MRTK-example scenes on my HoloLens 2 there is also a dismatch between the rendered images for both eyes.
Does anyone had troubles with the same issue and can provide some ideas about a solution how the images can be matched correctly for both eyes?
It seems like something went wrong in your Unity project setting, it is recommended to double-check the XR Setting to troubleshoot. For XR SDK, please follow this link: Getting started with MRTK and XR SDK. For Legacy XR, have a look at Legacy XR
Besides, we always recommend the latest Unity LTS (Long Term Support) and MRTK as the best version so that we can avoid some known issue, and the current recommendation is to use Unity 2019.4.20f1 and Mixed Reality Toolkit v2.5.4.
Unity Version: Unity 2019.3.9f1
Vuforia Version: 9.0.12
The app works fine in unity editor, it builds and runs successfully without error but no camera feed (black screen). Can't seem to find up to date solutions online.
Updated the Vuforia version to 9.2.7 does not seem to solve the problem.
I don't think to check the "Vuforia Augmented Reality Supported" under the "XR Settings" is an option, because it's able to deprecate. Also Checking the "Windows Mixed Reality" plug-in under XR Plug-in Management didn't solve the problem.
I already checked the "InternetClient" and "WebCam" in the publish setting for UWP.
Do I need to change anything in ARCamera's "Open Vuforia Engine configuration"? Some solutions mention disabling the Vuforia play mode will help, but I can't seem to find the option anywhere.
Anyone encountered the same issue and find a solution? Thanks.
I don't have a current solution, but would like to share my experience working with vuforia, UWP.
I found that there are varying breaking versions of unity and vuforia's SDK.
The latest version may not necessarily work I had to trial and error before I found a compatible version, so you might want to try that out. perhaps a older version of either unity/vuforia in reference with https://library.vuforia.com/platform-support/supported-versions.html
And yeah, definitely run your "hello world" tests on the sample projects first.
Best of luck, it's a great SDK ,once you get it to work.
I am currently working on developing an application for the Hololens 1 using Unity and MRTK.
I have been unable to get the air tap or any other input working in my application. The ring pointer for airtap does not appear in the application even though it works in the Unity Play Mode Input Simulation and other applications on the device. I tried it with the MRTK examples and even those did not work on the device.
Also I had to add the Tracked Pose Driver from the Player Settings to get the camera working properly but have not figured out how to get the application to accept gesture input.
Also tried the solution listed here: Why is 'air tap' gesture not working on HoloLens1 in my Unity/MRTK app?
but that did not work.
Will appreciate any guidance to solve this problem.
I finally got my project working after a lot of trying.
It turned out that initially, I had unknowingly configured the project to use XR SDK in Unity 2019 and thus had to configure MRTK accordingly. Thank you to Kevleigh for helping me with the issue here: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/7850
While this did work for my example project, I couldn't get the main project to work with the same settings even after installing all the plugins.
Finally, I had to switch to Unity 2018 and I got the project working with MRTK 2.3 and the default configuration. So, while Unity 2019 did not work for me you can get it working with XR SDK as suggested in the above link.
I'm almost new to Unity3D, I've watched this presentation of Unity evengelist made in February 2016:
https://www.youtube.com/watch?v=pK0ZD53gOoE
Evengelist said and showed that to bring project to VR you need to select one checkbox (Virtual Reality Supported). Now in 5.5 version just downloaded, when I select Virtual Reality Supported it says also "you must add at least one VR SDK", also after that checkbox selected when I click play scene, I do not see two eyes screen, just ordinary view. When last year I tried to make VR for Cardboard and loaded Cardboard SDK, scene view showed two screens to each eye in play mode.
So the question - how now make VR that works on Cardboard in Unity3d? Do I still need Cardboard SDK (I don't need magnet input support or similar, just stereo and head movement support)?
Added: I don't have Cardboard SDK option in Unity somehow:
According to Unity Blog, Cardboard support is exclusive to Android only. iOS Cardboard support will be added soon.
Do I still need Cardboard SDK
I don't think you need the SDK. This is now Native support for Cardboard. Although,you can still download the Cardboard SDK and Unity will automatically use it.
And here is how to enable Cardboard SDK in Unity 5.5.
Thanks Programmer for your answer, it helped me find what my issue was. However, I've spent literally all of my time over the past few days trying to get Google Cardboard and Unity setup, so I figured I can at least post my answer too.
One problem I initially ran into was that I was trying to use GVR Unity SDK v1.1. There are several bugs in this version, so I reverted back to the GVR Unity SDK v1.0.3. This can be downloaded from the github repo: https://codeload.github.com/googlevr/gvr-unity-sdk/zip/f391c2436426857899af1c37f0720b3985631eb3
Then, I ran into multiple problems just getting things to run on android, so I found that I have to use build tools version 24.0.1. This can be downloaded using the Android SDK Manager executable.
Lastly, the "cardboard" option wasn't appearing for me as part of the drop downs, just like in the picture posted by the asker. The problem was that I was using a regular version of Unity, when I needed to actually be using the technical preview. This can be downloaded from https://unity3d.com/partners/google/daydream, and I'm running Unity v5.4.2f2-GVR13.
Then the drop down "cardboard" appeared, and I was able to follow google's official instructions (https://developers.google.com/vr/unity/get-started) and get things set up.
I ended up installing the Unity 5.6 Beta and got my Cardboard app built quite simply using the EasyMovieTexture store asset, turning on VR in Player Settings and adding Google Cardboard. It is working great in IOS and Android. I am working on turning off the Google Overlay as my app toggles between Cardboard and a simple 360 view and that is a proving a challenge. It seems from what I have read Google does not want you to turn off their overlay. I might try to do this natively on IOS.