In case you’re missing some of the more advanced samples like “glass” that were removed from the
SDK in OptiX 4.0, we’ve put a handful of them on github:
OptiX Advanced Samples
Along the way we switched from GLUT to GLFW and added UIs with the imgui library; for
example, the new “optixGlass” sample has sliders for glass color and other things.
Build instructions for Linux and Windows are in the top level directory.
The OptiX Advanced Samples repository on github received some updates in the meantime.
To accompany the GTC 2018 tutorial S8518 - An Introduction to NVIDIA OptiX, a set of nine increasingly complex examples has been added inside the optixIntroduction sub-folder.
The extensive README on this site explains which different features each example added.
Although it starts very basic, the tutorial quickly provides the necessary foundation for a renderer implementation with quite a set of features already in form of an elegant and easy to extend uni-directional path tracer architecture.
The recording and slides (without animations) of the GTC presentation are publicly available on
Then another new example optixParticleVolumes had been added recently.
It demonstrates how to use OptiX’ BVH traversal for volumetric depth samples of unstructured geometry and provides a reference for particle volume rendering, similar to splatting, within OptiX.
An new OptiX Introduction example optixIntro_10 has been added to show how to use the OptiX 5.1.0 HDR DL Denoiser implementation.
With the OptiX 5.1.0 release, the built-in DL denoiser has been improved to support HDR input directly, which allows to move the tone-mapping into the final post-processing after the denoising stage again.
Please compare the necessary code changes against the optixIntro_09 example which had shown how to use the standard DL denoiser as supported since OptiX 5.0.0.
I’m happy to announce that new OptiX 7 advanced samples have gone live here:
The first two examples, intro_runtime and intro_driver, both port the seventh introduction example from the OptiX 5/6 API to the OptiX 7 API, using the CUDA Runtime API resp. the CUDA Driver API.
The intro_denoiser example adds the OptiX 7 HDR DL denoiser on top, with RGB, RGB+Albedo or RGB+Albedo+Normal buffers in either float4 or half4 buffer formats controlled via a compile time option.
It’s effectively matching the optixIntro_10 advanced sample, except for the motion blur and added normal buffer support.
The rtigo3 example is demonstrating different strategies for multi-GPU rendering distribution, where all GPUs work on the same frame, combined with different OpenGL interop methods. Of course it also works with single-GPU for comparisons.
Its mode of operation and scene layout is controlled by two simple text files. The rendering resolution is independent of the window size. It also contains code to load triangle mesh data from any file format supported by the ASSIMP library.
Please read the README.md and
scene_*.txt files inside the repository for more information.
For more introductory examples using the OptiX 7 API, please refer to the OptiX 7 SIGGRAPH course examples first:
The OptiX 7 advanced samples have been updated to also compile with the OptiX SDK 7.1.0 now.
The OptiX SDK 7.1.0 release changed a few API structures (listed in its release notes) which required some small adjustments to the existing OptiX SDK 7.0.0 based examples to compile. Look for compile-time decisions based on
OPTIX_VERSION to find the differences.
Currently the examples still build against OptiX 7.0.0 by default. To change that, please simply replace the
find_package(OptiX7 REQUIRED) against
find_package(OptiX71 REQUIRED) in each individual example’s CMakeLists.txt you want to switch to the new SDK.
Note that the OptiX SDK 7.1.0 strictly requires R450 drivers and only works on Maxwell GPUs and newer.
I also overhauled the default structure initializations, the text output, and fixed a multi-GPU synchronization issue inside the rtigo3 compositor() routine.
A new example called nvlink_shared has been added, which demonstrates how to share textures and/or geometry acceleration structures among the GPU devices inside an NVLINK configuration to increase the loadable scene size.
It’s derived from the existing rtigo3 example but moved the resource management from the Device class up to the Raytracer class because that decides which device shares what resource.
Please read the README.md and source code comments for more information. Find them via the link in the post above.
The OptiX 7 advanced samples have been updated to automatically use the latest installed OptiX SDK version which incudes support for OptiX SDK 7.2.0 now (Oct. 2020) and in the meantime OptiX 7.4.0.
Support for the NVIDIA Management Library (NVML) has been added to the nvlink_shared and rtigo3 examples to determine the system’s current NVLINK topology. That allows supporting arbitrary NVLINK configurations, esp. with more than two GPUs installed.
A new introduction example intro_motion_blur has been added as well.
It demonstrates how to implement motion blur with linear matrix transforms, scale-rotate-translate (SRT) motion transforms, and optional camera motion blur inside an animation timeline where frame number, frames per seconds, object velocity and angular velocity of the rotating object can be changed interactively. This example is only built when using the OptiX SDK 7.2.0 and newer.
Please always refer to the updated
README.me which contains more information.