I created a new Unity Project which just has a simple Main camera and a Directional Light. I added the scene and chose Android as my build environment. When I "Build and Run" my Unity app always crashes and does not start the game. I tried building the same apk on other (non-tango) android device and it seems to load fine. I haven't even added my Tango prefabs yet (although i did try adding them but no luck).
Am I missing something ? Has anyone else experienced this problem ?
P.S.: My other tango unity samples seem to run fine.
Try following the steps in https://developers.google.com/project-tango/apis/unity/unity-prefab-motion-tracking. They also have some suggested Player Settings for Default Orientation (Landscape Left) and Min API (17).
Try disabling "Dynamic Batching" in android player settings and disable "Draw Default UX Exceptions" in Tango Ux Script, which did the trick for me
Related
So, my game in the windows build works perfectly but it freezes in my android build when my gamescene is finally loaded. It's a network game so I can see my android player moving, it's just that the screen it's permanently frozen. I have no errors in console and in one of my build I managed to get this: not sure if it helps, not sure what to do
enter image description here
Use Vulkan API for Android - instead of GLES: https://docs.unity3d.com/Manual/GraphicsAPIs.html
I just launched my game on Google Play, it works fine on Android devices, but if I try to boot it though Bluestacks emulator the Unity splash (sometimes) shows and after that only a dark grey screen and nothing happens
This is how it looks after the Unity Splash intro
I have tried to install the game though Google Play and by installing the Apk file itself, both ways dont work.
I'm using v2021.1.18f1 to build the game
The game itself is here https://play.google.com/store/apps/details?id=com.BrokenGlass.TapNinja
Thank you.
UPDATE
I fixed it by changing a lot of settings in the Player Settings, not sure which is the one that actually made it work. Raguels answers was partially correct, but changing only the Graphics API did not work.
This is how my Player Settings look
It is happening because you didn't include some of the supported graphics API in your android build. Bluestacks might not work if you omit OpenGLES2. Make sure you have OpenGLES 2 in your supported graphic APIs. You can find it in Project Settings/Player/Other Settings
To make it available, you will have to change the Color space from Linear to Gamma.
For me worked changing "Optimized Frame Pacing" to disabled, in Proyect Settings/Player/Resolution and Presentation
When running the sample project 'HelloCardboard' from Google VR cardboard-xr-plugin on my Samsung Galaxy S9 (API Level 29) the view stutters when I look around (move the camera) in VR. This wasn't a problem when I used the old Google SDK on Unity 2019.4 in my own project.
I'm using Unity 2020.1
To make sure that it was not a performance issue, I have tested the following:
removing all assets from the demo scene, except for the camera and a simple plane
creating a new project with the cardboard xr plugin installed, without importing the 'HelloCardboard' demo scene
Since this didn't make a difference regarding the stuttering, I tried running the app after I:
installed a different SDK (which shouldn't be a problem but still)
changed the Graphics API from OpenGLES2 to OpenGLES3
None of this worked.
Does anyone know what (might) cause the stuttering? Or know where I can find the solution? Please help.
Did you try to deploy app to another smartphone?
Did you try new plugin-in Unity 2019.4?
Did you try to use 'Mono' Scripting Backend?
Currently, I am trying to make the Virtual Tour app to play with cardboard, then get the demo completed and it's working like a charm in Editor Play mode and on my Lenovo Phab 2 phone. Unfortunately, when I install it on Samsung Note 9, the app displays upside down. I have tried change the orientation in player setting and edit the android manifest but still no luck are there any one know the solution? or is it the bug in GoogleVRSDK or Unity ,caused at first there is the lack in app build that Unity build the app as normal app not Cardboard one even GoogleVR Demo scene, but after restart Unity it works fine.
This is apparently an issue with Unity 2019.1.x and both Android and iOS.
Either, switch rendering from Vulkan to OpenGLES3 (Android, not sure about iOS)
Or, downgrade to 2018.3.14f (is said to work for both iOS and Android)
Track updates here:
https://github.com/googlevr/gvr-unity-sdk/issues/1030
https://github.com/googlevr/gvr-unity-sdk/issues/1031
I am developing using Unity5.3.5f1 (64 Bit) and have a problem with a black screen on my Nexus 7 Android version 4.4.3 every time I try to launch the app.
I try to implement the Vuforia Object Recognition Unity Sample (https://developer.vuforia.com/library//articles/Training/Vuforia-Object-Recognition-Unity-Sample-Guide) so it should work while I followed the instructions.
I didn't modify the code, just followed the instructions to add the 3D target.
I followed the hints of the developer forum to set the player settings for building https://developer.vuforia.com/forum/issues-and-bugs/camera-not-working-when-app-installed-mobile but nothing changed the situation:
Setting Rendering Path to "Legacy Deffer"
changing the Minimum API Level to Android 4.2
enable "GPU skinning"
set graphics APIs to "OpenGLES2"
I have noticed a lot of problems between unity and mobile devices when building. There seems to be some residual meta data left on the device from unity so not all changes end up working properly (which holds the information of what objects the script is attached to). I had an instance where I deleted EVERYTHING in my scene and I had a debug script attached to some of those items that would output some text to the Xcode console in the scripts start() method. After cleaning out the entire scene and redeploying that debug script was sill outputting to the console. I deleted the .meta file associated with that script and redeployed. This deletion stopped the file from running. I have noticed that restarting the device can also fix this issue. Also deleting the meta, deploying, then undoing the delete and running again also fixes some of these issues. You will NOT notice this problem when developing in unity and breakpoints will never be hit, but it will still happen on the mobile device and even run scripts that you completely disabled.