VR Tutorial for Meta Quest 3 Setup

This topic has 33 replies, 3 voices, and was last updated 5 months, 1 week ago by kdv.

Viewing 4 posts - 31 through 34 (of 34 total)

← 1 2 3

Author

Posts
2024-02-11 at 5:07 pm #70398

tomtm
Customer

kdv wrote:

tomtm wrote:

Mst of the time I have 90 fps

What resolution per eye? EB W and EB H values in OVR Metrics Tool.

tomtm wrote:

Did you make the changes?

Yes, I reworked and optimized the original demo.

Also you can test FPS in the original demo with VR mode added.
Use this link https://v3d.net/k94 (not from the Asset Store)

EW B / EW H
1680 x 1760 show’s in the tool.

What is the trick with the collison, that the camera goes up the stairs?
Is there a addition in the raytrace puzzles?

2024-02-12 at 3:52 am #70403

kdv
Participant

Did you test this https://v3d.net/k94? What FPS it shows?

tomtm wrote:

1680 x 1760 show’s in the tool.

That’s too low resolution. It gives you blurry experience in VR. You should test with at least 2064 x 2208. Actually, for the best, monitor-like picture, the resolution should be 2700 x 2700 for Quest 2 and 3000 x 3000 for Quest 3.

tomtm wrote:

What is the trick with the collison, that the camera goes up the stairs?
Is there a addition in the raytrace puzzles?

Read this topic to the end

VR Controller Navigation (Quest 2)

Puzzles and JS coding. Fast and expensive.

If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

2024-02-12 at 10:12 am #70422

tomtm
Customer

kdv wrote:

Did you test this https://v3d.net/k94? What FPS it shows?

tomtm wrote:

1680 x 1760 show’s in the tool.

That’s too low resolution. It gives you blurry experience in VR. You should test with at least 2064 x 2208. Actually, for the best, monitor-like picture, the resolution should be 2700 x 2700 for Quest 2 and 3000 x 3000 for Quest 3.

tomtm wrote:

What is the trick with the collison, that the camera goes up the stairs?
Is there a addition in the raytrace puzzles?

Read this topic to the end

VR Controller Navigation (Quest 2)

<iframe class=”wp-embedded-content” sandbox=”allow-scripts” security=”restricted” style=”position: absolute; clip: rect(1px, 1px, 1px, 1px);” title=”“VR Controller Navigation (Quest 2)” — Soft8Soft” src=”https://www.soft8soft.com/topic/vr-controller-navigation-quest-2/embed/#?secret=SXmV0tDZ93#?secret=oXaqu4KgOj” data-secret=”oXaqu4KgOj” width=”600″ height=”338″ frameborder=”0″ marginwidth=”0″ marginheight=”0″ scrolling=”no”></iframe>

Where could I change the resolution?
The specs for MQ 3 is 2064 x 2208 pixels per eye.

2024-07-10 at 3:29 pm #75842

kdv
Participant

tomtm wrote:

Mst of the time I have 90 fps, biggest dip is at 79 fps.

That’s the power of optimization If you compare with the original demo from the App Store with the VR mode added https://v3d.net/k94 (use only this link, not from the App Store), you will see a little degradation in perfomance. Just three times less FPS. Even Quest 3 is too weak for it.

kdv wrote:

Where could I change the resolution?

Quest Games Optimizer + OVR Metrics Tool to control the result.

Puzzles and JS coding. Fast and expensive.

If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.
Author

Posts