Final Hurdles on Oculus store - Gear Vr Demo

Almost got the demo I’ve been working on ready for the Oculus store…

Have two more tweaks that I’m struggling to fix…

Note 4
Lollipop
Your app should maintain a framerate of at least 60 FPS.

  • all the other devices get a green light!
    A “back” action is interpreted by the application dependent on its current state, but generally it will retreat one level in an interface hierarchy. The short-press should provide a custom confirmation dialog which allows the user to exit the app and return to Oculus Home. Short press does not take me back to Oculus Home. Short press option should bring up the, exit to Oculus Home? screen.

  • this functionality works on my test device!

anyone encountered similar problems? Going to comb through the app and look to optimise… the back button is a mind scramble though…

any help appreciated!

thanks

  1. You can drop support for Note 4 by sending an email to submissions@oculus.com and by mentioning in submission notes as well.

  2. Back button should respond at every stage in the app. If this doesn’t work, they usually mention the state of app in which it doesn’t work. Again the best thing would be to send an email to ask for details. I assume that you are using OVRPlatformMenu.cs for that. If you have your own script that handles back-button. You should have a look at this script to compare what they might expect which you aren’t offering in the app.

1 Like

Thanks for the reply!

I think i’ll drop support for the note 4 and add a submission note - cheers for that…

Not currently using that script - as the last unity update seemed to add that function automatically, will look into it!

This script is recommended by Oculus and easy to use as well. Just drop on any persistent gameObject (which exists in all scenes ) and you are good to go. Short press will show “Quit to Oculus Home” menu and long press will show Utility Menu.

1 Like

Submitted again! fingers crossed…

This is crazy - The app is now failing the graphics test…

Your app should maintain a framerate of at least 60 FPS.
Frame rate is consistently low throughout the app, and drops specifically when attempting to look up

This is happening even though previous builds have passed these tests, and there is no performance drop on my test device. ( Samsung S6 )

Anyone else had similar problems?

I can give details of the app/unity scene etc if anyone is interested. Real bummer as the app has now missed the submission date for the holidays.:frowning:

Welcome to the ‘Walled Garden’. Google Daydream is even more ridiculous.

Are you using Legacy Vertex Lit rendering path?

1 Like

i’ll go double check, have you experienced a similar rejection?

I have never tried to publish to Oculus store. I also have no plans of publishing to Daydream, as outlined here:
https://forum.unity3d.com/threads/how-can-i-submit-my-daydram-app.446010/

However, I understand the problems with performance as I built mobile VR game for the 1st Gear VR on a Note 3:

Unless you have a greatly optimized (and small) scene, per-pixel lighting effects cannot be used (bump, spec, dynamic lighting etc). So that’s why to use vertex lit render path. You still need to know every single shader, material, texture, and model, etc that is being used and optimized each as much as possible.

Thanks for all that advice dude!

Pretty sure i used vertex lit render path - cant check right now as I’m out of the studio…

Also spent two days optimising the hell out of all the models, materials, animation etc…

So if I want to publish a game for gear vr the rendering path has to be Legacy Vertex Lit and not Forward?

No, it has to run consistently at 60fps on a note3.

re-submitting!

option for rendering with Legacy vertex lit dropped from the latest version of unity, but using the rendering path from the camera.

changed all materials to mobile/vertex lit(only Directional Lights)

still looks pretty good on my samsung s6…

God i hope this works as I’m really get sick of this demo.