Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are FFR (Fixed Foveation Rendering) and MultView extensions incompatible? #1371

Open
emadurandal opened this issue Jun 6, 2024 · 0 comments

Comments

@emadurandal
Copy link

(I am not sure if this is the right place to ask this question, but if you know of a better place, please let me know.)

I am working on improving the performance of WebXR in my Web3D library and have recently added support for the MultiView extension (oculus_multiview/OVR_multiview2).

To further improve it, I am also planning to use FFR (Fixed Foveation Rendering), but I found a curious description on the following oculus developer website: https://developer.oculus.com/documentation/web/webxr-ffr/#why-it-might-not-be-working

Rendering the scene to an intermediate buffer and then post-processing that into the final frame. FFR only applies when rendering to the final frame buffer, so if you’re rendering to an intermediate buffer, you won’t see a meaningful performance improvement.

The MultiView extension requires the scene to be drawn to a texture array rather than to the HMD's framebuffer. Would this conflict with this constraint?

Are FFR and MultiView incompatible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant