forked from immersive-web/immersiveweb.dev
-
Notifications
You must be signed in to change notification settings - Fork 0
/
chrome-support.html
154 lines (152 loc) · 5.59 KB
/
chrome-support.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
---
---
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<link rel="stylesheet" href="./main.css">
<link rel="stylesheet" href="./highlight.css">
<title>Chrome Hardware Support - Immersive Web Developer Home</title>
<meta property="og:title" content="Chrome Hardware Support - Immersive Web Developer Home">
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@ImmersiveWebW3C">
<meta name="twitter:creator" content="@ImmersiveWebW3C">
<meta property="og:url" content="https://immersiveweb.dev/">
<meta name="description" content="Get started building XR applications through the Web with the WebXR Device API, demos, docs, samples and more.">
<meta property="og:description" content="Get started building XR applications through the Web with the WebXR Device API, demos, docs, samples and more.">
<meta property="og:image" content="https://immersiveweb.dev/images/webxrlogo.png">
</head>
<body>
<main>
<img src="./webxr-logo.svg" alt="The WebXR Device API" />
<h1>Chrome Hardware Support</h1>
<article style="grid-column: 1/-1;">
<p>Chrome supports WebXR on a variety of platforms and hardware. This page details the supported devices and required configuration (if any) to use them.</p>
</article>
<h2>
Chrome Compatibility Table
</h2>
<div class="compat-table">
<table>
<thead>
<tr>
<td>Device</td>
<td>OS</td>
<td>Runtime</td>
<td>Supported Session Modes</td>
<td>WebXR Support</td>
</tr>
</thead>
<tbody>
<tr>
<td>
Windows Mixed Reality PC headsets
</td>
<td>Windows</td>
<td>Windows Mixed Reality</td>
<td>immersive-vr</td>
<td>Enabled in Chrome 79+</td>
</tr>
<tr>
<td>
Daydream View<br/>
Lenovo Mirage Solo
</td>
<td>Android</td>
<td>Google VR</td>
<td>immersive-vr</td>
<td>Enabled in Chrome 79+</td>
</tr>
<tr>
<td>
<a href="https://developers.google.com/ar/discover/supported-devices">ARCore-compabile mobile devices</a>
</td>
<td>Android</td>
<td>ARCore</td>
<td>immersive-ar</td>
<td>Enabled in Chrome 81+</td>
</tr>
<tr>
<td>
Oculus Rift<br/>
Oculus Rift S<br/>
</td>
<td>Windows</td>
<td>Oculus</td>
<td>immersive-vr</td>
<td><a href="#experimental-vr-flags">Experimental VR support</a></td>
</tr>
<tr>
<td>
HTC Vive<br/>
Valve Index<br/>
Other OpenVR-compatible headsets<br/>
</td>
<td>Windows</td>
<td>SteamVR</td>
<td>immersive-vr</td>
<td><a href="#experimental-vr-flags">Experimental VR support</a></td>
</tr>
<tr>
<td>
OpenXR-compatible headsets
</td>
<td>Windows</td>
<td>OpenXR</td>
<td>immersive-vr</td>
<td>Enabled in Chrome 81+,<br/><a href="#experimental-vr-flags">Requires the XR_EXT_win32_appcontainer_compatible extension</a></td>
</tr>
</tbody>
</table>
</div>
<h2 id='experimental-vr-flags'>
Enabling experimental support for other VR headsets
</h2>
<p style="grid-column: 1/-1;">
Some desktop headsets are capable of working with Chrome but their associated runtimes have not yet been enabled by default. This is typically because the Chrome team is still working with the runtime developer to ensure it can be used with the browser's security requirements. Developers that want to test Chrome's support for these devices can enable them by following the steps below.
<br/><br/>
<b>It is not recommended that you use Chrome with the following flags for daily browsing, as it disables certain security measures around Chrome interaction with VR hardware.</b>
<br/><br/>
Additionally, please note that runtimes that have not been enabled by default may exhibit a variety of issues or not support all applicable WebXR features.
</p>
<p style="grid-column: 1/-1;">
<b>Unsandboxed OpenXR</b>
<br/><br/>
To test Chrome with OpenXR runtimes that do not implement the <i>XR_EXT_win32_appcontainer_compatible</i> extension, use the following command line options:
<pre>--disable-features=XRSandbox</pre>
</p>
<p style="grid-column: 1/-1;">
<b>OpenVR</b>
<br/><br/>
To test Chrome with experimental support for OpenVR, use the following command line options:
<pre>--disable-features=XRSandbox --enable-features=openvr --force-webxr-runtime=openvr</pre>
</p>
<p style="grid-column: 1/-1;">
<b>Oculus</b>
<br/><br/>
To test Chrome with experimental support for Oculus, use the following command line options:
<pre>--disable-features=XRSandbox --enable-features=oculus --force-webxr-runtime=oculus</pre>
</p>
<footer>
<p>CC0 Licensed, feel free to remix, Maintained by the <a href ="https://w3.org/immersive-web">W3C Immersive Web Working and Community Groups</a>
</p>
<p>
Request changes by <a href="https://github.com/adarosecannon/immersiveweb">making a pull request on github.</a>
</p>
</footer>
</main>
<script>
Array.from(document.querySelectorAll('main > h1,main > h2, main > h3')).forEach(el => {
const id = el.id || el.textContent.replace(/[^a-z0-9]/gi,'').toLocaleLowerCase();
el.setAttribute('id', id);
const linkEl = document.createElement('A');
linkEl.className = 'targetlink';
linkEl.setAttribute('href', '#' + id);
linkEl.innerHTML = '🔗︎';
el.insertAdjacentElement('afterbegin', linkEl);
});
</script>
</body>
</html>