Official New! VR Beginner: Escape Room

looks really great. I will dive-in this weekend!

 

I have not been able to get this to build correctly on Quest for the life of me. I get a black box in my dashboard, almost like playing a video, the game doesn't render at all.

Also, the steps in the written tutorial are not clear, as the project does not appear in the learn tab of unity hub. Instead, I had to make a new project first, then go into package manager and import from there. Maybe this was my issue?

I think this is a great package, looks fantastic, and I can't wait to start going through the XR toolkit with my students!.. If only I could get the project to build!

 

I have tried absolutely every thing that you have suggested, followed the updated instructions to a tee, and still having the same issue.

I'm assuming I just need to remove the pre-existing build of the same project, as I have a few others on there (which by the way fully function using srp,opengl, and OVR).

Everything else is set exactly as you mentioned, and I am still getting the same black screen

 

Ok. I ended up changing to multipass instead of multiview, and it magically worked.. though when i went back into unity the oculus tab of the XR plugin management has changed into the older version where it just lets you choose stereo rendering and V2 signing. There were several more options beforehand..

I literally have no idea what I did to get it working, but it finally builds properly and I could explore the two premade scenes!

thank you for the help and for making this amazing project for learning!

 

Hello !

I just downloaded the project and everything seems to work fine with an HTC Vive

But I got something i find weird in the prototype scene, I don't have any component attached to the toaster, it's not grabbable, the knob cannot be turned and the lever cannot be pulled is that on purpose or something is missing ?
The left thermostat has the same "issue"

Anyway thanks for your work it's appreciated !

 

Hello,

In my quest apk is not running and it is opening like a black dashboard screen and nothing is rendering at all.
my graphics library is Vulcan and Texture compression is ETC2, and there is pretty much storage left in my quest.

Please help me!!

 

After exploring the project a bit more, I've realized that the post processing is not working when built for Quest. Does this have something to do with URP? Vulkan? Do I have to make sure I'm using a particular URP (mobile vs desktop)

I have been trying to figure out how to have performant bloom on Quest, and it seems like this project is using the most current frameworks, so I am just a loss.

 

Yes, I do have that checked, tested both in the escape room scene and a new "prototype" scene with added pp volume. N o effects are rendered.

Also, when I rebuilt in the escape room scene after turning post processing on, the teleportation assets dissappeared on.. for some reason they now become disabled on play.

Edit: This of course is happening because I didnt put the book on the pedastle to enable them!

So what did I do, I decided to start again, so I can understand the steps to get this project running. What happened? I ended up back where I started with the black box, even after doing everything that has been mentioned so far.

As I mentioned earlier, I noticed a difference in the oculus tab of the XR plugin management, or rather that it had changed. I have attached screenshots of both. I only managed to get this rendering correctly on device with the panel that has fewer options.

 

Hello everyone and thank you very much for this!

I'm trying to understand what is the best way to prototype VR projects quickly and I have been overwhelmed by VRTK, steam vr, oculus interation .. and all the problems they have with each other!

a week studies vrtk3, but then the 4 is better, but then the 4 does not go with steamvr and if the user has oculus?!?

no, you can't do that!

It seems to me that this is the solution!

I followed the whole tutorial and found it really well done.
If I can afford a note, I would have liked to have a little more explanations on the parts to interact with: like the buttons, the clock / menu on the right hand, and some explanations on programming .. for example what could be the best method for open a door? by clicking a button?
pushing it?

Another important point I think may be what to study next ..
the Design, Develop, and Deploy for VR course goes deeper, but uses different technologies .. is there a way to use those techniques (vrtk) with Unity XR?

Thanks again
great material!

 

I changed to android build (for Quest) and followed every step as shown in the tutorial. The build takes extremly long in the "compling shader variants" step, is this normal? I don't have a "high end" PC (only a VR ready PC with a GTX 970 and i5 6500 3.20GHz), but it still weird that such a simple scene (graphical wise) takes so long to build (Im currently at 30min and the part is like 40% done)

Also the Quest build seems a little "laggy" it's playable, but sometimes frame drops are noticable. Maybe the tutorial could add some additional optimization tricks for the Quest version?

Otherwise it's a nice demo, good job!

 

hey folks,

tried importing with 2019.3.3, keeps failing decompressing package :'(

