forked from immersive-web/webxr-samples
-
Notifications
You must be signed in to change notification settings - Fork 0
/
xr-presentation.html
240 lines (202 loc) · 10.4 KB
/
xr-presentation.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
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
<!doctype html>
<!--
Copyright 2018 The Immersive Web Community Group
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-->
<html>
<head>
<meta charset='utf-8'>
<meta name='viewport' content='width=device-width, initial-scale=1, user-scalable=no'>
<meta name='mobile-web-app-capable' content='yes'>
<meta name='apple-mobile-web-app-capable' content='yes'>
<!-- Origin Trial Token, feature = WebXR Device API, origin = https://immersive-web.github.io, expires = 2018-07-25 -->
<meta http-equiv="origin-trial" data-feature="WebXR Device API" data-expires="2018-07-25" content="AiOtRLgiXauzJY1CytLCb96aWE1XryUKk1o4uTBQNRpMoeFAbO9e+wsRbT41diaTMC3M6NC6C+HgubQtPUU57wEAAABceyJvcmlnaW4iOiJodHRwczovL2ltbWVyc2l2ZS13ZWIuZ2l0aHViLmlvOjQ0MyIsImZlYXR1cmUiOiJXZWJYUkRldmljZSIsImV4cGlyeSI6MTUzMjU0MDY0Mn0=">
<title>XR Presentation</title>
<link href='css/common.css' rel='stylesheet'></link>
<!--The polyfill is not needed for browser that have native API support,
but is linked by these samples for wider compatibility.-->
<script src='https://cdn.jsdelivr.net/npm/webxr-polyfill@latest/build/webxr-polyfill.js'></script>
<!--This script patches up around implementation differences in past browser versions
so that the samples can always be written against the most recent spec changes.
It won't be necessary after the API has been officially shipped for a bit.-->
<script src='js/webxr-version-shim.js'></script>
<script src='js/cottontail/build/cottontail.js'></script>
<script src='js/webxr-button.js'></script>
</head>
<body>
<header>
<details open>
<summary>XR Presentation</summary>
<p>
This sample demonstrates how to present a simple WebGL scene to a
XRDevice. The scene is not rendered to the page prior to XR
presentation, nor is it mirrored during presentation.
<a class="back" href="./">Back</a>
</p>
</details>
</header>
<main style='text-align: center;'>
<p>Click 'Enter XR' to see content</p>
</main>
<script>
(function () {
'use strict';
// If requested, initialize the WebXR polyfill
if (QueryArgs.getBool('allowPolyfill', false)) {
var polyfill = new WebXRPolyfill();
}
// XR globals.
let xrButton = null;
let xrFrameOfRef = null;
// WebGL scene globals.
let gl = null;
let renderer = null;
let scene = new Scene();
scene.addNode(new Gltf2Node({url: 'media/gltf/space/space.gltf'}));
scene.addNode(new SkyboxNode({url: 'media/textures/milky-way-4k.png'}));
// Checks to see if WebXR is available and, if so, queries a list of
// XRDevices that are connected to the system.
function initXR() {
// Adds a helper button to the page that indicates if any XRDevices are
// available and let's the user pick between them if there's multiple.
xrButton = new XRDeviceButton({
onRequestSession: onRequestSession,
onEndSession: onEndSession
});
document.querySelector('header').appendChild(xrButton.domElement);
// Is WebXR available on this UA?
if (navigator.xr) {
// Request an XRDevice connected to the system.
navigator.xr.requestDevice().then((device) => {
// If the device allows creation of exclusive sessions set it as the
// target of the 'Enter XR' button.
device.supportsSession({immersive: true}).then(() => {
xrButton.setDevice(device);
});
});
}
}
// Called when the user selects a device to present to. In response we
// will request an exclusive session from that device.
function onRequestSession(device) {
device.requestSession({immersive: true}).then(onSessionStarted);
}
// Called when we've successfully acquired a XRSession. In response we
// will set up the necessary session state and kick off the frame loop.
function onSessionStarted(session) {
// This informs the 'Enter XR' button that the session has started and
// that it should display 'Exit XR' instead.
xrButton.setSession(session);
// Listen for the sessions 'end' event so we can respond if the user
// or UA ends the session for any reason.
session.addEventListener('end', onSessionEnded);
// Create a WebGL context to render with, initialized to be compatible
// with the XRDisplay we're presenting to.
gl = createWebGLContext({
compatibleXRDevice: session.device
});
// Create a renderer with that GL context (this is just for the samples
// framework and has nothing to do with WebXR specifically.)
renderer = new Renderer(gl);
// Set the scene's renderer, which creates the necessary GPU resources.
scene.setRenderer(renderer);
// Use the new WebGL context to create a XRWebGLLayer and set it as the
// sessions baseLayer. This allows any content rendered to the layer to
// be displayed on the XRDevice.
session.baseLayer = new XRWebGLLayer(session, gl);
// Get a frame of reference, which is required for querying poses. In
// this case an 'eyeLevel' frame of reference means that all poses will
// be relative to the location where the XRDevice was first detected.
session.requestFrameOfReference('eyeLevel').then((frameOfRef) => {
xrFrameOfRef = frameOfRef;
// Inform the session that we're ready to begin drawing.
session.requestAnimationFrame(onXRFrame);
});
}
// Called when the user clicks the 'Exit XR' button. In response we end
// the session.
function onEndSession(session) {
session.end();
}
// Called either when the user has explicitly ended the session (like in
// onEndSession()) or when the UA has ended the session for any reason.
// At this point the session object is no longer usable and should be
// discarded.
function onSessionEnded(event) {
xrButton.setSession(null);
// In this simple case discard the WebGL context too, since we're not
// rendering anything else to the screen with it.
renderer = null;
}
// Called every time the XRSession requests that a new frame be drawn.
function onXRFrame(t, frame) {
let session = frame.session;
// Per-frame scene setup. Nothing WebXR specific here.
scene.startFrame();
// Inform the session that we're ready for the next frame.
session.requestAnimationFrame(onXRFrame);
// Get the XRDevice pose relative to the Frame of Reference we created
// earlier.
let pose = frame.getDevicePose(xrFrameOfRef);
// Getting the pose may fail if, for example, tracking is lost. So we
// have to check to make sure that we got a valid pose before attempting
// to render with it. If not in this case we'll just leave the
// framebuffer cleared, so tracking loss means the scene will simply
// dissapear.
if (pose) {
// If we do have a valid pose, bind the WebGL layer's framebuffer,
// which is where any content to be displayed on the XRDevice must be
// rendered.
gl.bindFramebuffer(gl.FRAMEBUFFER, session.baseLayer.framebuffer);
// Clear the framebuffer
gl.clear(gl.COLOR_BUFFER_BIT | gl.DEPTH_BUFFER_BIT);
// Loop through each of the views reported by the frame and draw them
// into the corresponding viewport.
for (let view of frame.views) {
let viewport = session.baseLayer.getViewport(view);
gl.viewport(viewport.x, viewport.y,
viewport.width, viewport.height);
// Draw this view of the scene. What happens in this function really
// isn't all that important. What is important is that it renders
// into the XRWebGLLayer's framebuffer, using the viewport into that
// framebuffer reported by the current view, and using the
// projection and view matricies from the current view and pose.
// We bound the framebuffer and viewport up above, and are passing
// in the appropriate matrices here to be used when rendering.
scene.draw(view.projectionMatrix, pose.getViewMatrix(view));
}
} else {
// There's several options for handling cases where no pose is given.
// The simplest, which these samples opt for, is to simply not draw
// anything. That way the device will continue to show the last frame
// drawn, possibly even with reprojection. Alternately you could
// re-draw the scene again with the last known good pose (which is now
// likely to be wrong), clear to black, or draw a head-locked message
// for the user indicating that they should try to get back to an area
// with better tracking. In all cases it's possible that the device
// may override what is drawn here to show the user it's own error
// message, so it should not be anything critical to the application's
// use.
}
// Per-frame scene teardown. Nothing WebXR specific here.
scene.endFrame();
}
// Start the XR application.
initXR();
})();
</script>
</body>
</html>