Loading in 5 sec....

CS 551 / 645: Introductory Computer GraphicsPowerPoint Presentation

CS 551 / 645: Introductory Computer Graphics

- 102 Views
- Uploaded on
- Presentation posted in: General

CS 551 / 645: Introductory Computer Graphics

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

CS 551 / 645: Introductory Computer Graphics

Ray Tracing

David Luebke7/30/2014

- Assignment 5: Intel okay

David Luebke7/30/2014

- What is not realistic about the following images?

David Luebke7/30/2014

David Luebke7/30/2014

David Luebke7/30/2014

David Luebke7/30/2014

David Luebke7/30/2014

David Luebke7/30/2014

Crude light-surface interaction model

Strictly local illumination model

- A big part of realism is realistic lighting
- Is Phong’s lighting model realistic?
- Empirical specular term
- “Ambient” term
- No shadows
- No surface interreflection

David Luebke7/30/2014

- Realistic lighting is global, not local
- Surfaces shadow each other
- Surfaces illuminate each other

- Two long-time approaches
- Ray-tracing: simulate light-ray optics
- Radiosity: simulate physics of light transfer

David Luebke7/30/2014

- To determine visible surfaces at each pixel:
- Cast a ray from the eyepoint through the center of the pixel
- Intersect the ray with all objects in the scene
- Whatever it hits first is the visible object

- This is called ray casting

David Luebke7/30/2014

- An example:

Eyepoint

Screen

Scene

David Luebke7/30/2014

- Obvious extension:
- Spawn additional rays off reflective surfaces
- Spawn transmitted rays through transparent surfaces

- Leads to recursive ray tracing

Secondary Rays

Primary Ray

David Luebke7/30/2014

- Slightly less obvious extension:
- Trace a ray from point of intersection to light source
- If ray hits anything before light source, object is in shadow
- These are called shadow rays

David Luebke7/30/2014

- Ray tracing is simple
- No clipping, perspective projection matrices, scan conversion of polygons

- Ray tracing is powerful
- Hidden surface problem
- Shadow computation
- Reflection/refraction

- Ray tracing is slow
- Complexity proportional to # of pixels
- Typical screen ~ 1,000,000 pixels
- Typical scene « 1,000,000 polygons

David Luebke7/30/2014

David Luebke7/30/2014

Pixel

ImagePlane

David Luebke7/30/2014

“Direct” Ray To Eye

David Luebke7/30/2014

“Indirect” Ray To Eye

David Luebke7/30/2014

- Physically, we’re interested in path of light rays from light source to eye.
- In practice, we trace rays backwards from eye to source (Why?)

David Luebke7/30/2014

- Physically, we’re interested in path of light rays from light source to eye.
- In practice, we trace rays backwards from eye to source (Why?)
- Computational efficiency: we want the finite subset of rays that leave source, bounce around, and pass through eye
- Can’t predict where a ray will go, so start with rays we know reach eye

David Luebke7/30/2014

- Function TraceRay()Recursively trace ray Rand return resulting color C
- ifRintersects any objects then
- Find nearest object O
- Find local color contribution
- Spawn reflected and transmitted rays, using TraceRay() to find resulting colors
- Combine colors; return result

- else
- return background color

- ifRintersects any objects then

David Luebke7/30/2014

Object allObs[];

Color image[];

RayTraceScene()

allObs = initObjects();

for (Yall rows in image)

for (X all pixels in row)

Ray R = calcPrimaryRay(X,Y);

image[X,Y] = TraceRay(R);display(image);

David Luebke7/30/2014

Color TraceRay(Ray R)

ifrayHitsObjects(R) then

Color localC, reflectC, refractC;

Object O = findNearestObject(R);

localC = shade(O,R);

Ray reflectedRay = calcReflect(O,R)

Ray refractedRay = calcRefract(O,R)

reflectC = TraceRay(reflectedRay);

refractC = TraceRay(refractedRay);

return localC reflectC refractC

else returnbackgroundColor

David Luebke7/30/2014

Color TraceRay(Ray R)

ifrayHitsObjects(R) then

