Run the live WebGL 2 Samples Pack.

Short and easy to understand samples demonstrating WebGL 2 features by Shuai Shao (Shrek), Trung Le and contributors. Advised by Patrick Cozzi, University of Pennsylvania.

Inspired by and ported from Christophe Riccio's (@Groovounet) OpenGL Samples Pack.

Tarek Sherif writes a really helpful WebGL 2 Examples repo which demonstrates how these features can be used to implement commonly-used algorithms.

Texture LOD	Flat/smooth interpolation

Sampler object wrap	Transform feedback

❕ WebGL 2 is released on Chrome 56 and FireFox 51 now.

❕ Compatibility table updated on 2017/02/02

⚠️ the minial-gltf-loader used for samples is in development and contributions are welcome.

Clone this repo:

[email protected]:WebGLSamples/WebGL2Samples.git

Then run a local web server from the repo's root directory. for example, if you have Python installed, run

cd WebGL2Samples
python -m SimpleHTTPServer

Then browse to

http://localhost:8000/

The samples do not require a build; however, Node.js and gulp can be used to run JSHint to aid in development.

Install Node.js. From the root directory of this repo, run:

npm install

To run JSHint on the entire codebase, run

npm run jsHint

To run JSHint automatically when a file is saved, run the following and leave it open in a console window:

npm run jsHint-watch

This is a community project. We welcome contributions! Check out the issues for ideas on what to contribute.

When you open a pull request, please make sure that GitHub reports that "All checks have passed", indicated by the white checkmark in a green circle on top of the "Merge pull request" button. Travis CI is used to run JSHint on your branch, and CLA assistant is used for signing a Contributor License Agreement (CLA). Submit an issue if you have any questions.

WebGL applications should, in general, use the delete* APIs to manage their resources (buffers, textures, etc.) rather than relying on the browser's garbage collector to reclaim them. Note that many of the samples here do not delete their resources explicitly; this is the case because they would only be reclaimed upon page unload, and it's neither necessary nor desirable to install an onunload handler only for the purpose of destroying WebGL resources. See the following pages for more details:

https://www.khronos.org/registry/webgl/specs/latest/1.0/#3

https://bugs.chromium.org/p/chromium/issues/detail?id=5638

• WebGL 2 course from SIGGRAPH Asia 2015
• WebGL 2 Spec
• OpenGL ES 3.0 Reference Pages
• WebGL Report

• three.js example page framework by Mr.doob (@mrdoob) and contributors
• OpenGL Samples Pack by Christophe Riccio (@Groovounet) and contributors
• Cesium build script by Matt Amato (@mramato) and contributors
• webgl2-particles by Brandon Jones (@toji) and Mr.doob (@mrdoob)