I've been searching the internet for a couple of hours and couldn't find anything related. So far, I just found that the GitHub project is archived. Also, there are several posts about the rebranding made in 2018, but none mention that they will stop working on it. They are even keeping the old React VR Docs.
So, what happened to it?
It seems like this is the case. You can see all of the currently supported development technologies here. Two of these are Unity and Unreal. Just click on the computer icon to see the other technologies. I looked through all of the options and did not see React mentioned anywhere.
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
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 have made a test project using Network Manager, and unity multiplayer service. It works perfectly on PC, but android device does not see list of servers.
After couple of hours searching internet, all I have found is that I have to supply Unet ID. I have found the ID in the Unity Dashboard, but.. what the hell do I do with it now? There is a ton of abandoned questions & threads all over the internet, and no answer. Help?
Unfortunatly, uNet is now deprecated, and was never really fully supported/working.
It is strongly advised to look for other solutions especially if you need matchmaking. I would recommand photon:
there is a new version that just came out: https://assetstore.unity.com/packages/tools/network/pun-2-free-119922
or you have the old version: https://assetstore.unity.com/packages/tools/network/photon-unity-networking-classic-free-1786
As far as I know, if I choose official facebook unity plugin, then a few prime31 unity plugins for android would be broken because they all override the main Unity Activity. Because there are many prime31 plugins but only one official facebook plugin, so an ideal solution would be that only changes to facebook plugin is applied.
The question is: how? Does anyone have experience on this?
Best,
Raven
Well, this is a bit old but no one has answered. You can use facebook with prime31's other plugins but you need a small modification to the FacebookPostProcess.cs ( changing a line from some default to 9999 ). I've ran into this issue twice, once for developing an app and another for a game. It has worked both times. Heres the official documentation: http://prime31.com/docs ( the red text box at the top ) and https://gist.github.com/prime31/6417808 for the code for implementation. Hope this helps.
Does anyone know of any good resources on the web to get the Prime31 Google Play Game Services Plug in to work with Unity3D?
Its been 3 days, I just don't seem to be making any progress testing Game Play Services in my game.
I am using the SHA1 from the ~/.android/debug.keystore - which I believe is the the right SHA1 that the unsigned version uses. I also tried using the published build in order to get the Game Center to come up.
I tried the Prime31 documentation, but that doesnt seems to be helping.
I also believe my app is correctly setup in the Game Service area of the Developer Console.
Any information would be great.
Thank you.
It turned out that after importing the game center package , I ended up with two manifest files. I had the Prime[31] AdMob already in the project, which comes with a manifest file.
By the way this is normal.
After talking to the their support service they directed me to use the "Generate AndroidManifest.xml file..." under their prime[31] drop down menu inside Unity3D. This merges the two files into a single manifest. That problem got solved.
I also had to upgrade to the latest files, by downloading them manually, from the Prime[31] web site.
After this two steps I was able to get the Game Center to work properly.
I hope it will help, I am posting my interaction with the Prime[31] support