GLSL v1.20. Scott MacHaffie Schrödinger, Inc.

Similar documents
Shader Programs. Lecture 30 Subsections 2.8.2, Robb T. Koether. Hampden-Sydney College. Wed, Nov 16, 2011

Programming shaders & GPUs Christian Miller CS Fall 2011

Supplement to Lecture 22

Programmable Graphics Hardware

12.2 Programmable Graphics Hardware

GLSL Introduction. Fu-Chung Huang. Thanks for materials from many other people

Programmable GPUs. Real Time Graphics 11/13/2013. Nalu 2004 (NVIDIA Corporation) GeForce 6. Virtua Fighter 1995 (SEGA Corporation) NV1

CSE 167: Lecture #8: GLSL. Jürgen P. Schulze, Ph.D. University of California, San Diego Fall Quarter 2012

The Graphics Pipeline and OpenGL III: OpenGL Shading Language (GLSL 1.10)!

GLSL Introduction. Fu-Chung Huang. Thanks for materials from many other people

CS 4620 Program 3: Pipeline

Today. Rendering - III. Outline. Texturing: The 10,000m View. Texture Coordinates. Specifying Texture Coordinates in GL

The Transition from RenderMan to the OpenGL Shading Language (GLSL)

TSBK03 Screen-Space Ambient Occlusion

Lecture 17: Shading in OpenGL. CITS3003 Graphics & Animation

Shader Programming. Daniel Wesslén, Stefan Seipel, Examples

Sign up for crits! Announcments

Introduction to Shaders for Visualization. The Basic Computer Graphics Pipeline

Introduction to the OpenGL Shading Language (GLSL)

Introduction to Shaders.

Lets assume each object has a defined colour. Hence our illumination model is looks unrealistic.

The Basic Computer Graphics Pipeline, OpenGL-style. Introduction to the OpenGL Shading Language (GLSL)

CS 130 Final. Fall 2015

Pipeline Operations. CS 4620 Lecture Steve Marschner. Cornell CS4620 Spring 2018 Lecture 11

Lab 9 - Metal and Glass

Introduction to the OpenGL Shading Language

Objectives Shading in OpenGL. Front and Back Faces. OpenGL shading. Introduce the OpenGL shading methods. Discuss polygonal shading

Pipeline Operations. CS 4620 Lecture 14

CSE 167: Introduction to Computer Graphics Lecture #13: GLSL. Jürgen P. Schulze, Ph.D. University of California, San Diego Fall Quarter 2015

MXwendler Fragment Shader Development Reference Version 1.0

CMPS160 Shader-based OpenGL Programming. All slides originally from Prabath Gunawardane, et al. unless noted otherwise

Information Coding / Computer Graphics, ISY, LiTH GLSL. OpenGL Shading Language. Language with syntax similar to C

Methodology for Lecture. Importance of Lighting. Outline. Shading Models. Brief primer on Color. Foundations of Computer Graphics (Spring 2010)

Shaders. Slide credit to Prof. Zwicker

OpenGL shaders and programming models that provide object persistence

CS 130 Exam I. Fall 2015

WebGL and GLSL Basics. CS559 Fall 2015 Lecture 10 October 6, 2015

Shaders CSCI 4239/5239 Advanced Computer Graphics Spring 2014

CS559 Computer Graphics Fall 2015

Programming with OpenGL Part 3: Shaders. Ed Angel Professor of Emeritus of Computer Science University of New Mexico

Lecture 09: Shaders (Part 1)

Programmable Graphics Hardware

CS 381 Computer Graphics, Fall 2012 Midterm Exam Solutions. The Midterm Exam was given in class on Tuesday, October 16, 2012.

Deferred Rendering Due: Wednesday November 15 at 10pm

Levy: Constraint Texture Mapping, SIGGRAPH, CS 148, Summer 2012 Introduction to Computer Graphics and Imaging Justin Solomon

SHADER PROGRAMMING. Based on Jian Huang s lecture on Shader Programming

GLSL 1: Basics. J.Tumblin-Modified SLIDES from:

EDAF80 Introduction to Computer Graphics. Seminar 3. Shaders. Michael Doggett. Slides by Carl Johan Gribel,

Adaptive Point Cloud Rendering

Shaders CSCI 4229/5229 Computer Graphics Fall 2017

LSU EE Homework 5 Solution Due: 27 November 2017

WebGL and GLSL Basics. CS559 Fall 2016 Lecture 14 October

GPU Programming EE Midterm Examination

1 of 5 9/10/ :11 PM

Lecture 5 Vertex and Fragment Shaders-1. CITS3003 Graphics & Animation

Computer Graphics Coursework 1

Today s Agenda. Basic design of a graphics system. Introduction to OpenGL

CMPS160 Shader-based OpenGL Programming

Graphics Programming. Computer Graphics, VT 2016 Lecture 2, Chapter 2. Fredrik Nysjö Centre for Image analysis Uppsala University

Programming with OpenGL Shaders I. Adapted From: Ed Angel Professor of Emeritus of Computer Science University of New Mexico

Zeyang Li Carnegie Mellon University

Computergrafik. Matthias Zwicker. Herbst 2010

GPU Programming EE Final Examination

Technical Game Development II. Reference: Rost, OpenGL Shading Language, 2nd Ed., AW, 2006 The Orange Book Also take CS 4731 Computer Graphics

CS 130 Exam I. Fall 2015

Understanding M3G 2.0 and its Effect on Producing Exceptional 3D Java-Based Graphics. Sean Ellis Consultant Graphics Engineer ARM, Maidenhead

C P S C 314 S H A D E R S, O P E N G L, & J S RENDERING PIPELINE. Mikhail Bessmeltsev

Programmable shader. Hanyang University

The Graphics Pipeline and OpenGL III: OpenGL Shading Language (GLSL 1.10)!

[175 points] The purpose of this assignment is to give you practice with shaders in OpenGL.

CS452/552; EE465/505. Intro to Lighting

Some advantages come from the limited environment! No classes. Stranight ans simple code. Remarkably. Avoids most of the bad things with C/C++.

Computer Graphics (CS 543) Lecture 8a: Per-Vertex lighting, Shading and Per-Fragment lighting

GPU Programming EE Final Examination

Computergrafik. Matthias Zwicker Universität Bern Herbst 2016

Shaders. Introduction. OpenGL Grows via Extensions. OpenGL Extensions. OpenGL 2.0 Added Shaders. Shaders Enable Many New Effects

OPENGL RENDERING PIPELINE

Waves, Displacement, Reflections. Arun Rao CS 594

Real-Time Rendering (Echtzeitgraphik) Michael Wimmer

Orthogonal Projection Matrices. Angel and Shreiner: Interactive Computer Graphics 7E Addison-Wesley 2015

OUTLINE. Learn the basic design of a graphics system Introduce pipeline architecture Examine software components for a graphics system

CS4621/5621 Fall Computer Graphics Practicum Intro to OpenGL/GLSL

Lecture 2. Shaders, GLSL and GPGPU

Shadows. Prof. George Wolberg Dept. of Computer Science City College of New York

INF3320 Computer Graphics and Discrete Geometry

Lecture 13: OpenGL Shading Language (GLSL)

CS770/870 Spring 2017 Open GL Shader Language GLSL

CS770/870 Spring 2017 Open GL Shader Language GLSL

Technical Game Development II. Reference: Rost, OpenGL Shading Language, 2nd Ed., AW, 2006 The Orange Book Also take CS 4731 Computer Graphics

BCA611 Video Oyunları için 3B Grafik

Problem Set 4 Part 1 CMSC 427 Distributed: Thursday, November 1, 2007 Due: Tuesday, November 20, 2007

Computer Graphics Fundamentals. Jon Macey

Graphics Hardware. Instructor Stephen J. Guy

Intro to GPU Programming (OpenGL Shading Language) Cliff Lindsay Ph.D. Student CS WPI

Real Time Rendering of Complex Height Maps Walking an infinite realistic landscape By: Jeffrey Riaboy Written 9/7/03

Objectives. Open GL Shading Language (GLSL)

Models and Architectures

OpenGL Programmable Shaders

Rasterization. CS 4620 Lecture Kavita Bala w/ prior instructor Steve Marschner. Cornell CS4620 Fall 2015 Lecture 16

X. GPU Programming. Jacobs University Visualization and Computer Graphics Lab : Advanced Graphics - Chapter X 1

Transcription:

1 GLSL v1.20 Scott MacHaffie Schrödinger, Inc. http://www.schrodinger.com Table of Contents Introduction...2 Example 01: Trivial shader...2 Syntax...3 Types of variables...3 Example 02: Materials vertex shader...4 Example 02: Materials fragment shader...5 Geometry transformations...7 Example 03: Sphere vertex shader...7 Example 03: Sphere fragment shader...9 if statements and the mix() function...11 Passing data...11 Variable lights...12 Example 04: Variable lights fragment shader...12 Debugging...13 Effects...15 Example 01: Outlines...17 Example 02: X...20 Example 03: Yellow X on red atoms...24 Example 04: Transparent atoms...25 Resources...28

2 Introduction Shaders are a convenient technique for getting higher quality and better performance out of modern graphics cards. GLSL is the name of the shading language which is a core part of OpenGL. GLSL has a unique version number corresponding to an OpenGL version number. this talk. For OpenGL 2.1, the GLSL version number is 1.20. This is the version I will be covering in For OpenGL 3.0, the GLSL version number is 1.30. This version is neither forwards- nor backwards-compatible with 1.20. GLSL is essentially a variant of C with extra features (additional data types, built-in functions, and built-in variables), minus some standard C features (e.g. pointers). A shader program requires both a vertex shader and a fragment shader. These two components are linked together into a shader program. The vertex shader is called once for each vertex, per primitive (e.g. three times for a triangle, four for a quad). The fragment shader is called once for each pixel. One of the big advantages of using shaders over traditional OpenGL code is that the lighting calculations can be done on a per-pixel basis, resulting in much higher quality. Example 01: Trivial shader The most trivial shader consists of transforming and passing the vertex coordinates in the vertex shader and copying the input color to the output color in the fragment shader. // This is a pass-through vertex shader void main()

