- Type
- Experimental Browser Build
- Download
- Download
- Version
- 2017-02-17
- Date released
- File size
- 94 MB
- System requirements
- 64-bit
- Release notes
-
- Applies multiple optimizations on top of the version of WebVR publicly available in Chrome 56 beta, primarily in the form of reducing texture copies. This gives significantly better performance and latency in most cases. Consider this a preview of performance targets for later versions of Chrome, with further possible improvements still to come.
Instructions
- Download the experimental build of Chromium with WebVR support.
- Find the
chromium_webvr_v1.1_win.zip
file in yourDownloads
directory, and extract all the contents. - In the output directory, find and launch the
chrome.exe
file. - In the URL bar, load
chrome://flags#enable-webvr
and toggle theEnable WebVR flag
. - In the URL bar, load
chrome://flags#enable-gamepad-extensions
and toggle theEnable Gamepad Extensions
flag. - Launch the SteamVR application.
- Enjoy WebVR content!
Demos
Latest version
Known issues
View list of bugs Report a bug
These known issues apply to the latest published build. Where applicable, the detailed release notes below will list when historic known issues were fixed.
Note: There is no installer for the experimental builds of Chromium. Once the contents of the .zip
file is extracted, launch chrome.exe
directly from the chrome-bin
directory.
Description | Browser build | Headset | Reported | Updated | Status |
---|---|---|---|---|---|
Scene wobbles as headset rotates | 2016-12-23 | HTC VIVE | Unresolved | ||
WebVR crashes immediately on calling `vrDisplay.requestPresent()` | 2016-12-23 | HTC VIVE | Fixed | ||
The timestamp passed to the `requestAnimationFrame` callback is off by a factor of 1000 | 2016-12-23 | Oculus Rift, HTC VIVE | Fixed |
Help
- What is the difference between Chromium and Chrome?
-
Chromium is an open-source Web browser project, started and maintained by Google, for the proprietary, closed-source Google Chrome browser. Chromium and Chrome share the majority of code and functionality, though there are some minor differences in features (e.g., video/audio codecs, Speech Recognition/Synthesis APIs, etc.), branding/logos, and licensing.
- What is Blink?
- Which audio and video codecs are supported?
-
Because of licensing issues, only these open codecs are supported right now. Namely, MP3 and x264 are not supported. These formats are supported: Opus audio (
audio/opus
,audio/ogg
), WebM (video/webm
), Theora (video/ogg
), Vorbis (audio/vorbis
), VP8, VP9, and WAV. - Where can I find the list of known bugs?
-
You can find a list of the known issues above. You can also search the issues listed in the
toji/chrome-webvr-issues
GitHub repository WebVR bugs for the experimental Chromium builds (not Chrome for Android). - How can I report a bug?
-
First, refer to the known issues above and the issues listed in the
toji/chrome-webvr-issues
GitHub repository WebVR bugs for the experimental Chromium builds (not Chrome for Android).If you still don’t see your issue reported for the experimental Chromium builds (not Chrome for Android), you can file a new bug in the
toji/chrome-webvr-issues
GitHub repository. Or, if you’d prefer, you can file a bug on WebCompat.com.