WebXR-WebGPU-Binding
navigation
| WebXR-WebGPU-Binding | navigation | |
|---|---|---|
| 1 | 3 | |
| 49 | 69 | |
| - | - | |
| 1.5 | 10.0 | |
| about 1 year ago | over 1 year ago | |
| Bikeshed | ||
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
WebXR-WebGPU-Binding
-
WebGPU is not a replacement for Vulkan (yet)
Not a very expansive post. Here's a few more things WebGPU is missing (at least on the web):
- Push constants (wgpu has them as a native feature for all backends) (allows avoiding a uniform buffer write and bind)
- Texture binding arrays (https://docs.rs/wgpu/latest/wgpu/struct.Features.html#associ...) (allows for rendering multiple materials at the same time)
- Multiview rendering (https://docs.rs/wgpu/latest/wgpu/struct.Features.html#associ...) needed for WebXR bindings (https://github.com/immersive-web/WebXR-WebGPU-Binding/blob/m...)
navigation
-
Meta rebuffs Google's virtual reality tie-up proposal
A primary feature of the Metaverse as initially envisioned was having a platform for diverse virtual shared spaces, experiences and software.
WebXR has the potential to be this shared platform. But certain features such as immersive navigation that would facilitate this may be being deliberately held back or neglected.
https://github.com/immersive-web/navigation/issues/14
-
The GPU Banana Stand
But representing the DOM etc inside a 3D space is useful so you don't loose access to the world of 2D information. However there are no good solutions to this at present the Immersive Web Workgroup in W3C are looking at Layers or DOM Overlay which is for AR modes but might support 2D navigation but it seems low down on the priority list due to CORS and other security challenges.
https://github.com/immersive-web/navigation
-
VRML
The Wikipedia example shows something kind of JSON-like but originally VRML was like HTML (SGML).
Something similar to that is A-Frame VR which is built on WebVR.
There used to be a way with at least one VR-enabled browser to navigate without exiting VR (if the other site supported VR). Not sure any still support it. I think this may be because it goes against walled-gardens interests. https://github.com/immersive-web/navigation#api-proposal
What are some alternatives?
webxr - Repository for the WebXR Device API Specification.
3d-tiles - Specification for streaming massive heterogeneous 3D geospatial datasets :earth_americas:
depth-sensing - Specification: https://immersive-web.github.io/depth-sensing/ Explainer: https://github.com/immersive-web/depth-sensing/blob/main/explainer.md
VL.Fuse - A library for visually programming on the GPU, built to enable rapid workflows and modular approaches to accelerated graphics, logic and computation.
dom-overlays - A feature incubation repo for layering DOM content on/in WebXR content. Feature lead: Piotr Bialecki
webxr-linux - Repository containing efforts in getting usable WebXR under Linux
performance-improvements - A feature-incubation repo for XR-related performance improvements. Feature lead: Trevor F. Smith
sdf-csg - Generate meshes from signed distance functions and constructive solid geometry operations.
raw-camera-access - Spec draft: https://immersive-web.github.io/raw-camera-access/. Repository for experimentation around exposing raw camera access through WebXR Device API. Feature leads: Piotr Bialecki, Alex Turner, Nicholas Butko