DOCSLIB.ORG

Accelerating Ray Tracing Using Optix

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Accelerating Ray Tracing Using Optix RAY TRACING WITH OPTIX A TUTORIAL FOR DEVELOPERS David McAllister, James Bigler, Brandon Lloyd RAY TRACING IN THE ABSTRACT . Given a ray (O, D) and a geometric dataset find — any hit — closest hit ? — all hits . Current datasets ~1M -> 100M primitives, usually triangles . Use a spatial data structure optimized for these operations . Datasets can also include GB of other data like textures OPTIX RAY TRACING TALKS AT GTC . Nvidia Keynote – Tue. 9:00 . Pixar Keynote – Wed. 11:00 . S4260 - Game Physics and Graphics APIs for Scientific Computing – Tue. 16:00 . S4359 - EM Wave Propagation Using OptiX for Simulation of Car-to-Car-Comm – Wed. 14:00 . S4697 - Realtime Preview For VFX: Challenges and Rewards – Wed. 14:00 . S4690 - Implementing OptiX Ray Tracing Features into FurryBall GPU Renderer – Wed. 17:30 . S4597 - Advanced OptiX Programming – Thur. 9:00 . S4400 - Petascale Molecular Ray Tracing: Accelerating VMD/Tachyon with OptiX – Thur. 10:00 . S4312 - QUIC EnvSim: Radiative Heat Transfer in Vegetative and Urban Environments with NVIDIA OptiX, Thur. 14:30 RENDERING WITH RAY TRACING RAY CASTING (APPEL, 1968) RECURSIVE RAY TRACING (WHITTED, 1980) 6 DISTRIBUTION RAY TRACING (COOK, 1984) 7 PATH TRACING (KAJIYA, 1986) 8 WHY RAY TRACING? . Ray tracing unifies rendering of visual phenomena — fewer algorithms with fewer interactions between algorithms . Easier to combine advanced visual effects robustly — soft shadows — subsurface scattering — indirect illumination — transparency — reflective & glossy surfaces — depth of field — … 9 REAL TIME PATH TRACING . What would it take? . GeForce GTX Titan: — 4 rays / sample — 400M rays / second — 50 samples / pixel — Need 30X speedup — 2M pixels / frame — 30 frames / second — 12B rays / second 1 shading sample 9 shading samples 18 shading samples 36 shading samples 72 shading samples 144 shading samples 1 AA sample 1 AA sample 2 AA samples 4 AA samples 8 AA samples 16 AA samples RAY TRACING REGIMES Real-time Interactive Batch Computational Power today HOW TO OPTIMIZE RAY TRACING .Better hardware (GPUs) .Better software (Algorithmic improvement) .Better middleware (Tune for the architecture) GPUS – THE PROCESSOR FOR RAY TRACING . Abundant parallelism, massive computational power . GPUs excel at shading . Opportunity for hybrid algorithms ACCELERATION STRUCTURES OPTIX PRIME . Specialized for ray tracing (no shading) . Replaces rtuTraversal (rtuTraversal is still supported) . Improved performance — Uses latest algorithms from NVIDIA Research . ray tracing kernels [Aila and Laine 2009; Aila et al. 2012] . Treelet Reordering BVH (TRBVH) [Karras 2013] — Can use CUDA buffers as input/output — Support for asynchronous computation . Designed with an eye towards future features API OVERVIEW . C API with C++ wrappers . API Objects — Context — Buffer Descriptor — Model — Query CONTEXT . Context tracks other API objects and encapsulates the ray tracing backend . Creating a context RTPresult rtpContextCreate(RTPcontexttype type, RTPcontext* context) . Context types RTP_CONTEXT_TYPE_CPU RTP_CONTEXT_TYPE_CUDA . Default for CUDA backend uses all available GPUs — Selects “Primary GPU” and makes it the current device — Primary GPU builds acceleration structure CONTEXT . Selecting devices: rtpContextSetCudaDeviceNumbers( RTPcontext context, int deviceCount, const int* deviceNumbers ) — First device is used as the primary GPU . Destroying the context — destroys objects created by the context — synchronizes the CPU and GPU BUFFER DESCRIPTOR . Buffers are allocated by the application . Buffer descriptors encapsulate Context information about the buffers rtpBufferDescCreate( RTPcontext context, BufferDesc RTPbufferformat format, RTPbuffertype type, void* buffer, RTPbufferdesc* desc ) . Specify region of buffer to use (in elements) rtpBufferDescSetRange( RTPbufferdesc desc, int begin, int end ) BUFFER DESCRIPTOR . Variable stride supported for vertex format rtpBufferDescSetStride — Allows for vertex attributes BUFFER DESCRIPTOR . Formats RTP_BUFFER_FORMAT_INDICES_INT3 RTP_BUFFER_FORMAT_VERTEX_FLOAT3, RTP_BUFFER_FORMAT_RAY_ORIGIN_DIRECTION, RTP_BUFFER_FORMAT_RAY_ORIGIN_TMIN_DIRECTION_TMAX, RTP_BUFFER_FORMAT_HIT_T_TRIID_U_V RTP_BUFFER_FORMAT_HIT_T_TRIID … . Types RTP_BUFFER_TYPE_HOST RTP_BUFFER_TYPE_CUDA_LINEAR MODEL . A model is a set of triangles combined with an acceleration data structure Context rtpModelCreate rtpModelSetTriangles indices rtpModelUpdate BufferDesc Model . Asynchronous update vertices BufferDesc rtpModelFinish rtpModelGetFinished QUERY . Queries perform the ray tracing on a model rtpQueryCreate Context rtpQuerySetRays rtpQuerySetHits indices BufferDesc rtpQueryExecute Model . Query types vertices BufferDesc RTP_QUERY_TYPE_ANY RTP_QUERY_TYPE_CLOSEST rays BufferDesc . Asynchronous query Query hits BufferDesc rtpQueryFinish rtpQueryGetFinished BUILD PERFORMANCE 200 180 160 140 120 100 80 60 40 Speedup over SBVH Speedup 20 0 RAY TRACING PERFORMANCE 3.0 2.5 2.0 rtuTraversal 1.5 1.0 0.5 Speedup over Speedup 0.0 RAYTRACING PERFORMANCE 350.0 300.0 250.0 200.0 150.0 /s for diffuse rays diffuse /s for 100.0 50.0 Mrays 0.0 FUTURE . Features we want to implement — Animation support (refit/refine) — Instancing — Large-model optimizations ART AND ANIMATION STUDIOS . Jan Tománek, CEO . FurryBall 4.6 .6 OPTIX GOALS . High performance ray tracing . Simpler ray tracing . Hide GPU-specific details . Express most ray tracing algorithms . Leverage CUDA architecture and compiler infrastructure GENERAL PURPOSE RAY TRACING . Rendering, baking, collision detection, A.I. queries, etc. Modern shader-centric, stateless and bindless design . Is not a renderer but can implement many types of renderers . Algorithm agnostic — User defined ray data — Programmable intersection — Interoperate with rasterization pipeline HIGHLY PROGRAMMABLE . Shading with arbitrary ray payloads . Ray generation/framebuffer operations — cameras, data unpacking, etc. Programmable intersection — triangles, NURBS, implicit surfaces, etc. EASY TO PROGRAM . Write single ray code (no exposed ray packets) . No need to rewrite shaders to target different hardware OTHER OPTIX FEATURES . OptiX node graph — Programmable traversal — Instancing — Dynamic scenes . Double precision arithmetic . Interop with CUDA, OpenGL and D3D — Textures, VBOs, etc. — Hybrid rasterization and ray tracing DOCS.NVIDIA.COM HOW OPTIX LINKS YOUR CODE Ray Generation Acceleration Structures DRAM I/F DRAM Material Shading Material I/F DRAM Material Shading JIT I/F DRAM HOST I/F HOST Compiler L2 I/F DRAM Object Intersection Thread Giga Material I/F DRAM Material Shading Scheduling I/F DRAM CUDA C shaders from OptiX API GPU Execution via user programs CUDA OVERVIEW – API OBJECTS Acceleration Program Group Variable GeometryGroup Context Transform GeometryInstance Selector Buffer Geometry TextureSampler Material API OBJECTS – CONTEXT . Manages API Object State — Program Loading Context — Validation and Compilation Ray Gen Programs . Manages Acceleration Structures Callable Programs Exception Programs — Building and Updating Miss Programs User Variables . Provides Entry Points into the system — rtContextLaunch*D() ENTRY POINTS AND RAY TYPES Context Entry Point 1 Entry Point 2 Ray Generation 1 Ray Generation 2 Exception 1 Exception 2 Trace ENTRY POINTS AND RAY TYPES Trace Material Ray Type Ray Shading 0 Closest Hit Any Hit 1 Closest Hit Any Hit Material Programs 2 Closest Hit Any Hit 3 Closest Hit Any Hit API OBJECTS – NODES . Nodes contain children Group — Other nodes — Geometry Instances GeometryGroup . Transforms hold matrices — Applied to all children Transform . Selectors have Visit programs — Provide programmable selection of children Selector — Similar to “switch nodes” — Can implement LOD systems Acceleration . Acceleration Structures — Builds over children of attached node THE OBJECT HIERARCHY Context Group GeometryGroup GeometryGroup GeometryInstance GeometryInstance GeometryInstance GeometryInstance API OBJECTS – GEOMETRY . GeometryInstance binds: — Geometry object GeometryInstance — A collection of Materials . Indexed by argument from intersection . Geometry — A collection of primitives Geometry Material — Intersection Program — Bounding Box Program Material . Material — Any Hit Program Material — Closest Hit Program DEFORMABLE OBJECTS 2. Groups and Acceleration Marked Dirty Context Group Acceleration GeometryGroup 1. Primitives Deform GeometryInstance 3. Context updates Acceleration Structures API OBJECTS – DATA MANAGEMENT . Supports 1D, 2D and 3D buffers . Buffer formats — RT_FORMAT_FLOAT3 Buffer — RT_FORMAT_UNSIGNED_BYTE4 — RT_FORMAT_USER, etc. TextureSampler . Other API Interoperability — e.g. create buffers from CUDA, OpenGL or D3D buffer objects . TextureSamplers reference Buffers — Attach buffers to MIP levels, array slices, etc. API OBJECTS – PROGRAMMABILITY . Runs on CUDA Program — Cg-like vectors plus pointers — Uses PTX, CUDA’s virtual assembly language Variable — C++ wrapper for use with NVCC compiler . Implements recursion and dynamic dispatch Callable — Intrinsic functions: rtTrace(), rtReportIntersection(), etc. Programs reference variables by name . Variables are defined by — Static initializers — Binding to API Objects in the hierarchy VARIABLES . Variables are one of: — A small primitive type (float4, matrix, ...) — A small user defined type — A handle to a buffer (1D, 2D, 3D) — A texture — A handle to a callable program — A buffer ID — A program ID VARIABLE SCOPING Context Context Definition: Color = blue GI GI Material Material GeometryInstance Definition: Color
Load more

