DECODED writes:
Cycles is a fantastic render engine, capable of creating stunning, photo-realistic images with real-world lighting effects. However, as a path tracing engine, Cycles can be very slow. In this video, I talk about all the methods I currently use to get faster renders in Blender Cycles.
4 Comments
A very useful guides it’s also worth mentioning that newer versions of Blender offer hybrid rendering (CPU and GPU working together). This is often faster still. It uses the GPU to accelerate the work the CPU does so you will have as many tiles as your CPU has cores. As such, it works best with smaller tile sizes (ie: 32x32) and currently only works with Cuda/OpenCL cards.
Optix rendering only uses the GPU at present so you’re better rendering one big tile with that: This is usually still the fastest option for rendering.
This was really useful for setting up an old laptop with the best 2.83 settings to get reasonable render speeds. Reducing the default Indirect Clamp value from 10 to 3 made no visible difference to my render, but reduced the render time from 1;30 to 1:21, a useful 10% improvement.
I'm glad it helped.
there are useful tips for speed the render in Cycles in this tuto. Everthless the new 2.80 features are missing, is still actual. Like Clamp values, bounce indirect light, size of Tiles, Area light portal, Caustic, etc..
https://www.youtube.com/watch?v=8gSyEpt4-60