3 gl_position = ftransform(); gl_frontcolor = gl_color; gl_backcolor = gl_color; // This is the pass-through fragment shader void main() gl_fragcolor = gl_color; Example 01: Basic vertex shader and basic fragment shader This fragment shader is actually useful for debugging. If the vertex shader is doing something complicated (typically, rewriting the vertices on the fly), then it can be helpful to use a pass-through fragment shader to check that the vertex shader is doing the correct thing. For example, I used a passthrough fragment shader several times when debugging the sphere vertex shader to make sure it was generating the correct bounding box. One easy way to do this in a fragment shader is to rename the real main() to main2() and insert the pass-through fragment shader as given above. Syntax Types of variables There are four types of variables in GLSL: uniform, varying, parameters, and local. Uniform variables are passed into the shader from the calling program (e.g. from Maestro). Varying variables are passed from the vertex shader to the fragment shader. Local variables are used within a function. Parameters are passed into separate functions. Uniform variables can appear in either the vertex shader or the fragment shader. I believe they have to be declared in the shader they are used in. For example, if a vertex shader uses "current_color", then it would need to have a declaration similar to: uniform vec3 current_color;

4 that would allow use of the current_color variable within the vertex shader. Note that uniform variables are shared between the fragment shader and vertex shader, and that they are read-only within the shaders. Thus, the fragment shader could access the same current_color variable as the vertex shader. Varying variables are set inside the vertex shader and passed as read-only variables into the fragment shader. Varying variables are interpolated across the vertices. For example, if you have created a triangle and you pass in the colors for the three vertices as solid red, solid green, and solid blue, then the colors will get interpolated based on the distance from each vertex. Pixels on the line from the red to the green vertex would smoothly transition from red to green. The pixels farther away from that line would have a blue component. Example 02: Materials vertex shader Here is a real example. This is vertex shader designed to handle the standard lighting model on a per-pixel basis. // This is a vertex shader using the current material settings varying vec3 normal; void main() normal = normalize(gl_normalmatrix * gl_normal); gl_position = ftransform(); gl_frontcolor = gl_color; gl_backcolor = gl_color; Example 02: Materials vertex shader We are passing a normal through to the fragment shader. This shader is called with triangles, so this shader will be called three times. The normal variable will be interpolated for each pixel. We are setting gl_position by calling ftransform(), which returns the projection modelview matrix

5 multiplied by the input position. We are also setting both the front and back colors from the predefined variable gl_color (which was set via the equivalent of glcolor3d() or by using a vertex array), although technically we probably only need to set the front color. OpenGL will convert the correct one of these (depending on whether the fragment is front-facing or back-facing) into the fragment shader predefined variable gl_color. Local variables are the same as in C or Python. There are int and float types, as well as vectors: vec2, vec3, and vec4. To access the elements of a vector, you can use either the syntax: v.xyzw or v.rgba. You can also access a partial set: vec4 v = vec4(1., 2., 3., 4.); vec2 v2 = v.xy; code: There is also a matrix type. Unlike C, GLSL has no implicit type casting. See the following int i; float f; // This code is wrong. It may compile on some cards / drivers and // fail on others f = i; // This is the correct way f = float(i); Function parameters can be any of the data types, but all function parameters take an additional keyword: in, out, or inout. in or inout means the variable can be read from. out or inout means the variable can be written to. Example 02: Materials fragment shader Putting all of that together, here is the fragment shader for handling materials and lighting on a per-pixel basis. It performs the basic lighting calculations to generate an output color based on two

6 lights (OpenGL lights 0 and 1), together with the ambient, diffuse, specular, emission, and shininess properties of the current (front) material. The lighting calculations are the same ones that OpenGL does when using the standard non-shader code, except that the shader does this for each pixel, and the standard pipeline only does this for each vertex. /* This is the corresponding fragment shader for materials */ // Note that this comes from the vertex shader and has been interpolated to // the correct value for this pixel. varying vec3 normal; void getlight(in int light, in vec3 N, inout vec4 ambient, inout vec4 diffuse, inout vec4 specular) vec3 L = normalize(gl_lightsource[light].position.xyz); vec3 H = normalize(gl_lightsource[light].halfvector.xyz); diffuse += max(0.0, dot(n, L)) * gl_frontlightproduct[light].diffuse; specular += pow(max(0.0, dot(n, H)), gl_frontmaterial.shininess) * gl_frontlightproduct[light].specular; ambient += gl_frontlightproduct[light].ambient; void main() vec3 N = normalize(normal); vec4 ambient = vec4(0, 0, 0, 1); vec4 diffuse = vec4(0, 0, 0, 1); vec4 specular = vec4(0, 0, 0, 1); getlight(0, N, ambient, diffuse, specular); getlight(1, N, ambient, diffuse, specular); ambient.w = 1.; diffuse.w = 1.; specular.w = 1.; gl_fragcolor = gl_color * (diffuse + ambient + gl_frontmaterial.emission) + specular; /* Need to copy over alpha */ gl_fragcolor.a = gl_color.a; Example 02: Materials fragment shader This shader makes use of a number of built-in variables. gl_lightsource is an array of

