WebXR: Difference between revisions
Xinreality (talk | contribs) |
Xinreality (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 43: | Line 43: | ||
With the announcement of visionOS 2 in mid-2024, Apple further committed to WebXR by making it enabled by default in Safari, eliminating the need for users to enable experimental feature flags. However, as of May 2025, WebXR on visionOS still only supports the immersive-vr session type, with the immersive-ar mode still in development.<ref name="immersiveweb"></ref> | With the announcement of visionOS 2 in mid-2024, Apple further committed to WebXR by making it enabled by default in Safari, eliminating the need for users to enable experimental feature flags. However, as of May 2025, WebXR on visionOS still only supports the immersive-vr session type, with the immersive-ar mode still in development.<ref name="immersiveweb"></ref> | ||
Ongoing efforts in the standard focus on improving performance, enhancing device compatibility, refining input methods, and expanding AR capabilities across platforms. | Ongoing efforts in the standard focus on improving performance, enhancing device compatibility, refining input methods, and expanding AR capabilities across platforms. | ||
| Line 70: | Line 68: | ||
#Delivering the combined framebuffer to the XR device for display | #Delivering the combined framebuffer to the XR device for display | ||
The API handles the complex timing and scheduling required for comfortable XR experiences, but does not directly manage 3D assets or perform | The API handles the complex timing and scheduling required for comfortable XR experiences, but does not directly manage 3D assets or perform rendering. That responsibility falls to WebGL or other graphics libraries.<ref name="mdn-fundamentals"></ref> | ||
====Input Handling==== | ====Input Handling==== | ||