Recommended publications
  • CUDA-SCOTTY Fast Interactive CUDA Path Tracer Using Wide Trees and Dynamic Ray Scheduling
    15-618: Parallel Computer Architecture and Programming CUDA-SCOTTY Fast Interactive CUDA Path Tracer using Wide Trees and Dynamic Ray Scheduling “Golden Dragon” TEAM MEMBERS Sai Praveen Bangaru (Andrew ID: saipravb) Sam K Thomas (Andrew ID: skthomas) Introduction Path tracing has long been the select method used by the graphics community to render photo-realistic images. It has found wide uses across several industries, and plays a major role in animation and filmmaking, with most special effects rendered using some form of Monte Carlo light transport. It comes as no surprise, then, that optimizing path tracing algorithms is a widely studied field, so much so, that it has it’s own top-tier conference (​HPG; ​High Performance Graphics). There are generally a whole spectrum of methods to increase the efficiency of path tracing. Some methods aim to create ​better sampling methods (Metropolis Light Transport), while others try to ​reduce noise​ in the final image by filtering the output ​(4D Sheared transform)​. In the spirit of the parallel programming course ​15-618​, however, we focus on a third category: system-level optimizations and leveraging hardware and algorithms that better utilize the hardware (​Wide Trees, Packet tracing, Dynamic Ray Scheduling)​. Most of these methods, understandably, focus on the ​ray-scene intersection ​part of the path tracing pipeline, since that is the main bottleneck. In the following project, we describe the implementation of a hybrid ​non-packet​ method which uses ​Wide Trees​ and ​Dynamic Ray Scheduling ​to provide an ​80x ​improvement over a ​8-threaded CPU implementation. Summary Over the course of roughly 3 weeks, we studied two ​non-packet​ BVH traversal optimizations: ​Wide Trees​, which involve non-binary BVHs for shallower BVHs and better Warp/SIMD Utilization and ​Dynamic Ray Scheduling​ which involved changing our perspective to process rays on a per-node basis rather than processing nodes on a per-ray basis.
    [Show full text]
  • Practical Path Guiding for Efficient Light-Transport Simulation
    Eurographics Symposium on Rendering 2017 Volume 36 (2017), Number 4 P. Sander and M. Zwicker (Guest Editors) Practical Path Guiding for Efficient Light-Transport Simulation Thomas Müller1;2 Markus Gross1;2 Jan Novák2 1ETH Zürich 2Disney Research Vorba et al. MSE: 0.017 Reference Ours (equal time) MSE: 0.018 Training: 5.1 min Training: 0.73 min Rendering: 4.2 min, 8932 spp Rendering: 4.2 min, 11568 spp Figure 1: Our method allows efficient guiding of path-tracing algorithms as demonstrated in the TORUS scene. We compare equal-time (4.2 min) renderings of our method (right) to the current state-of-the-art [VKv∗14, VK16] (left). Our algorithm automatically estimates how much training time is optimal, displays a rendering preview during training, and requires no parameter tuning. Despite being fully unidirectional, our method achieves similar MSE values compared to Vorba et al.’s method, which trains bidirectionally. Abstract We present a robust, unbiased technique for intelligent light-path construction in path-tracing algorithms. Inspired by existing path-guiding algorithms, our method learns an approximate representation of the scene’s spatio-directional radiance field in an unbiased and iterative manner. To that end, we propose an adaptive spatio-directional hybrid data structure, referred to as SD-tree, for storing and sampling incident radiance. The SD-tree consists of an upper part—a binary tree that partitions the 3D spatial domain of the light field—and a lower part—a quadtree that partitions the 2D directional domain. We further present a principled way to automatically budget training and rendering computations to minimize the variance of the final image.
    [Show full text]
  • GPU Developments 2018
    GPU Developments 2018 2018 GPU Developments 2018 © Copyright Jon Peddie Research 2019. All rights reserved. Reproduction in whole or in part is prohibited without written permission from Jon Peddie Research. This report is the property of Jon Peddie Research (JPR) and made available to a restricted number of clients only upon these terms and conditions. Agreement not to copy or disclose. This report and all future reports or other materials provided by JPR pursuant to this subscription (collectively, “Reports”) are protected by: (i) federal copyright, pursuant to the Copyright Act of 1976; and (ii) the nondisclosure provisions set forth immediately following. License, exclusive use, and agreement not to disclose. Reports are the trade secret property exclusively of JPR and are made available to a restricted number of clients, for their exclusive use and only upon the following terms and conditions. JPR grants site-wide license to read and utilize the information in the Reports, exclusively to the initial subscriber to the Reports, its subsidiaries, divisions, and employees (collectively, “Subscriber”). The Reports shall, at all times, be treated by Subscriber as proprietary and confidential documents, for internal use only. Subscriber agrees that it will not reproduce for or share any of the material in the Reports (“Material”) with any entity or individual other than Subscriber (“Shared Third Party”) (collectively, “Share” or “Sharing”), without the advance written permission of JPR. Subscriber shall be liable for any breach of this agreement and shall be subject to cancellation of its subscription to Reports. Without limiting this liability, Subscriber shall be liable for any damages suffered by JPR as a result of any Sharing of any Material, without advance written permission of JPR.
    [Show full text]
  • Adding RTX Acceleration to Iray with Optix 7
    Adding RTX acceleration to Iray with OptiX 7 Lutz Kettner Director Advanced Rendering and Materials July 30th, SIGGRAPH 2019 What is Iray? Production Rendering on CUDA In Production since > 10 Years Bring ray tracing based production / simulation quality rendering to GPUs New paradigm: Push Button rendering (open up new markets) Plugins for 3ds Max Maya Rhino SketchUp … 2 SIMULATION QUALITY 3 iray legacy ARTISTIC FREEDOM 4 How Does it Work? 99% physically based Path Tracing To guarantee simulation quality and Push Button • Limit shortcuts and good enough hacks to minimum • Brute force (spectral) simulation no intermediate filtering scale over multiple GPUs and hosts even in interactive use GTC 2014 19 VCA * 8 Q6000 GPUs 5 How Does it Work? 99% physically based Path Tracing To guarantee simulation quality and Push Button • Limit shortcuts and good enough hacks to minimum • Brute force (spectral) simulation no intermediate filtering scale over multiple GPUs and hosts even in interactive use • Two-way path tracing from camera and (opt.) lights 6 How Does it Work? 99% physically based Path Tracing To guarantee simulation quality and Push Button • Limit shortcuts and good enough hacks to minimum • Brute force (spectral) simulation no intermediate filtering scale over multiple GPUs and hosts even in interactive use • Two-way path tracing from camera and (opt.) lights • Use NVIDIA Material Definition Language (MDL) 7 How Does it Work? 99% physically based Path Tracing To guarantee simulation quality and Push Button • Limit shortcuts and good
    [Show full text]
  • The Growing Importance of Ray Tracing Due to Gpus
    NVIDIA Application Acceleration Engines advancing interactive realism & development speed July 2010 NVIDIA Application Acceleration Engines A family of highly optimized software modules, enabling software developers to supercharge applications with high performance capabilities that exploit NVIDIA GPUs. Easy to acquire, license and deploy (most being free) Valuable features and superior performance can be quickly added App’s stay pace with GPU advancements (via API abstraction) NVIDIA Application Acceleration Engines PhysX physics & dynamics engine breathing life into real-time 3D; Apex enabling 3D animators CgFX programmable shading engine enhancing realism across platforms and hardware SceniX scene management engine the basis of a real-time 3D system CompleX scene scaling engine giving a broader/faster view on massive data OptiX ray tracing engine making ray tracing ultra fast to execute and develop iray physically correct, photorealistic renderer, from mental images making photorealism easy to add and produce © 2010 Application Acceleration Engines PhysX • Streamlines the adoption of latest GPU capabilities, physics & dynamics getting cutting-edge features into applications ASAP, CgFX exploiting the full power of larger and multiple GPUs programmable shading • Gaining adoption by key ISVs in major markets: SceniX scene • Oil & Gas Statoil, Open Inventor management • Design Autodesk, Dassault Systems CompleX • Styling Autodesk, Bunkspeed, RTT, ICIDO scene scaling • Digital Content Creation Autodesk OptiX ray tracing • Medical Imaging N.I.H iray photoreal rendering © 2010 Accelerating Application Development App Example: Auto Styling App Example: Seismic Interpretation 1. Establish the Scene 1. Establish the Scene = SceniX = SceniX 2. Maximize interactive 2. Maximize data visualization quality + quad buffered stereo + CgFX + OptiX + volume rendering + ambient occlusion 3.
    [Show full text]
  • RTX Beyond Ray Tracing
    RTX Beyond Ray Tracing Exploring the Use of Hardware Ray Tracing Cores for Tet-Mesh Point Location -Now, let’s run a lot of experiments … I Wald (NVIDIA), W Usher, N Morrical, L Lediaev, V Pascucci (University of Utah) Motivation – What this is about - In this paper: We accelerate Unstructured-Data (Tet Mesh) Volume Ray Casting… NVIDIA Confidential Motivation – What this is about - In this paper: We accelerate Unstructured-Data (Tet Mesh) Volume Ray Casting… - But: This is not what this is (primarily) about - Volume rendering is just a “proof of concept”. - Original question: “What else” can you do with RTX? - Remember the early 2000’s (e.g., “register combiners”): Lots of innovation around “using graphics hardware for non- graphics problems”. - Since CUDA: Much of that has been subsumed through CUDA - Today: Now that we have new hardware units (RTX, Tensor Cores), what else could we (ab-)use those for? (“(ab-)use” as in “use for something that it wasn’t intended for”) NVIDIA Confidential Motivation – What this is about - In this paper: We accelerate Unstructured-Data (Tet Mesh) Volume Ray Casting… - But: This is not what this is (primarily) about - Volume rendering is just a “proof of concept”. - Original question: “What else” can you do with RTX? - Remember the early 2000’s (e.g., “register combiners”): Lots of innovation around “using graphics hardware for non- graphics →problems”.Two main goal(s) of this paper: -a)SinceGet CUDA: readers Much ofto that think has beenabout subsumed the “what through else”s CUDA… - Today: Nowb) Showthat
    [Show full text]
  • RTX-Accelerated Hair Brought to Life with NVIDIA Iray (GTC 2020 S22494)
    RTX-accelerated Hair brought to Life with NVIDIA Iray (GTC 2020 S22494) Carsten Waechter, March 2020 What is Iray? Production Rendering on CUDA In Production since > 10 Years Bring ray tracing based production / simulation quality rendering to GPUs New paradigm: Push Button rendering (open up new markets) Plugins for 3ds Max Maya Rhino SketchUp … … … 2 What is Iray? NVIDIA testbed and inspiration for new tech NVIDIA Material Definition Language (MDL) evolved from internal material representation into public SDK NVIDIA OptiX 7 co-development, verification and guinea pig NVIDIA RTX / RT Cores scene- and ray-dumps to drive hardware requirements NVIDIA Maxwell…NVIDIA Turing (& future) enhancements profiling/experiments resulting in new features/improvements Design and test/verify NVIDIA’s new Headquarter (in VR) close cooperation with Gensler 3 Simulation Quality 4 iray legacy Artistic Freedom 5 How Does it Work? 99% physically based Path Tracing To guarantee simulation quality and Push Button • Limit shortcuts and good enough hacks to minimum • Brute force (spectral) simulation no intermediate filtering scale over multiple GPUs and hosts even in interactive use • Two-way path tracing from camera and (opt.) lights • Use NVIDIA Material Definition Language (MDL) • NVIDIA AI Denoiser to clean up remaining noise 6 How Does it Work? 99% physically based Path Tracing To guarantee simulation quality and Push Button • Limit shortcuts and good enough hacks to minimum • Brute force (spectral) simulation no intermediate filtering scale over multiple
    [Show full text]
  • Megakernels Considered Harmful: Wavefront Path Tracing on Gpus
    Megakernels Considered Harmful: Wavefront Path Tracing on GPUs Samuli Laine Tero Karras Timo Aila NVIDIA∗ Abstract order to handle irregular control flow, some threads are masked out when executing a branch they should not participate in. This in- When programming for GPUs, simply porting a large CPU program curs a performance loss, as masked-out threads are not performing into an equally large GPU kernel is generally not a good approach. useful work. Due to SIMT execution model on GPUs, divergence in control flow carries substantial performance penalties, as does high register us- The second factor is the high-bandwidth, high-latency memory sys- age that lessens the latency-hiding capability that is essential for the tem. The impressive memory bandwidth in modern GPUs comes at high-latency, high-bandwidth memory system of a GPU. In this pa- the expense of a relatively long delay between making a memory per, we implement a path tracer on a GPU using a wavefront formu- request and getting the result. To hide this latency, GPUs are de- lation, avoiding these pitfalls that can be especially prominent when signed to accommodate many more threads than can be executed in using materials that are expensive to evaluate. We compare our per- any given clock cycle, so that whenever a group of threads is wait- formance against the traditional megakernel approach, and demon- ing for a memory request to be served, other threads may be exe- strate that the wavefront formulation is much better suited for real- cuted. The effectiveness of this mechanism, i.e., the latency-hiding world use cases where multiple complex materials are present in capability, is determined by the threads’ resource usage, the most the scene.
    [Show full text]
  • An Advanced Path Tracing Architecture for Movie Rendering
    RenderMan: An Advanced Path Tracing Architecture for Movie Rendering PER CHRISTENSEN, JULIAN FONG, JONATHAN SHADE, WAYNE WOOTEN, BRENDEN SCHUBERT, ANDREW KENSLER, STEPHEN FRIEDMAN, CHARLIE KILPATRICK, CLIFF RAMSHAW, MARC BAN- NISTER, BRENTON RAYNER, JONATHAN BROUILLAT, and MAX LIANI, Pixar Animation Studios Fig. 1. Path-traced images rendered with RenderMan: Dory and Hank from Finding Dory (© 2016 Disney•Pixar). McQueen’s crash in Cars 3 (© 2017 Disney•Pixar). Shere Khan from Disney’s The Jungle Book (© 2016 Disney). A destroyer and the Death Star from Lucasfilm’s Rogue One: A Star Wars Story (© & ™ 2016 Lucasfilm Ltd. All rights reserved. Used under authorization.) Pixar’s RenderMan renderer is used to render all of Pixar’s films, and by many 1 INTRODUCTION film studios to render visual effects for live-action movies. RenderMan started Pixar’s movies and short films are all rendered with RenderMan. as a scanline renderer based on the Reyes algorithm, and was extended over The first computer-generated (CG) animated feature film, Toy Story, the years with ray tracing and several global illumination algorithms. was rendered with an early version of RenderMan in 1995. The most This paper describes the modern version of RenderMan, a new architec- ture for an extensible and programmable path tracer with many features recent Pixar movies – Finding Dory, Cars 3, and Coco – were rendered that are essential to handle the fiercely complex scenes in movie production. using RenderMan’s modern path tracing architecture. The two left Users can write their own materials using a bxdf interface, and their own images in Figure 1 show high-quality rendering of two challenging light transport algorithms using an integrator interface – or they can use the CG movie scenes with many bounces of specular reflections and materials and light transport algorithms provided with RenderMan.
    [Show full text]
  • Getting Started (Pdf)
    GETTING STARTED PHOTO REALISTIC RENDERS OF YOUR 3D MODELS Available for Ver. 1.01 © Kerkythea 2008 Echo Date: April 24th, 2008 GETTING STARTED Page 1 of 41 Written by: The KT Team GETTING STARTED Preface: Kerkythea is a standalone render engine, using physically accurate materials and lights, aiming for the best quality rendering in the most efficient timeframe. The target of Kerkythea is to simplify the task of quality rendering by providing the necessary tools to automate scene setup, such as staging using the GL real-time viewer, material editor, general/render settings, editors, etc., under a common interface. Reaching now the 4th year of development and gaining popularity, I want to believe that KT can now be considered among the top freeware/open source render engines and can be used for both academic and commercial purposes. In the beginning of 2008, we have a strong and rapidly growing community and a website that is more "alive" than ever! KT2008 Echo is very powerful release with a lot of improvements. Kerkythea has grown constantly over the last year, growing into a standard rendering application among architectural studios and extensively used within educational institutes. Of course there are a lot of things that can be added and improved. But we are really proud of reaching a high quality and stable application that is more than usable for commercial purposes with an amazing zero cost! Ioannis Pantazopoulos January 2008 Like the heading is saying, this is a Getting Started “step-by-step guide” and it’s designed to get you started using Kerkythea 2008 Echo.
    [Show full text]
  • NVIDIA Ampere GA102 GPU Architecture Whitepaper
    NVIDIA AMPERE GA102 GPU ARCHITECTURE Second-Generation RTX Updated with NVIDIA RTX A6000 and NVIDIA A40 Information V2.0 Table of Contents Introduction 5 GA102 Key Features 7 2x FP32 Processing 7 Second-Generation RT Core 7 Third-Generation Tensor Cores 8 GDDR6X and GDDR6 Memory 8 Third-Generation NVLink® 8 PCIe Gen 4 9 Ampere GPU Architecture In-Depth 10 GPC, TPC, and SM High-Level Architecture 10 ROP Optimizations 11 GA10x SM Architecture 11 2x FP32 Throughput 12 Larger and Faster Unified Shared Memory and L1 Data Cache 13 Performance Per Watt 16 Second-Generation Ray Tracing Engine in GA10x GPUs 17 Ampere Architecture RTX Processors in Action 19 GA10x GPU Hardware Acceleration for Ray-Traced Motion Blur 20 Third-Generation Tensor Cores in GA10x GPUs 24 Comparison of Turing vs GA10x GPU Tensor Cores 24 NVIDIA Ampere Architecture Tensor Cores Support New DL Data Types 26 Fine-Grained Structured Sparsity 26 NVIDIA DLSS 8K 28 GDDR6X Memory 30 RTX IO 32 Introducing NVIDIA RTX IO 33 How NVIDIA RTX IO Works 34 Display and Video Engine 38 DisplayPort 1.4a with DSC 1.2a 38 HDMI 2.1 with DSC 1.2a 38 Fifth Generation NVDEC - Hardware-Accelerated Video Decoding 39 AV1 Hardware Decode 40 Seventh Generation NVENC - Hardware-Accelerated Video Encoding 40 NVIDIA Ampere GA102 GPU Architecture ii Conclusion 42 Appendix A - Additional GeForce GA10x GPU Specifications 44 GeForce RTX 3090 44 GeForce RTX 3070 46 Appendix B - New Memory Error Detection and Replay (EDR) Technology 49 Appendix C - RTX A6000 GPU Perf ormance 50 List of Figures Figure 1.
    [Show full text]
  • Nx Witness User Manual Contents
    User Manual Still need help? Visit us at http://support.networkoptix.com Nx Witness User Manual Contents Table of Contents Working with Nx Witness 1 Opening................................................................................................................................... and Closing Nx Witness Client 1 Connecting................................................................................................................................... to Nx Witness via Web-Client 3 Connecting................................................................................................................................... to Enterprise Controller and Working Offline 4 Launching................................................................................................................................... Nx Witness in Compatibility Mode 7 Introducing................................................................................................................................... User Roles 8 Nx Witness................................................................................................................................... User Interface Overview 9 Main Menu .......................................................................................................................................................... 10 Show ing and ..........................................................................................................................................................Hiding Side Panels 11 Tabs and Layouts.........................................................................................................................................................
    [Show full text]