CIS 565 - GitHub

Teaching Intro and Advanced
Graphics with WebGL
Patrick Cozzi
Ed Angel
Analytical Graphics, Inc.
University of Pennsylvania
University of New Mexico
Why WebGL?
Ed’s Course
Patrick’s Course
What is WebGL?
• WebGL 1.0 is a JavaScript API based on
OpenGL ES 2.0
– uses HTML5 canvas element
– runs in all recent browsers
• OpenGL ES 2.0 is
– shader based with no legacy fixed-function
Why WebGL and Why Teach with it?
Cross-platform broad deployment – web and mobile
Low barrier-to-entry
Fast iteration
Modern-ish API
Integrate with other web APIs
Why not WebGL?
• Students need to learn JavaScript: not an
• Academic integrity? not an issue
• Initial startup time for first application higher:
minor issue
WebGL in Teaching
Interactive 3D Graphics Udacity
course by Eric Haines
Intro class now in WebGL
High-Profile WebGL Uses
Two Approaches
• WebGL from the beginning
• OpenGL then WebGL
– fixed function OpenGL or shader-based
• Both approaches share some key
elements that must be presented
Necessary New Elements
Execution in a browser
Starting with WebGL
Ed’s course
Student projects from
CS 495/595 ECE 491/591: Special Topics (online)
CS/ECE 412: Computer Graphics
Week 1: Introduction and Overview
Week 2: Introduction to WebGL
Week 3: GLSL and Shaders
Week 4: Input and Interaction
Week 5: Geometry and Transformations
Week 6: Modeling and Viewing
Week 7: Projection Matrices and Shadows
Week 8: Lighting and Shading
Week 9: Buffers and Texture Mapping
Week 10: Discrete Techniques
Week 11: Off-Screen Rendering.
Week 12: Hierarchy
Week 13: Implementation
Week 14: Curves and Surfaces
Week 15: Global Rendering
Basic Decisions
• Only JS and HTML
– no CSS or JQuery for required projects
– discourage use of three.js
– shaders in HTML file
• Encourage use of separate HTML and JS
– HTML file for page layout, resources and shaders
– JS file for WebGL
Project 1: Tessellation and Twist
twist without tessellation
tessellated triangle
twist after tessellation
Project 2: CAD
Stephen Harding
Project 3: 3D Maze
Term Project: CSG Modeler
Zach Friendland
Term Project: Animated Voronoi Diagram
Trevor Corriveau
• At the beginning, we needed to spend a
little time on the following none of which
were prerequisites for the course
– JavaScript
– Execution in a browsers
• At the end:
– students did better with the WebGL version
and liked it better
– we were able to bring a lot more interactivity
back into the course
– experienced no platform-dependent problems
From OpenGL to WebGL
• The course we just described replaces the
course that was taught with desktop
• That course had transitioned from the
fixed-function pipeline to the a fully
shader-based OpenGL three years ago
Student projects from
CIS 565: GPU Programming and Architecture
CIS 700/003: Real-Time Rendering
Ray Marching Distance Fields
Nop Jiarathanakul – CIS 565 Spring 2012
Procedural Infinite City
Alice Yang – CIS 565 Spring 2012
Hao Wu and Guanyu He – CIS 565 Fall 2013
Deferred Shading
Sijie Tian and Yuqin Shao – CIS 565 Fall 2013
Particle Fluid Simulation
Alex Miller and Noah Lyons – CIS 700/003 Spring 2014
Online Shader Editors
System Capability Tools
Web Tracing Framework
WebGL Tools - Firefox
WebGL Tools - Chrome
All WebGL Sessions at SIGGRAPH
Contact Info
Patrick Cozzi
Analytical Graphics, Inc.
University of Pennsylvania
Ed Angel
University of New Mexico
[email protected]
[email protected]
Bonus: WebGL on Mobile
From Olli Etuaho, NVIDIA
Qualitative differences between
mobile and desktop
1. highp shaders not supported everywhere - and testing lowp and mediump
shaders requires specific hardware, since on desktop lowp and mediump
evaluate as highp as well.
1.1. Example gotcha from a real app: accessing cube map with a nonnormalized vector can cause severe distortion when the shader is running in
low precision, while it looks fine on desktop where variables specified as lowp
are actually evaluated at higher precision.
2. Extension support varies more: most importantly s3tc compressed textures,
anisotropic filtering and OES_texture_float, ANGLE_instanced_arrays are
much less widely supported ( Using floating-point textures as
framebuffer attachments is not supported on any GLES2 device.
2.1. Rendering to RGB floating-point textures not supported on GLES3
devices either, only RGBA if the driver has the right extensions. This is due to
limitations in the GLES3 EXT_color_buffer_float spec.
Qualitative differences between
mobile and desktop
3. Context loss is more likely: power events, robustness limits easier to hit.
4. Mobile devices are typically HighDPI, so 1:1 pixel rendering is harder to
5. Various limitations exposed by getParameter. These apply to some desktop
platforms as well, but limitations are much more common on mobile: Texture
access from vertex shaders may not be supported at all. Multisampling may
not be supported. Depth buffer precision can be lower (16-bit is much more
common on old mobile SOCs), and shader variable count limits are tighter.
6. GenerateMipmap for any 32-bit float textures might not be supported, even if
OES_texture_float_linear is supported. (On IMG GPUs, see ). GenerateMipmap is not
supported for RGB float textures on any ES3 device (see ES3
GenerateMipmap spec).
Performance differences between
mobile and desktop
1. Memory bandwidth is limited, which will cause one of two things:
1.1. On chunker architectures, which cache a part of the framebuffer in GPU
memory, state changes like switching framebuffers can be especially
expensive. Avoid state changes.
1.2. On modern, desktop-like SOCs like Tegra K1, framebuffer access is more
time-consuming. However, ways to mitigate:
1.2.1. Avoid overdraw.
1.2.2. Do work in shaders instead of issuing multiple draw calls where possible
- shaders have plenty of processing power! This trend is only expected to grow
stronger in the future.
2. Lowp and mediump shader math might be faster, lower-power than highp
3. Memory capacity can be limited compared to desktop.

similar documents