Legacy XR Disabled

Looking at the XR project settings within a project under 2019.3 with Oculus XR package installed. I'm seeing the following alert messages (screenshots below).

I'm not sure this is a problem, but is there any information on where the new XR settings pages are? If they're required at all?

I'm not sure this is a problem but I'd like to know where I might be able to look for more insight on what's happened here between versions.

 

OK - so - in an update, this *is* actually a problem. It looks like the new Oculus SDK doesn't work with VRTK?\\I'm trying to launch a demo scene and am getting an eternal scene loading screen.

Will try again without VRTK to see if that's the problem I guess.

 

Did you resolve this ?

 

do you resolve this

 

I'm having the same issue. Does anyone know how to best resolve this?

 

Also facing this issue after just starting a project today. Though I have a working Oculus VR project made earlier, but weighed down with sample assets.

To resolve this particular issue:

1. I opened the Window>PackageManager and removed anything with "XR" in the name.
2. Then the "Virtual Reality Supported" Option, disabled in the above screenshot, was no longer disabled. I checked it.
3. restart Unity

After updating the remaining, seemingly essential Oculus packages and restarting Unity, the Oculus option was available on the top toolbar, and using it I built and ran the App, which thankfully loads much quicker than my previous one.

Overall, getting started, Follow these steps:

1. https://developer.oculus.com/documentation/unity/unity-conf-settings/#enable-vr-support
   
2. https://developer.oculus.com/documentation/unity/unity-add-camera-rig/?device=QUEST
   
3. The steps noted above to finish enabling VR support to access the Oculus top-toolbar menu.

 

Sorry to all who are asking about this. I was mainly doing VR work for use in conferences. When COVID hit, the idea of sharing a face covering across thousands of people lost some of its luster.

100% of my VR work dried up overnight.

I did wind up finding a solution to this, but it was so long ago I've forgotten exactly what it was. Sounds like Allenjonesing has a workaround, but IIRC I went another way and decided to abandon VRTK rather than downgrade to the older packages.

If you check out the unity-created XRTK, it has a similar suite of interactables while being "more native" as a dependency.

 

did you find a solution?

 

apakah kamu menemukan solusi?