Failed to import package with error: Couldn't decompress package
UnityEditor.Web.JSProxyMgroTasks()

 

I did this just yesterday in 2019.3.3 on a Mac and didn't run in to any issues. So, I'd suggest clearing your cache and re-downloading from scratch.

 

I also get black dashboard on Oculus Quest and nothing more. Has anyone found a solution? I've tried everything that have come to my mind.

 

Awesome. Too bad it does not include SteamVR... most people use that even for non game solutions.

 

First time, yes. it's very very slow to compile those shaders. After that, it's not bad.

I also noticed some choppy stuff when picking things up. I haven't investigated it yet, but I am guessing it's the difference between Update() and LateUpdate(). But I saw that kind of behavior in the XR Interaction Toolkit demo, too.

Since I've finished the tutorial, I'm going to pick apart the XR Interaction Toolkit with a better foundation now.

 

I've a question about compression methods. In this tutorial, it's recommended to use ETC2 (GLES 3.0). It was recommended to me before by someone else to use ASTC. Can someone explain the difference and why one would prefer one over the other? Is ETC2 better for Vulkan?

 

@UnityJackT, thanks a ton! Followed the steps and it fixed the issue for me.

 

I suppose that this doesn't work with the Samsung Gear VR, I'm right?

 

Looks like the course has been updated to use ASTC! https://learn.unity.com/tutorial/ge...bf44edbc2a09bf60dceb#5e4c0b5eedbc2a002125ac8c


One other thing they seem to be missing is (for Oculus Quest) is that Oculus requires ARM64 which is under
PLAYER ->
Set Scripting Backend to IL2CPP
and CHECK the ARM64 box.



I'm not sure if the course discusses this later, but it isn't in the setup phase.

 

Where is the OpenVR Plugin for the XR Plugins system. I find it odd that the plugin for the worlds Largest game distributor is missing still.

 

It hasn't been released yet. I think I recall seeing in another thread that it is confirmed to be in development, but not certain on that.

 

Hello everyone, first of all I wanted to thank the team responsible for that project as it helped me a lot understand the XR Interaction package.

I have a legal question : Can we use this project as a framework to develop our own projects (possibly commercial ones) ?

I find the ability to create an empty "VR Ready" scene very useful, and some prefabs in this project could be used too.

Thanks in advance

 

Hi there
I was wondering why on the documentation you say to do the locomotion system in one way

|
| On the XR Rig GameObject, add a Locomotion System, a Teleportation Provider, and a Snap Turn Provider.​

and then in the example it is done in a quite different way!?

and can you tell me where I can learn how to interact with buttons?

thanks a lot

 

ok
i understand how the master controller script works, but can i use it in my products?

are there other possibilities for having teleport and direct interatcion with the same controller?

thanks!

 

I have a WMR VR headset and it doesn't look like it is supported.

 

Is this a yes or a no?
The user didn't ask about the framework, but the solution shared as an example in this project.

This is exactly what Unity is missing from the base package.
A drag and drop teleportation and interaction solution that everyone could use as a base.


Even of this is a no,
I strongly suggest you distribute a similar system as prefab with the new XR framework.
One of the reasons many architects move to Unreal is because unreal offers exactly that.

They load their building, fix lighting and materials and after setting up the floor collision they can create VR scenes easily for their customers out of the box without having to search the Marketplace for hours and buy assets that do not work.

 

I don't have a WMR headset myself - but have you tried following the oculus setup steps and swapping in the windows XR plugin instead?



then make sure you don't switch to android



not sure if it will work for you, but probably worth a try.

 

If you hit play to test the experience are you supposed to see it in your headset? I have a quest with a working link cable attached and its not showing the experience. According to the oculus app everything is ok, link is enabled everything working fine except the preview.

Any ideas?

 

Good day everyone!
what is the best practice for having teleport and direct interaction with XR?

thanks for your help

 

maybe I'm wrong the question?

 

Hi! it was, I manually restarted but didnt work. Any other suggestion?

 

You could build it to the Quest?

 

Yes, I can build it generating the APK, no issues there.

What I cant is preview it on the headset while connected through link. Any ideas?

 

Thanks so much. After checking the issue was the Oculus Loader was only installed for Android. I added it to PC and it worked.

Thanks everyone for the help.