7.0 / July 30, 2019
|Written in||C / C++|
|Operating system||Linux, OS X, Windows 7 and later|
|License||proprietary software, free-of-cost for non-commercial use|
|Website||NVIDIA OptiX developer site|
Nvidia OptiX (OptiX Application Acceleration Engine) is a ray tracing API. The computations are offloaded to the GPUs through either the low-level or the high-level API introduced with CUDA. CUDA is only available for Nvidia's graphics products. Nvidia OptiX is part of Nvidia GameWorks. OptiX is a high-level, or "to-the-algorithm" API, meaning that it is designed to encapsulate the entire algorithm of which ray tracing is a part, not just the ray tracing itself. This is meant to allow the OptiX engine to execute the larger algorithm with great flexibility without application-side changes.
Commonly, video games use rasterization rather than ray-tracing for their rendering.
According to Nvidia, OptiX is designed to be flexible enough for "procedural definitions and hybrid rendering approaches." Aside from computer graphics rendering, OptiX also helps in optical & acoustical design, radiation and electromagnetic research, artificial intelligence queries and collision analysis.
Ray tracing with OptiX
A light ray (or perhaps another kind of ray) might have a different behavior when hitting a particular surface rather than another one, OptiX allows to customize these hit conditions with user-provided programs. These programs are written in CUDA C or directly in PTX code and are linked together when used by the OptiX engine.
Using the OptiX engine into a ray tracing application usually involves the following steps:
- Defining programs for ray generation (e.g. rays can be shot in parallel, in a perspective fashion or like a gradient field), ray missing (when a ray doesn't intersect any object), an optional exception program (when the ray cannot be shot for some reason), a bounding box program (the program that provides a bounding box intersection test for a given object) and an intersection program.
Several examples for these programs are available with the program's SDK
// Sample code using OptiX APIs // /* Ray generation program */ rtProgramCreateFromPTXFile( *context, path_to_ptx, "pinhole_camera", &ray_gen_program ); rtContextSetRayGenerationProgram( *context, 0, ray_gen_program ); /* Miss program */ rtProgramCreateFromPTXFile( *context, path_to_ptx, "miss", &miss_program ); rtContextSetMissProgram( *context, 0, miss_program ); /* Bounding box and intersection program */ rtProgramCreateFromPTXFile( context, path_to_ptx, "box_bounds", &box_bounding_box_program ); rtGeometrySetBoundingBoxProgram( *box, box_bounding_box_program ); rtProgramCreateFromPTXFile( context, path_to_ptx, "box_intersect", &box_intersection_program ); rtGeometrySetIntersectionProgram( *box, box_intersection_program );
- Create material any hit and closest hit programs: these two programs determine a ray behavior when encountering its first intersection (closest hit) or a generic intersection (any hit)
// Sample code using OptiX APIs // rtProgramCreateFromPTXFile( context, path_to_ptx, "closest_hit_radiance", &closest_hit_program ); rtProgramCreateFromPTXFile( context, path_to_ptx, "any_hit_shadow", &any_hit_program ); /* Associate closest hit and any hit program with a material */ rtMaterialCreate( context, material ); rtMaterialSetClosestHitProgram( *material, 0, closest_hit_program ); rtMaterialSetAnyHitProgram( *material, 1, any_hit_program );
- Define buffers, variables that might be used inside the supplied programs. Buffers are memory areas that allow host code (i.e. normal CPU code) to communicate with device code (i.e. the code that gets executed on the GPU) and vice versa. Variables are OptiX's internal way of communicating and using buffers to transfer data back and forth.
- Define the OptiX hierarchy of geometry objects, groups, selectors and other nodes to generate a tree graph of the entire scene to be rendered
In order to render a complex scene or trace different paths for any ray OptiX takes advantage of GPGPU computing by exploiting NVIDIA CUDA platform. Since the process of shooting rays and setting their behavior is highly customizable, OptiX may be used in a variety of other applications aside from ray tracing.
Starting from OptiX 3.5.0 a second library called OptiX Prime was added to the bundle which aims to provide a fast low-level API for ray tracing - building the acceleration structure, traversing the acceleration structure, and ray-triangle intersection. Prime also features a CPU fallback when no compatible GPU is found on the system. Unlike OptiX, Prime is not a programmable API, so lacks support for custom, non-triangle primitives and shading. Being non-programmable, OptiX Prime does not encapsulate the entire algorithm of which ray tracing is a part. Thus, Prime cannot recompile the algorithm for new GPUs, refactor the computation for performance, or use a network appliance like the Quadro VCA, etc.
Software using OptiX
- Blender has OptiX support since version 2.81 
- The Blender Add-on D-NOISE uses OptiX binaires for AI-accelerated denoising
- FurryBall - Advanced real-time GPU production quality final frame renderer using raytrace as well as rasterize - based on Nvidia OptiX
- At SIGGRAPH 2011 Adobe showcased OptiX in a technology demo of GPU ray tracing for motion graphics.
- At SIGGRAPH 2013 OptiX was featured in Pixar's realtime, GPU-based lighting preview tool.
- OptiX has been integrated into the GameWorks developers library along with PhysX and other CUDA powered graphics engines and frameworks.
- Adobe After Effects CC
- DAZ Studio had OptiX Prime Acceleration since its Iray integration, however support was removed in version 220.127.116.11
- "Scheduling in OptiX, the Nvidia ray tracing engine" (PDF). August 15, 2009.
- Felbecker, Robert; Raschkowski, Leszek; Keusgen, Wilhelm; Peter, Michael (2012). "Electromagnetic wave propagation in the millimeter wave band using the NVIDIA OptiX GPU ray tracing engine". 2012 6th European Conference on Antennas and Propagation (EUCAP). IEEE Xplore. pp. 488–492. doi:10.1109/EuCAP.2012.6206198. ISBN 978-1-4577-0920-3.
- Steven G. Parker; Heiko Friedrich; David Luebke; Keith Morley; James Bigler; Jared Hoberock; David McAllister; Austin Robison; Andreas Dietrich; Greg Humphreys; Morgan McGuire; Martin Stich (2013). "Magazine Communications of the ACM - GPU ray tracing". Communications of the ACM. ACM. Retrieved August 14, 2013.
- Steven G. Parker; Heiko Friedrich; David Luebke; Keith Morley; James Bigler; Jared Hoberock; David McAllister; Austin Robison; Andreas Dietrich; Greg Humphreys; Morgan McGuire; Martin Stich (2010). "OptiX: a general purpose ray tracing engine". ACM Transactions on Graphics (Tog). ACM. doi:10.1145/1778765.1778803. Retrieved August 14, 2013.
- "Blender 2.81 Benchmarks On 19 NVIDIA Graphics Cards - RTX OptiX Rendering Performance Is Incredible". phoronix.com. 2019. Retrieved November 26, 2019.
- "D-NOISE: Rapid AI Denoising for Blender". Remington Creative. July 20, 2019. Retrieved December 14, 2019.
- "Adobe showcasing OptiX in a technology demo for ray tracing motion graphics with GPUs". NVIDIA. 2013. Retrieved August 14, 2013.
- "Nvidia announces Gameworks Program at Montreal 2013; supports SteamOS". NVIDIA. 2013. Retrieved October 29, 2013.
- "GPU changes (for CUDA and OpenGL) in After Effects CC (12.1) | After Effects region of interest". Retrieved February 22, 2015.
- "DAZ Studio Changelog". DAZ 3D. Retrieved December 14, 2019.