7 lights containing the position, color components, and a half-vector which is used for calculating specular highlights. The gl_frontlightproduct array contains the product of the gl_lightsource array with the front material properties for specular, ambient, and diffuse components. The output of the fragment shader is gl_fragcolor (another predefined variable). Geometry transformations Vertex shaders can be used to modify the geometry. This is useful because you can pass in a minimal set of vertices and pack them with additional data, then use that data to calculate complex shapes. Example 03: Sphere vertex shader For example, in the sphere shader, we pass in a quad with all four of the vertices set to the center of the sphere. This gives us the center coordinates to pass on to the fragment shader. We use a pair of variables, up and right to transform each vertex to the corners of a screen-aligned bounding box containing the sphere. // Vertex shader uniform vec3 right_vector; uniform vec3 up_vector; varying vec4 color; varying vec3 view_direction; varying vec3 sphere_center; varying float radius2; varying vec3 point; void main(void) // Get billboard attributes float right = gl_multitexcoord0.x; float up = gl_multitexcoord0.y; float radius = gl_multitexcoord0.z; radius2 = radius * radius; // compute squared radius // We need to project the vertex out to the edge of the square, which

8 // is the following distance: // float corner_distance = sqrt(2.0 * radius2); // but since we need to normalize the corner vector computed below // which has length sqrt(2.0), we can simply use radius as corner distance // to compute vertex position of screen-oriented quad. // Compute corner vector vec3 corner_direction = up * up_vector + right * right_vector; // Calculate vertex of screen-oriented quad (billboard) vec4 vertex = vec4(gl_vertex.xyz + radius * corner_direction, gl_vertex.w); // Calculate vertex position in modelview space vec4 eye_space_pos = gl_modelviewmatrix * vertex; // Compute sphere position in modelview space vec4 tmppos = gl_modelviewmatrix * gl_vertex; sphere_center = vec3(tmppos) / tmppos.w; // Compute ray direction and origin point point = vec3(eye_space_pos) / eye_space_pos.w; view_direction = normalize(point); // Pass fog coordinate gl_fogfragcoord = abs(sphere_center.z); // Pass the transformed vertex for clipping plane calculations gl_clipvertex = eye_space_pos; // Pass color color = gl_color; // Pass transformed vertex gl_position = gl_modelviewprojectionmatrix * vertex; Example 03: Sphere vertex shader In this example, the up and right directions are passed as part of the texture for the vertex. These variables are passed in as all combinations of 1 and -1 (e.g. 1, 1; -1, 1). Then, vertex is set to the center plus the up and right vectors. We also pass in some other useful variables (e.g. radius2) to the fragment shader to avoid repetitive computations at the fragment level (which will be called for each pixel). We also set gl_clipvertex to let OpenGL know that we've changed the vertex. It will

9 use this modified vertex as the basis for the interpolation for the data sent into the fragment shader. Example 03: Sphere fragment shader The vertex shader produces a quad bounding the sphere, but we still have to draw an actual sphere. The fragment shader takes the data that is passed in and calculates a sphere-ray intersection to determine which points are actually part of the sphere. // Fragment shader // 0 is no fog, 1 is linear, 2 is exp, 3 is exp2 uniform float fogging[4]; uniform float perspective; varying vec4 color; varying vec3 view_direction; varying vec3 sphere_center; varying float radius2; varying vec3 point; const float INV_LOG2 = 1.442695; void getlight(in int light, in vec3 N, inout vec4 ambient, inout vec4 diffuse, inout vec4 specular) vec3 L = normalize(gl_lightsource[light].position.xyz); vec3 H = normalize(gl_lightsource[light].halfvector.xyz); diffuse += max(0.0, dot(n, L)) * gl_frontlightproduct[light].diffuse; specular += pow(max(0.0, dot(n, H)), gl_frontmaterial.shininess) * gl_frontlightproduct[light].specular; ambient += gl_frontlightproduct[light].ambient; void main(void) vec3 ray_origin = mix(point, vec3(0., 0., 0.), perspective); vec3 ray_direction = mix(vec3(0., 0., 1.), normalize(view_direction), perspective); vec3 sphere_direction = mix(ray_origin - sphere_center, sphere_center, perspective); // Calculate sphere-ray intersection float b = mix(dot(sphere_direction, ray_direction), dot(ray_direction, sphere_direction), perspective);