Color localC, reflectC, refractC;

Object O = findNearestObject(R);

localC = shade(O,R);

Ray reflectedRay = calcReflect(O,R)

Ray refractedRay = calcRefract(O,R)

reflectC = TraceRay(reflectedRay);

refractC = TraceRay(refractedRay);

return localC reflectC refractC

else returnbackgroundColor

David Luebke7/30/2014

- Given a ray and a list of objects, what objects (if any) intersect the ray?
- Query: Does ray R intersect object O?
- How to represent ray?
- What kind of object?
- Sphere
- Polygon
- Box
- General quadric

David Luebke7/30/2014

- How might we represent rays?
- We represent a ray parametrically:
- A starting point O
- A direction vector D
- A scalar t

R = O+ tD

O

t < 0

t = 1

t > 1

D

David Luebke7/30/2014

- Ray R = O + tD
x = Ox + t Dx

y = Oy + t Dy

z = Oz + t Dz

- Sphere at (l, m, n) of radius r is:
(x - l)2 + (y - m)2 + (z - n)2 = r 2

- Substitute for x,y,z and solve for t…

David Luebke7/30/2014

- Works out as a quadratic equation:
at2 + bt + c = 0

where

a = Dx2 + Dy2 + Dz2

b =2Dx(Ox - l) + 2Dy(Oy - m) + 2Dz(Oz - n)

c = l2 + m2 + n2 + Ox2 + Oy2 + Oz2 - 2(l Ox + m Oy + n Oz + r2)

David Luebke7/30/2014

- If solving for t gives no real roots: ray does not intersect sphere
- If solving gives 1 real root r, ray grazes sphere where t = r
- If solving gives 2 real roots (r1, r2), ray intersects sphere at t = r1& t = r2
- Ignore negative values
- Smallest value is first intersection

David Luebke7/30/2014

- Find intersection point Pi = (xi, yi, zi) by plugging t back into ray equation
- Find normal at intersection point by subtracting sphere center from Pi and normalizing:
- When will we need the normal? When not?

David Luebke7/30/2014

- Polygons are the most common model representation
- Can render in hardware
- Lowest common denominator

- Basic approach:
- Find plane equation of polygon
- Find point of intersection between ray and plane
- Does polygon contain intersection point?

David Luebke7/30/2014

d

- Find plane equation of polygon:ax + by + cz + d = 0
- Remember how?
N = [a, b, c]

d = N P1

y

N

P2

P1

x

David Luebke7/30/2014

- Find intersection of ray and plane:
t = -(aOx + bOy + cOz + d) / (aDx + bDy + cDz)

- Does polygon contain intersection point Pi ?
- One simple algorithm:
- Draw line from Pi to each polygon vertex
- Measure angles between lines (how?)
- If sum of angles between lines is 360°, polygon contains Pi

- Slow — better algorithms available

- One simple algorithm:

David Luebke7/30/2014

- Often want to find whether a ray hits an axis-aligned box (Why?)
- One way:
- Intersect ray with pairs of parallel planes that form box
- If intervals of intersection overlap, the ray intersects the volume.

David Luebke7/30/2014

- Simple idea:
- Where a ray intersects a surface, send a shadow ray to each light source
- If the shadow ray hits any surface before the light source, ignore light

- Q: how much extra work is involved?
- A: each ray-surface intersection now spawns n + 2 rays, n = # light sources
- Remember: intersections 95% of work

David Luebke7/30/2014

- Some problems with using shadow rays as described:
- Lots of computation
- Infinitely sharp shadows
- No semitransparent object shadows

David Luebke7/30/2014

- Some problems with using shadow rays as described:
- Lots of computation
- Infinitely sharp shadows
- No semitransparent object shadows

David Luebke7/30/2014

Light Buffer

- Light buffer (Haines/Greenberg, 86)
- Precompute lists of polygons surrounding light source in all directions
- Sort each list by distance to light source
- Now shadow ray need only be intersected with appropriate list!

ShadowRay

Occluding Polys

Current Intersection Point

David Luebke7/30/2014

- Some problems with using shadow rays as described:
- Lots of computation
- Infinitely sharp shadows
- No semitransparent object shadows

David Luebke7/30/2014

- Why are the shadows sharp?
- A: Infinitely small point light sources
- What can we do about it?
- A: Implement area light sources
- How?

David Luebke7/30/2014

- Could trace a conical beam from point of intersection to light source:
- Track portion of beam blocked by occluding polygons:

30% blockage

David Luebke7/30/2014

- Too hard! Approximate instead:
- Sample the light source over its area and take weighted average:

50% blockage

David Luebke7/30/2014

- Disadvantages:
- Less accurate (50% vs. 30% blockage)
- Oops! Just quadrupled (at least) number of shadow rays

- Moral of the story:
- Soft shadows are very expensive in ray tracing

David Luebke7/30/2014

- Some problems with using shadow rays as described:
- Lots of computation
- Infinitely sharp shadows
- No semitransparent object shadows

David Luebke7/30/2014

- In principle:
- Translucent colored objects should cast colored shadows
- Translucent curved objects should create refractive caustics

- In practice:
- Can fake colored shadows by attenuating color with distance
- Caustics need backward ray tracing

David Luebke7/30/2014

- Intersect rays faster
- Shoot fewer rays
- Shoot “smarter” rays

David Luebke7/30/2014

- Intersect rays faster
- Shoot fewer rays
- Shoot “smarter” rays

David Luebke7/30/2014

- Bounding volumes
- Spatial partitions
- Reordering ray intersection tests
- Optimizing intersection tests

David Luebke7/30/2014

- Bounding volumes
- Idea: before intersecting a ray with a collection of objects, test it against one simple object that bounds the collection

7

7

5

5

3

3

1

1

8

8

6

6

0

0

9

9

2

2

4

4

David Luebke7/30/2014

- Hierarchical bounding volumes
- Group nearby volumes hierarchically
- Test rays against hierarchy top-down

David Luebke7/30/2014

- Different bounding volumes
- Spheres
- Cheap intersection test
- Poor fit
- Tough to calculate optimal clustering

- Axis-aligned bounding boxes (AABBs)
- Relatively cheap intersection test
- Usually better fit
- Trivial to calculate clustering

- Spheres

David Luebke7/30/2014

- More bounding volumes
- Oriented bounding boxes (OBBs)
- Medium-expensive intersection test
- Very good fit (asymptotically better)
- Medium-difficult to calculate clustering

- Slabs (parallel planes)
- Comparatively expensive
- Very good fit
- Difficult to calculate good clustering

- Oriented bounding boxes (OBBs)

David Luebke7/30/2014

- Hierarchical bounding volumes surround objects in the scene with (possibly overlapping) volumes
- Spatialpartitioning techniques classify all space into non-overlapping portions

David Luebke7/30/2014

- Example spatial partitions:
- Uniform grid (2-D or 3-D)
- Octree
- k-D tree
- BSP-tree

David Luebke7/30/2014

- Uniform grid pros:
- Very simple and fast to generate
- Very simple and fast to trace rays across (How?)

- Uniform grid cons:
- Not adaptive
- Wastes storage on empty space
- Assumes uniform spread of data

- Not adaptive

David Luebke7/30/2014

- Octree pros:
- Simple to generate
- Adaptive

- Octree cons:
- Nontrivial to trace rays across
- Adaptive only in scale

David Luebke7/30/2014

- k-D tree pros:
- Moderately simple to generate
- More adaptive than octrees

- k-D tree cons:
- Less efficient to trace rays across
- Moderately complex data structure

David Luebke7/30/2014

- BSP tree pros:
- Extremely adaptive
- Simple & elegant data structure

- BSP tree cons:
- Very hard to create optimum BSP
- Splitting planes can explode storage
- Simple but slow to trace rays across

David Luebke7/30/2014

- Caching ray hits (esp. shadow rays)
- Memory-coherent ray tracing

David Luebke7/30/2014

- Fine-tune the math!
- Share subexpressions
- Precompute everything possible

- Code with care
- Even use assembly, if necessary

David Luebke7/30/2014