What's the Target FPS for Quest?

72

Thank you very much. So that means, that 72-FPS the absolute maximum FPS you can reach with the Quest, is this correct?

Also, if that's the case. Is there anything inside of the Unreal project settings you need to consider before deploying?
Like, setting up a fixed FPS? 

Nope, once you start working on more projects you realize it tough to maintain that FPS. For now, if you are hitting 70, that is fantastic

Thank you prokshit. I am currently tackling three major issues.

1. Is there a faster way to deploy to the Quest?
   It takes some time to run tests, because deploying to the quest using the USB3 cable takes some significant time. Isn't there a way to simulate the Quest-Deployment directly on PC?
   
2. For some reason, when running the app with Five-Primitive Objects only, I am dropping in some areas down to 55-FPS. All lights are static, everything is baked.
3. When running on the Quest, and moving my head left to right, the objects look like they are "jumping". A jittery effect happens. What could possible cause that problem and how to fix it?

additional question:
if you don't have a PC, how can you copy a packaged Android Game to the Quest and run it?

I'll upload my project file asap.

VR VIDEO Capture Test-Result can be found here:
https://www.youtube.com/watch?v=Re6RmLMxl4Y


Unreal Project File for Download:
https://mega.nz/#!hfR2wKAD!IO4PFmSoShJG7eNIxmNYrbk4WgvXsZmz4dvjx0xR8BQ

Problem #1:
As you can see in the Video, I am having an AA issue.
The edges appear jaggy and black - I am using 8xMSAA .

There is also an additional problem, you can NOT see in the video-capture.
When using the Quest, the cubes (1mx1m) seem to "jump" when turning the headset.
Ruins the entire experience and can make your head spin.

For some reason, we can also see a significant FPS-Drop when looking at the cubes or the picture on the wall.
Even so, I am just dealing only with 1000 triangles, just using static lights and all is baked.

Question:

• What could cause the problem and how could I fix that?

Thank you so much!

Choose "Scalable 3D or 2D" in  "Target hardware".  That may be helpful to the "jump".

Thank you Michael and MaxArch.

My project is setup with "Scalable 3D or 2D". So the "jumping" still remains and that doesn't really cause this problem.

@MaxArch:
The Plugin Substance:
You don't need that plugin at all. Just uncheck in the Plugin Settings. And you are 100% good.
There are only 4-Materials I am using for this test.

They are Standard Unreal Materials. And only texture maps are added to the Difuse Slot.
One Shader (on the red sphere) is using some roughness. Just to test reflection. 

It's a super simple setup, just with primitive objects.

VIDEO EXPLANATION:
https://youtu.be/U1sdR8S73P4

Custom Build UnrealEngine:
That's odd. I am just using the latest 4.24.2 you can download from the Epic Launcher. It's nothing special, just the general build.

Updated Scene File:
In my latest Project File, I added a rotating head-sculpture. I wanted to see the performance when an object is rotating. As expected, Frames Drop. For the rotation I am losing about -20 FPS. Wow, that's a lot.

DOWNLOAD PROJECT FILE:
https://mega.nz/#!gWJREKYI!XIlBMFzjC9OKbHffLKr8aKF6kZ6MdFQJBhPN-RzzBE8

My Documentation about HotFixes, Debugging and my Developing-Process for the Quest can be found here:
https://fattybull.com/oculus-quest/

cheers

Hi Max!

Thank you so much for your reply - suuuuper cool, appreciate it!!!  :)

I will test each component to see what impact it will have. It's a lot of testing, but I also want to document what's causing issues or what's "eating up" the performance.

@vulkan:
I also noticed in another test, when Vulkan was enabled the app stopped working on the Quest. It took me a while to figure out that it was Vulkan. It was not clear for me, when you check "Support Vulkan" if the Quest automatically uses Vulkan and ignores OpenGl. 

However. When I turned off Vulkan at all, I still had the Anti-Aliasing issues on all the edges. Even if I was using 8xMSAA.

@Lights:
At my very first test I just used static lights for best performance. After that est, I loaded the statue (head) to see how the lights will react when using an animation. I noticed that my frames dropped -20FPS. Pretty huge for an animation. But that seems to be intense for the rendering. And yes, I guess I just want to test one Moving Light with Real Time Shadows on to see how the performance will be using also the turntable animation (statue on the cube).

@TexturMaps Resolution:
Yes, that makes totally sense. I think I loaded just three texture maps. The one on the cube (1meter grid size) is for sure 512x512 so that works for mipmaps. The two other ones I just compressed as .jpg images and then added .. also for testing purpose. What's interesting.. is that you mentioned that the two texture maps are already using 40MB RAM. Hmm... how much RAM can the Quest actually handle? Didn't look into that yet, but for sure super interesting.

I am going to watch again Sjoerd de Jong's Unreal Videos. I did already as soon as they have been released. However, I am also testing.. meaning.. I want to see what impact texture maps have, reflections etc.

But so far, I only created a base Material.. there is nothing complex. Just a texture map in the Base Color. Besides the Glossy Plastic Shader, that uses Roughness Values. 

Good Texture maps are for sure very important. But I am also a "nerd" in render quality. And for sure, reflections are important for materials. One thing that is unclear, is the texture format: I am using .jpg images, but I could read on some other documentations that you should use ASTC Texture compression: https://youtu.be/JvMQUz0g_Tk?t=459

Is this a compression you automatically have when saving .jpg images using Photoshop?
or is this a specific compression format you need an additional plugin?

Thank you so much for all your input - that's super nice and kind of you.
I really do appreciate that!

Happy developing and testing!
cheers, Bernhard 

ps: I'll keep you posted with my tests.. really curios if I can resolve the two current issues: AA, and "jumping" effect.