Another test with Octane in Houdini. The render time was about 2:20 Minutes on RTX5000 for the image (in 5k resolution).
finally, I got some time to play with octane in Houdini. I am impressed with the interactivity of the renderer. The render time was about 2:30 Minutes on RTX5000 for the image (in 5k resolution).
rendered with Arnold in Houdini. I’ve tried the atmosphere volumes the first time. easy to setup. The render time was quite slow on the volumes, typically for volumes, but much faster then render the screen envr with VDB cloud. I’ve used a mesh light for inner character illumination.
it’s a shame I could not use Arnold 6 GPU, because its missing features. Volumes would boost get huge speed boost with volume raymarching on a GPU. I had to use a denoiser from Affinity Photo in dark areas.
with Arnold 6 GPU it does not drop any errors, you have to wait 1-2 minutes if data is loaded to GPU and starts the rendering or not. even a wrong file pass to an Hdri image makes Arnold GPU drop out, you sitting and wait in front of a black screen and don’t know if it will render or not.
I’ve made a simple scene to test the physics of light. for proper light calculation, I used spectral render Indigo and Octane.
Indigo has multiple Engines, standard Spectral Path tracer on CPU or GPU and Bidirectional path tracing with MTL sampling (metropolis Light Transport). Octane has only default Spectral Path tracer on GPU but includes an MTL sampling method. I’v also added Renderman 23 to the test with its unified rendering integrator. It supports bidirectional path, manifold caustics and path guiding on the CPU.
Another render engine like Arnold or Cycles with regular Path tracing would impractical fro complex light calculation tasks.
The base scene is Sphere and squashed Sphere underneath inside a volume box (uniform VDB).
The following image is the result of Indigo Renderer with BiDirectional path tracing and MTL. It was by far the fastest rendering.
an N-Body simulation which calculates a gravity field and corresponding velocity and acceleration contributions accumulated by each body in the system from every other body. Shows how to mitigate computation between all available devices including CPU and GPU devices, as well as a hybrid combination of both, using separate threads for each simulator.
the setup in Houdini : 120.000 stars simulated with the openCL wrangle in a Solver. the graphic card on my macbook RX420 GPU is about 25 faster then NBody in C/Vex on the I7 CPU
realtime nbody on my macbook with 40.000 stars