10 float position = b * b + radius2 - dot(sphere_direction, sphere_direction); // Check if the ray missed the sphere if (position < 0.0) discard; // Calculate nearest point of intersection float nearest = mix(sqrt(position) - b, b - sqrt(position), perspective); // Calculate intersection point on the sphere surface. The ray // origin is at the quad (center point), so we need to project // back towards the user to get the front face. vec3 ipoint = nearest * ray_direction + ray_origin; // Calculate normal at the intersection point vec3 N = normalize(ipoint - sphere_center); // Calculate depth in fragment space vec2 clipzw = ipoint.z * gl_projectionmatrix[2].zw + gl_projectionmatrix[3].zw; gl_fragdepth = 0.5 + 0.5 * clipzw.x / clipzw.y; // Calculate lighting vec4 diffuse = vec4(0, 0, 0, 1); vec4 ambient = vec4(0, 0, 0, 1); vec4 specular = vec4(0, 0, 0, 1); getlight(0, N, ambient, diffuse, specular); getlight(1, N, ambient, diffuse, specular); ambient.w = 1.; diffuse.w = 1.; specular.w = 1.; // Calculate fog // No fogging float fog = fogging[0]; // Linear fog fog += mix(0.0, clamp((gl_fog.end - gl_fogfragcoord) * gl_fog.scale, 0.0, 1.0), fogging[1]); // Exp fog fog += mix(0.0, clamp(exp(-gl_fog.density * gl_fogfragcoord), 0.0, 1.0), fogging[2]); // Exp^2 fog: exp(x) = 2^(x/log(2)) fog += mix(0.0, clamp(exp2(-gl_fog.density * gl_fog.density * gl_fogfragcoord * gl_fogfragcoord *

11 INV_LOG2), 0.0, 1.0), fogging[3]); // Calculate final color gl_fragcolor = mix(gl_fog.color, color * (diffuse + ambient + gl_frontmaterial.emission) + specular, fog); Example 03: Sphere fragment shader The getlight() function is the same as in the materials shader. For spheres, we add in fogging. The fog code we have replicates the fogging modes in the fixed pipeline. if statements and the mix() function In graphics cards, if statements are typically very slow. On the other hand, the mix() function is very fast. To handle perspective versus orthogonal drawing, we use the perspective variable in combination with mix(). The mix() statement works as an if statement when you restrict your conditional values to 0 and 1. Basically: result = mix(x, y, condition) sets result to y if condition is 1 and x if condition is 0. Passing data You can pass data which doesn't vary across vertices (e.g. a highlight color) by using uniform variables. However, when you need to pass distinct data on a per-vertex basis, that won't work. Instead, you need to make full use of the variables which do vary on a per-vertex basis: Coordinate data (4 floats): you can use the fourth component of the coordinates to pass data, but you need to reset the fourth coordinate to 1 before operating on it. Color data (4 floats): if you have a fixed alpha, then you can use the color's alpha value to pass in different information. Texture data (4 floats): this is arbitrary data you can use for what you want.

12 Normals (3 floats): if you don't need the normal data, you can pass in your own values. Variable lights In Maestro, by default we enable only lights 0 and 1. Through the GUI, the user can turn off either one of those lights. Through commands, the user can turn on any combination of the eight OpenGL lights. We optimize the default case (as shown in the previous examples). For any other combination of lights, we fall back to a generalized lighting mechanism. Example 04: Variable lights fragment shader To handle the lights, we pass in an array indicating whether or not each light is on (1 for on, 0 for off). In GLSL, if statements are typically slow. Therefore, we want to minimize if statements. Specifically, we want to avoid doing eight if statements in a row. To do that, we make heavy use of the mix() statement. We do a straight multiply against enabled, and we use mix() to generate valid vectors. /* This is the corresponding fragment shader for materials */ uniform float light_enabled[8]; varying vec3 normal; const vec3 UNIT_VEC3 = vec3(1.0, 0.0, 0.0); void getlight(in int light, in float enabled, in vec3 N, inout vec4 ambient, inout vec4 diffuse, inout vec4 specular) vec3 L = normalize(mix(unit_vec3, gl_lightsource[light].position.xyz, enabled)); vec3 H = normalize(mix(unit_vec3, gl_lightsource[light].halfvector.xyz, enabled)); diffuse += enabled * max(0.0, dot(n, L)) * gl_frontlightproduct[light].diffuse; specular += enabled * pow(max(0.0, dot(n, H)), gl_frontmaterial.shininess) * gl_frontlightproduct[light].specular; ambient += enabled * gl_frontlightproduct[light].ambient;

13 void main() vec3 N = normalize(normal); vec4 ambient = vec4(0, 0, 0, 1); vec4 diffuse = vec4(0, 0, 0, 1); vec4 specular = vec4(0, 0, 0, 1); getlight(0, light_enabled[0], N, ambient, diffuse, specular); getlight(1, light_enabled[1], N, ambient, diffuse, specular); getlight(2, light_enabled[2], N, ambient, diffuse, specular); getlight(3, light_enabled[3], N, ambient, diffuse, specular); getlight(4, light_enabled[4], N, ambient, diffuse, specular); getlight(5, light_enabled[5], N, ambient, diffuse, specular); getlight(6, light_enabled[6], N, ambient, diffuse, specular); getlight(7, light_enabled[7], N, ambient, diffuse, specular); ambient.w = 1.; diffuse.w = 1.; specular.w = 1.; gl_fragcolor = gl_color * (diffuse + ambient + gl_frontmaterial.emission) + specular; /* Need to copy over alpha */ gl_fragcolor.a = gl_color.a; Example 04: Variable lights fragment shader Debugging Different drivers accept slightly different syntaxes for GLSL. For example, the nvidia drivers tend to be fairly permissive in what they accept. The code which loads the shaders in Maestro is set up to display any error messages we get from the driver at any stage (vertex shader compilation, fragment shader compilation, and linking). It can be useful to try shaders on different drivers: nvidia, Mesa v7.7 or later, and ATI. There are also some programs which can compile shaders and generate error messages for invalid syntax. I've used GLSL Validate from 3D labs (Windows or Linux under wine). One error that doesn't get reported well is either having too many main() functions in a shader or not enough. The vertex shader and the fragment shader each need to have exactly one main() function. nvidia in particular generates an unhelpful message (something like "couldn't link").

14 There are some OpenGL debuggers available, but I haven't used any of them so, I can't comment on their quality. The other way of debugging is to set specific colors to catch specific things (e.g. red for error #1, blue for error #2, yellow for error #3, white for no error). I have used this technique to identify when a calculation was not producing the expected result. If you are specifically trying to debug a vertex shader which rewrites the vertices, you can temporarily switch the fragment shader to simply pass through the input color. That will show you specifically where the vertices are, which might be useful.

15 Effects There are a number of effects which are possible using shaders. For reference, here is an image using the standard shader:

16 Example 01: Outlines This shader produces an outline around the outside of the structure. The idea with this shader is to set the interior of each sphere to black without adjusting the Z value, so that the spheres erase each other. Given the standard atom sphere fragment shader, the basic changes are to check if we're on the border (position < 0.1), and only then do we adjust the Z value and do the lighting calculations. Otherwise, we set the color to black. // Fragment shader // 0 is no fog, 1 is linear, 2 is exp, 3 is exp2 uniform float fogging[4]; uniform float perspective; varying vec4 color; varying vec3 view_direction; varying vec3 sphere_center; varying float radius2;

17 varying vec3 point; const float INV_LOG2 = 1.442695; void getlight(in int light, in vec3 N, inout vec4 ambient, inout vec4 diffuse, inout vec4 specular) vec3 L = normalize(gl_lightsource[light].position.xyz); vec3 H = normalize(gl_lightsource[light].halfvector.xyz); diffuse += max(0.0, dot(n, L)) * gl_frontlightproduct[light].diffuse; specular += pow(max(0.0, dot(n, H)), gl_frontmaterial.shininess) * gl_frontlightproduct[light].specular; ambient += gl_frontlightproduct[light].ambient; void main(void) vec3 ray_origin = mix(point, vec3(0., 0., 0.), perspective); vec3 ray_direction = mix(vec3(0., 0., 1.), normalize(view_direction), perspective); vec3 sphere_direction = mix(ray_origin - sphere_center, sphere_center, perspective); // Calculate sphere-ray intersection float b = mix(dot(sphere_direction, ray_direction), dot(ray_direction, sphere_direction), perspective); float position = b * b + radius2 - dot(sphere_direction, sphere_direction); // Check if the ray missed the sphere if (position < 0.0) discard; if (position < 0.1) // Calculate nearest point of intersection float nearest = mix(sqrt(position) - b, b - sqrt(position), perspective); // Calculate intersection point on the sphere surface. The ray // origin is at the quad (center point), so we need to project // back towards the user to get the front face. vec3 ipoint = nearest * ray_direction + ray_origin; // Calculate normal at the intersection point vec3 N = normalize(ipoint - sphere_center); // Calculate depth in fragment space vec2 clipzw = ipoint.z * gl_projectionmatrix[2].zw + gl_projectionmatrix[3].zw; gl_fragdepth = 0.5 + 0.5 * clipzw.x / clipzw.y;

18 // Calculate lighting vec4 diffuse = vec4(0, 0, 0, 1); vec4 ambient = vec4(0, 0, 0, 1); vec4 specular = vec4(0, 0, 0, 1); getlight(0, N, ambient, diffuse, specular); getlight(1, N, ambient, diffuse, specular); ambient.w = 1.; diffuse.w = 1.; specular.w = 1.; // Calculate fog // No fogging float fog = fogging[0]; // Linear fog fog += mix(0.0, clamp((gl_fog.end - gl_fogfragcoord) * gl_fog.scale, 0.0, 1.0), fogging[1]); // Exp fog fog += mix(0.0, clamp(exp(-gl_fog.density * gl_fogfragcoord), 0.0, 1.0), fogging[2]); // Exp^2 fog: exp(x) = 2^(x/log(2)) fog += mix(0.0, clamp(exp2(-gl_fog.density * gl_fog.density * gl_fogfragcoord * gl_fogfragcoord * INV_LOG2), 0.0, 1.0), fogging[3]); // Calculate final color gl_fragcolor = mix(gl_fog.color, color * (diffuse + ambient + gl_frontmaterial.emission) + specular, fog); else gl_fragcolor = vec4(0., 0., 0., 1.); Example 01: Outline fragment shader

19 Example 02: X This example puts an X on all of the spheres. This shader makes use of the up and right data which is passed into the vertex shader. Since these values are not exported from the vertex shader in the standard shaders, this shader requires both a new vertex shader and a new fragment shader. // Vertex shader uniform vec3 right_vector; uniform vec3 up_vector; varying vec4 color; varying vec3 view_direction; varying vec3 sphere_center; varying float radius2; varying vec3 point; varying float u1; varying float r1;

20 void main(void) // Get billboard attributes float right = gl_multitexcoord0.x; float up = gl_multitexcoord0.y; float radius = gl_multitexcoord0.z; radius2 = radius * radius; // compute squared radius u1 = up; r1 = right; // We need to project the vertex out to the edge of the square, which // is the following distance: // float corner_distance = sqrt(2.0 * radius2); // but since we need to normalize the corner vector computed below // which has length sqrt(2.0), we can simply use radius as corner distance // to compute vertex position of screen-oriented quad. // Compute corner vector vec3 corner_direction = up * up_vector + right * right_vector; // Calculate vertex of screen-oriented quad (billboard) vec4 vertex = vec4(gl_vertex.xyz + radius * corner_direction, gl_vertex.w); // Calculate vertex position in modelview space vec4 eye_space_pos = gl_modelviewmatrix * vertex; // Compute sphere position in modelview space vec4 tmppos = gl_modelviewmatrix * gl_vertex; sphere_center = vec3(tmppos) / tmppos.w; // Compute ray direction and origin point point = vec3(eye_space_pos) / eye_space_pos.w; view_direction = normalize(point); // Pass fog coordinate gl_fogfragcoord = abs(sphere_center.z); // Pass the transformed vertex for clipping plane calculations gl_clipvertex = eye_space_pos; // Pass color color = gl_color; // Pass transformed vertex gl_position = gl_modelviewprojectionmatrix * vertex;

21 Example 02: X vertex shader Notice that we are simply copying the up and right variables to u1 and r1. In the fragment shader, we produce a cheap unlighted effect for the X by inverting the normal. // Fragment shader // 0 is no fog, 1 is linear, 2 is exp, 3 is exp2 uniform float fogging[4]; uniform float perspective; varying vec4 color; varying vec3 view_direction; varying vec3 sphere_center; varying float radius2; varying vec3 point; varying float u1; varying float r1; const float INV_LOG2 = 1.442695; void getlight(in int light, in vec3 N, inout vec4 ambient, inout vec4 diffuse, inout vec4 specular) vec3 L = normalize(gl_lightsource[light].position.xyz); vec3 H = normalize(gl_lightsource[light].halfvector.xyz); diffuse += max(0.0, dot(n, L)) * gl_frontlightproduct[light].diffuse; specular += pow(max(0.0, dot(n, H)), gl_frontmaterial.shininess) * gl_frontlightproduct[light].specular; ambient += gl_frontlightproduct[light].ambient; void main(void) vec3 ray_origin = mix(point, vec3(0., 0., 0.), perspective); vec3 ray_direction = mix(vec3(0., 0., 1.), normalize(view_direction), perspective); vec3 sphere_direction = mix(ray_origin - sphere_center, sphere_center, perspective); // Calculate sphere-ray intersection float b = mix(dot(sphere_direction, ray_direction), dot(ray_direction, sphere_direction), perspective); float position = b * b + radius2 - dot(sphere_direction, sphere_direction);

22 // Check if the ray missed the sphere if (position < 0.0) discard; // Calculate nearest point of intersection float nearest = mix(sqrt(position) - b, b - sqrt(position), perspective); // Calculate intersection point on the sphere surface. The ray // origin is at the quad (center point), so we need to project // back towards the user to get the front face. vec3 ipoint = nearest * ray_direction + ray_origin; // Calculate normal at the intersection point vec3 N = normalize(ipoint - sphere_center); if (abs(abs(u1) - abs(r1)) < 0.1) N = -N; // Calculate depth in fragment space vec2 clipzw = ipoint.z * gl_projectionmatrix[2].zw + gl_projectionmatrix[3].zw; gl_fragdepth = 0.5 + 0.5 * clipzw.x / clipzw.y; // Calculate lighting vec4 diffuse = vec4(0, 0, 0, 1); vec4 ambient = vec4(0, 0, 0, 1); vec4 specular = vec4(0, 0, 0, 1); getlight(0, N, ambient, diffuse, specular); getlight(1, N, ambient, diffuse, specular); ambient.w = 1.; diffuse.w = 1.; specular.w = 1.; // Calculate fog // No fogging float fog = fogging[0]; // Linear fog fog += mix(0.0, clamp((gl_fog.end - gl_fogfragcoord) * gl_fog.scale, 0.0, 1.0), fogging[1]); // Exp fog fog += mix(0.0, clamp(exp(-gl_fog.density * gl_fogfragcoord), 0.0, 1.0), fogging[2]); // Exp^2 fog: exp(x) = 2^(x/log(2)) fog += mix(0.0, clamp(exp2(-gl_fog.density * gl_fog.density *

23 gl_fogfragcoord * gl_fogfragcoord * INV_LOG2), 0.0, 1.0), fogging[3]); // Calculate final color gl_fragcolor = mix(gl_fog.color, color * (diffuse + ambient + gl_frontmaterial.emission) + specular, fog); Example 02: X fragment shader Example 03: Yellow X on red atoms The next example is the same as the previous example, except that the X only appears on red atoms (e.g. oxygen with the element coloring scheme). We just expand the "X" test to include a color check. Instead of: vec4 color2 = color; if (abs(abs(u1) - abs(r1)) < 0.1) float factor = abs(abs(u1) - abs(r1)) * 10.; // Set the color to yellow color2 = mix(vec4(1., 1., 0., 1.), color, factor);

24 Clip from example 02 We do: vec4 color2 = color; // If the sphere is mostly red, then draw an X on it if (abs(abs(u1) - abs(r1)) < 0.1 && color.r > 0.7 && color.g < 0.3 && color.b < 0.3) float factor = abs(abs(u1) - abs(r1)) * 10.; // Set the color to yellow color2 = mix(vec4(1., 1., 0., 1.), color, factor); Example 03: Yellow X for red atoms fragment shader Example 04: Transparent atoms This effect produces a cheesy transparency (50% transparency) on red atoms. We simply discard every other pixel for red atoms. This example uses the standard vertex

25 shader, so only the fragment shader is shown. // Fragment shader // 0 is no fog, 1 is linear, 2 is exp, 3 is exp2 uniform float fogging[4]; uniform float perspective; varying vec4 color; varying vec3 view_direction; varying vec3 sphere_center; varying float radius2; varying float depth_level; varying vec3 point; const float INV_LOG2 = 1.442695; void getlight(in int light, in vec3 N, inout vec4 ambient, inout vec4 diffuse, inout vec4 specular) vec3 L = normalize(gl_lightsource[light].position.xyz); vec3 H = normalize(gl_lightsource[light].halfvector.xyz); diffuse += max(0.0, dot(n, L)) * gl_frontlightproduct[light].diffuse; specular += pow(max(0.0, dot(n, H)), gl_frontmaterial.shininess) * gl_frontlightproduct[light].specular; ambient += gl_frontlightproduct[light].ambient; void main(void) vec3 ray_origin = mix(point, vec3(0., 0., 0.), perspective); vec3 ray_direction = mix(vec3(0., 0., 1.), normalize(view_direction), perspective); vec3 sphere_direction = mix(ray_origin - sphere_center, sphere_center, perspective); // Calculate sphere-ray intersection float b = mix(dot(sphere_direction, ray_direction), dot(ray_direction, sphere_direction), perspective); float position = b * b + radius2 - dot(sphere_direction, sphere_direction); // Check if the ray missed the sphere if (position < 0.0) discard; // Draw a 50% cheesy transparency effect on red (oxygen) atoms if (color.r > 0.7 && color.g < 0.3 && color.b < 0.3 && (int(abs(gl_fragcoord.x + gl_fragcoord.y)) % 2) == 1)

26 discard; // Calculate nearest point of intersection float nearest = mix(sqrt(position) - b, b - sqrt(position), perspective); // Calculate intersection point on the sphere surface. The ray // origin is at the quad (center point), so we need to project // back towards the user to get the front face. vec3 ipoint = nearest * ray_direction + ray_origin; // Calculate normal at the intersection point vec3 N = normalize(ipoint - sphere_center); // Calculate depth in fragment space vec2 clipzw = ipoint.z * gl_projectionmatrix[2].zw + gl_projectionmatrix[3].zw; gl_fragdepth = 0.5 + 0.5 * clipzw.x / clipzw.y; // Calculate lighting vec4 diffuse = vec4(0, 0, 0, 1); vec4 ambient = vec4(0, 0, 0, 1); vec4 specular = vec4(0, 0, 0, 1); getlight(0, N, ambient, diffuse, specular); getlight(1, N, ambient, diffuse, specular); ambient.w = 1.; diffuse.w = 1.; specular.w = 1.; // Calculate fog // No fogging float fog = fogging[0]; // Linear fog fog += mix(0.0, clamp((gl_fog.end - gl_fogfragcoord) * gl_fog.scale, 0.0, 1.0), fogging[1]); // Exp fog fog += mix(0.0, clamp(exp(-gl_fog.density * gl_fogfragcoord), 0.0, 1.0), fogging[2]); // Exp^2 fog: exp(x) = 2^(x/log(2)) fog += mix(0.0, clamp(exp2(-gl_fog.density * gl_fog.density * gl_fogfragcoord * gl_fogfragcoord * INV_LOG2), 0.0, 1.0), fogging[3]); // Calculate final color gl_fragcolor = mix(gl_fog.color, color * (diffuse + ambient +

27 gl_frontmaterial.emission) + specular, fog); Example 04: Transparent red atom fragment shader Resources This is a list of useful resources for GLSL. OpenGL v3.2 (GLSL 1.5) quick reference card: http://www.khronos.org/files/opengl-quick-reference-card.pdf GLSL v1.20 quick reference card: http://www.cs.brown.edu/courses/cs123/resources/glslquickref.pdf Shader Toy (allows experimenting with different shaders in very recent web browsers): http://www.iquilezles.org/apps/shadertoy/