-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Looking Glass WebXR Support #260
Comments
As Unity is a closed box, the simplest solution was to send the views to the full framebuffer. I guess you already looked at Notice that Unity's JS minimizer on some versions supports only ES5, so newer JS syntax won't work in the jspre file. |
Any updates? Or things that I can change that would help with this implementation? |
I did try building out a basic implementation in unity to test performance. One of the issues that I ran into was unity's webGL / WASM output being limited to a single-thread, rendering 48 cameras at once is much slower than in native builds. I briefly tried looking into some optimizations for it, but didn't have too much luck and sort of left it at that for the time being. |
I tried to look if there's open source Looking Glass Unity package, but it seems that I need to download a I recently added support for Unity XR SDK to WebXR Export, but sadly there's no Single Pass or Multiview support for web. |
So, this issue is mostly to ask a few questions about the project, specifically around Unity's handling of multiple views as I'm looking to see if it's possible to use this to support the Looking Glass WebXR Library.
It looks like unity currently renders both views to the full framebuffer based on some digging with nvidia nsight,
I've attempted to load the Looking Glass WebXR Library with the Unity WebGL output, and while it does initiate an XR Session it doesn't render beyond two views, this part makes sense because of the way the plugin was written. I'm working on a PR now that remedies this, but was more curious about the full canvas rendering.
The way the Looking Glass WebXR Library works is that it renders a grid of views to the XRWebGLLayer, then runs those through a subpixel shader to render for the Looking Glass display. Currently, the Unity WebGL build seems to render the views to the full framebuffer, rather than the specific quadrant associated with a view, is this something baked into unity, or something that can be configured with how the WebXR Exporter is handled?
Thanks!
The text was updated successfully, but these errors were encountered: