Single/Multiplayer, Touch & Vive blueprint only Template

cjlee · June 21, 2019, 11:55pm

Thanks a lot for the info and great works!!

Hi @vbvisr

I should release it soon, the only thing that keeps me is work, work, work!

I’ve been quasi-exclusively developing with the Quest / Rift S for the last 2 months. Learned a lot of things; I had also a lot of communications with the Oculus for Business people, so I’ll share with you what I’ve learned.

As a preview, here’s what you can do/do not with Quest as of now:

You can use the Expressive Avatars, it works well

You can use ES2, ES3.1 and Vulkan, they both work well. ES3.1/Vulkan are pretty much identical, but maybe some performance gain with Vulkan

You cannot enable the mic with the Quest, as it’s clashes with the Avatars plugin. So as we speak the Expressive Avatars on the Quest are mute. Anyway unless you’re multiplayer, it will not matter for now.

You cannot use platform features (including multiplayer), unless you’ve gained access to the Quest API

Oculus (as for now) are only giving access to Quest API to accepted pitches.

Accepted pitches are only for the general public store. No keys-only apps.

There are other ways you can publish/sideload your app (i.e. WeAreVR, SideQuest, etc), but again, without Oculus platform features

You can use photon for multiplayer, but I’ve never gone that way. As I have a good relation with Oculus I prefer to stick to their platform.

All business/education/keys only apps will have to be managed through the Oculus Business Software Suite, sold as 499$ upgrade / 999$ already installed on a 128Gb Quest. The Suite will be launched this fall, probably at OC6?

I spoke to many people at Oculus, it seems that it is not clear for now if business/education/keys only apps will use platform features of the general public store or a “business” store. It seems it is not decided for now.

So I’ll do a kind of mini-guide, including more infos on the bugs and small changes to do to VS. See you soon!