Question Basic question when using Oculus Air Link for Quest 2 development

When using Oculus Air Link to run a project launched from within the Unity editor, is the application fully executing on the Quest 2 or is it simply being streamed and the processing is taking place on the PC?

Still figuring Quest 2 development out, but as of right now a build which is physically deployed to my Quest 2 is performing much worse than when I play test the same app launched from Unity using Air Link and I'm trying to understand why that is.

Thanks.

 

1. Air link is your desktop doing the work
2. "physically deployed" builds are running on a tiny mobile phone processor in the quest.

So it should be pretty obvious air link is not representative in any way of what the quest can do. It's what the desktop can do, streamed as video to the quest.

 

OK, so "Build and Run" is the only way to gauge the actual playability and spot any issues on the device? Makes sense and it certainly explains what I'm seeing. Thanks.

 

Yes, but still use air link (or regular link) to build and play the game in general. You just do Build and Run every so often to make sure performance is behaving (once you've achieved the perf you want).

 

Do you have any suggestions oh how to wear or place your headset while developing to make iterating easier? Do you raise it up and rest it on your forehead? Do you hang it next to you and aim it towards your desk so you don't have to wear it all of the time? Right now I'm just messing with a bunch of different interactions ideas so I've setup a little virtual world bench right where.my real one is. Sometimes I need to check out scene view while I'm testing to check various things as well.

 

I either put on the headset and use OVRMetrics (highly recommended!) to see performance, CPU and GPU usage, available RAM etc. If I just want to do edits in play mode in Unity I either put it on fully or hold it with my thumb over the distance sensor in the headset