Ray tracing hardware

From Wikipedia, the free encyclopedia
  (Redirected from Ray Processing Unit)
Jump to: navigation, search

Ray tracing hardware is special purpose computer hardware designed for accelerating ray tracing calculations.

Introduction: Ray tracing and rasterization[edit]

The problem of rendering 3D graphics can be conceptually presented as finding all intersections between a set of "primitives" (typically triangles or polygons) and a set of "rays" (typically one or more per pixel).[1]

Up to 2010 all typical graphic acceleration boards, called graphics processing units (GPUs), use rasterization algorithms. The ray tracing algorithm solves the rendering problem in a different way. In each step, it finds all intersections of a ray with a set of relevant primitives of the scene.

Both approaches have their own benefits and drawbacks. Rasterization can be performed using devices based on a stream computing model, one triangle at the time, and access to the complete scene is needed only once.[note 1] The drawback of rasterization is that non-local effects, required for an accurate simulation of a scene, such as reflections and shadows are difficult; and refractions[2] nearly impossible to compute.

The ray tracing algorithm is inherently suitable for scaling by parallelization of individual ray renders.[3] However anything other than ray casting requires recursion of the ray tracing algorithm (and random access to the scene graph) to complete their analysis,[4] since reflected, refracted, and scattered rays require that various parts of the scene be re-accessed in a way not easily predicted. But it can easily compute various kinds of physically correct effects, providing much more realistic impression than rasterization.[note 2]

The complexity of a well implemented ray tracing algorithm scales logarithmically;[note 3] this is due to objects (triangles and collections of triangles) being placed into BSP trees or similar structures, and only being analyzed if a ray intersects with the bounding volume of the binary space partition.[5][note 4]

Architecture and methods[edit]

Implementations[edit]

Various implementations of ray tracing hardware have been created, both experimental and commercial:

  • (2002–2009) ART VPS company (founded 2002[6]), situated in the UK, sold ray tracing hardware for off-line rendering. The hardware used multiple specialized processors that accelerated ray-triangle intersection tests. Software provided integration with Maya (see Autodesk Maya) and Max (see Autodesk 3ds Max) data formats, and utilized the Renderman scene description language for sending data to the processors (the .RIB or Renderman Interface Bytestream file format).[7] As of 2010, ARTVPS no longer produces ray tracing hardware but continues to produce rendering software.[6]
  • (2002) The computer graphics laboratory at Saarland University headed by Dr. -Ing Slusallek has produced prototype ray tracing hardware including the FPGA based fixed function data driven SaarCOR (Saarbrücken’s Coherence Optimized Ray Tracer) chip[8][9][10] and a more advanced programmable (2005) processor, the Ray Processing Unit (RPU)[11]
  • (1996) Researchers at Princeton university proposed using DSPs to build a hardware unit for ray tracing acceleration, named "TigerSHARK"[12]
  • Implementations of volume rendering using ray tracing algorithms on custom hardware have also been proposed : (2002) VIZARD II[13] or built (1999) : vg500 / VolumePro ASIC based system[14][15]
  • Caustic Graphics[16] have produced a plug in card, the "CausticOne" (2010), that accelerates global illumination and other ray based rendering processes when coupled to a PC CPU and GPU. The hardware is designed to organize scattered rays (typically produced by global illumination problems) into more coherent sets (lower spatial or angular spread) for further processing by an external processor.[17]
  • Siliconarts[18] developed a dedicated real-time ray tracing hardware (2010). RayCore (2011), which is the world's first real-time ray tracing semiconductor IP, was announced.

References, notes and further reading[edit]

Notes[edit]

  1. ^ For additional visualisations such as shadows, or reflections such as produced by a large flat body of water an addition pass of the scene graph is required for each effect
  2. ^ Rasterisation methods are capable of generating realistic shadows (including shadows produced by partially transparent objects), and plane reflections easily (as of 2010), but does not easily implement reflections from non planar surfaces (excluding approximations using normal maps) or refractions.
  3. ^ That is if X is the number of triangles, then the number of computations to complete the scene is proportional to log(X)
  4. ^ The same methods can be used in rasterization, in a simplistic implemention culling is limited to those BSP partitions that lie within the much larger viewing frustum ( more advanced implementations including those that implement occlusion culling or predicated rendering scale better than linearly for complex (especially high occluded) scenes (Note in common API's : DirectX 10 D3D10_QUERY_OCCLUSION_PREDICATE [1] , in OpenGL 3.0 HP_occlusion_query ). With ray tracing the viewing frustum is replaced by the volume enclosed by a single ray (or ray bundle)

References[edit]

  1. ^ Introduction to real time raytracing Course notes, Course 41 , Philipp Slusallek, Peter Shirley, Bill Mark, Gordon Stoll, Ingo Wald , SIGGRAPH 2005 , (powerpoint presentation), Slide 26 :Comparison Rasterization vs. Ray Tracing (Definitions) graphics.cg.uni-saarland.de
  2. ^ Chris Wyman's Research: Interactive Refractions Department of Computer Science at The University of Iowa , www.cs.uiowa.edu
  3. ^ SaarCOR —A Hardware Architecture for Ray Tracing, Jörg Schmittler, Ingo Wald, Philipp Slusallek, Section 2, "Previous work"
  4. ^ SaarCOR —A Hardware Architecture for Ray Tracing, Jörg Schmittler, Ingo Wald, Philipp Slusallek, Section 3, "The Ray Tracing Algorithm"
  5. ^ Ray Tracing and Gaming - One Year Later Daniel Pohl , 17/1/2008 , via "PCperspective" , www.pcper.com
  6. ^ a b About ArtVPS www.artvps
  7. ^ ALL ABOUT ARTVPS, PURE CARDS, RENDERDRIVES and RAYBOX Mark Segasby (Protograph Ltd) , www.protograph.co.uk
  8. ^ "SaarCOR - A Hardware Architekture for Ray Tracing". 
  9. ^ "SaarCOR —A Hardware Architecture for Ray Tracing". Graphics Hardware (Computer Graphics Group, Saarland University, Germany). 2002), pp. 1–11 , Jörg Schmittler, Ingo Wald, Philipp Slusallek.  Check date values in: |date= (help)
  10. ^ Jörg Schmittler, Sven Woop, Daniel Wagner, Wolfgang J. Paul, Philipp Slusallek (2004). "Realtime Ray Tracing of Dynamic Scenes on an FPGA Chip". Graphics Hardware (Computer Science, Saarland University, Germany). CiteSeerX: 10.1.1.72.2947. 
  11. ^ Sven Woop, Jorg Schmittler, Philipp Slusallek. "RPU: A Programmable Ray Processing Unit for Realtime Ray Tracing". Saarland University. 
  12. ^ A Hardware Accelerated Ray-tracing Engine Greg Humphreys, C. Scott Ananian (Independent Work) , Department of Computer Science, Princeton University, 14/5/1996 , cscott.net
  13. ^ VIZARD II: An FPGA-based Interactive Volume Rendering System Urs Kanus, Gregor Wetekam, Johannes Hirche, Michael Meißner, University of Tubingen / Philips Research Hamburg , Graphics Hardware (2002), pp. 1–11 , via www.doggetts.org
  14. ^ The vg500 Real-Time Ray-Casting ASIC Hanspeter Pfister , MERL - A Mitsubishi Electric Research Laboratory , Cambridge MA (USA) www.hotchips.org
  15. ^ Hanspeter Pfister, Jan Hardenbergh, Jim Knittely, Hugh Lauery, Larry Seiler (April 1999). "The VolumePro Real-Time Ray-Casting System". Mitsubishi Electric. CiteSeerX: 10.1.1.69.4091. 
  16. ^ Caustic Graphics company website www.caustic.com
  17. ^ Reinventing Ray Tracing 15/7/2009 , Jonathan Erickson interview with James McCombe of Caustic Graphics , www.drdobbs.com
  18. ^ Siliconarts company website www.siliconarts.com

Further reading[edit]