|
Nvidia OptiX (OptiX Application Acceleration Engine) is a general purpose ray tracing API for rendering, baking, collision detection, A.I. queries, etc. OptiX is ''not'' a renderer but can implement many types of renderers, it implements a modern shader-centric, stateless and bindless design.〔(【引用サイトリンク】title=Scheduling in OptiX, the Nvidia ray tracing engine )〕 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 Nvdia'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. With very few exceptions, such as Quake Wars: Ray Traced, 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 == OptiX works by using user-supplied instructions (in the form of CUDA kernels) regarding what a ray should do in particular circumstances to simulate a complete tracing process. 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. In order to use OptiX a CUDA-capable GPU must be available on the system and the CUDA toolkit must be installed. 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 ); Bounding box programs are used to define bounding volumes used to accelerate ray tracing process within acceleration structures as kd-trees or bounding volume hierarchies * 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. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「OptiX」の詳細全文を読む スポンサード リンク
|