So this is a weird one. The window that loads when you open up the build setting in Unity (2019.4.10f1) seems to be lagging up my computer.
No other part of Unity does this and I haven’t found any help with it. Anyone got any ideas?
Thanks!
Usually when unity is like this it depends on nvidia drivers. But of course what you are describing is really vague and could be anything
Related
So this question I think is the same as this but the solution for this problem was downgrading to Unity 2017 LTS, which is incompatible with my current project.
Basically, whenever I build, there's maybe a 10% chance that the app runs in the Hololens. Most of the time however, no floating balls animation pops up, no Unity splash screen appears, and I don't see any of my app content. Strangely enough, the app does ask for microphone permissions, but that's all. It should ask for eye tracking too, but it doesn't. (Not sure if that's related but I'm out of ideas.) On a proper run, I get the floating balls, Unity splash, and all permissions asked before the content. The most frustrating part is that it sometimes works, and there has been no trend at all towards what helps or what doesn't.
I've tried rebuilding in Unity, redeploying in VS, reinstalling the appx, updating VS, updating Windows, and checked every forum post I could find but I can't figure this out. Does anyone have any ideas?
I thought it might be an OpenXR / Holographic remoting problem, but those have both been dead ends. Really not sure what to do at this point. Thanks in advance.
Unity version: 2020.3.36f1,
VS 2022, MRTKv2, HoloLens 2
Thanks for the help everyone! For some reason, my solution is just as confusing as the problem, but it seems to reliably work.
Problem has something to do with the Holographic Remoting for OpenXR, so simply enabling and then disabling that feature in the editor right before building seems to fix a buggy build. Tested this a few times now and it works pretty consistently. Hope this can help someone and eventually get patched.
EDIT: Previous answer didn't work. Now I'm thinking the problem was actually caused by a toggle in the Project Settings. For a successful build it seems as though XR Plug-in Management > Windows Mixed Reality > UWP > Use Primary Window should be checked on. Seems weird since I'm using OpenXR anyways, but this might help someone so thought I'd update. Works most of the time now - needs more testing.
There are two solutions:
Use "Windows Mixed Reality" plug-in provider.
Use "OpenXR plugin". For this case the order of installation of packages plays important role:
When you create new project, manually install OpenXR plugin using Package Manager of Unity.
Using "Mixed Reality Feature Tool", install other features of MRTK2 including "Mixed Reality Open XR plugin" in "Platform Support".
XR Plug-in Management
OpenXR features
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'm trying to develop an app to Oculus Quest
yet i encounter many issues on the way.
the app basically consist of a room and teleportation.
the issue i encountered happens both on unity 2018.3.12 and 2019.1.8.
I created an app that did work as expected before on Quest using Oculus integration v1.35.
however, when re-exported and installed to a brand new Quest device:
teleportation that worked before refuse to work
pressing a button on 1 controller hids the other one from view.
hands movement is limited
even though target devices is set to Quest, I still (on v1.35) see the controller of oculus go
it only happens when exporting to quest, on rift it works just fine.
from the posts in Oculus Forum
https://forums.oculusvr.com/developer/discussion/comment/702108#Comment_702108
https://forums.oculusvr.com/developer/discussion/79144/hands-not-showing-up-with-localavator-unity#latest
it looks like there is a firmware issue (but then you should be encountering that too no?)
things I tried:
Start a new project from scratch:
followed the standard tutorial and documentation like those
https://www.youtube.com/watch?v=qiJpjnzW-mw&t=1s
https://developer.oculus.com/documentation/quest/latest/concepts/book-unity-gsg/
could not see the hands at all, and no teleportation was implemented, it is said that there is a bug in current v1.39
https://forums.oculusvr.com/developer/discussion/79144/hands-not-showing-up-with-localavator-unity
I tried to use both the unity OVR assets and the following plugins
https://assetstore.unity.com/packages/tools/input-management/vr-movement-system-for-oculus-47292
https://assetstore.unity.com/packages/tools/input-management/vr-arc-teleporter-61561
and in all 3 encountered the same issue.
did anyone encounter any issue similar to what's described?
as said, i expect to see the ands and controllers, and the code attached to the trigger press executed. none of this happened.
as some test, (since i do not have another quest)
i exported a build and sharing here.
please comment if you have tried it and it workd fine on your quest or not
https://www.dropbox.com/s/uvcmhyar2qljb19/k14.apk?dl=0
From what you wrote it's seems like an update issue with your device.
Check references with the new device .
For me when i publish i use the 2018.4.1f LTE
Since i encountered a lot of issues with android build with the 2019 version.
Go to the company and ask what changed with the new versions.
thanks to all the helpers.
update 1:
if hands don't appear at all, its because Oculus integration 1.39 is buggy
revert to 1.38
https://developer.oculus.com/downloads/package/unity-integration-archive/
second:
the problem is that the latest firmware update added GO controller support and defaulted it.
so Quest controllers begun appearing as GO
the trick was to copy the AndroidManifest to Assets/Plugins and edit it properly to specifically define the correct settings.
you can see the recommended changes here
https://developer.oculus.com/documentation/quest/latest/concepts/mobile-native-manifest/?fbclid=IwAR3AgasGPJFVGsz7lyzfJNfuTB8R1FOg88Quq8YZz67eQlwEFvgEMDGjSdo
I recently downloaded unity onto my new computer. However, whenever I open in I only get a blank work space window with the warning of Assertion failed on SUCCEED(hr). I haven't used unity in years and I can't seem to find a solution to this problem on their forums. I have tried re-downloading Here is a link to an screenshot I took of the problem unity in different versions. I have also tried downloading their projects. Nothing is working, does anyone have any idea what could be going on? thank you!
I had to switch from Nvidia GPU to integrated graphics in the NVIDIA Configuration/Settings in the Taskbar.
Does anyone know if this is bug in Unity version 5.4.1f1 I am not able to to use the Maximize on Play feature in the editor. I have to manually maximize then play for it to work.
Does anyone know if this is bug in Unity version 5.4.1f1?
Yes, it is a bug. You need to vote for this bug here and file for a new bug report. This will let Unity know that so many people are having this problem.
I do suggest that you update your GPU driver. This will likely fix it temporary.