Is it normal for such a simple shader to take a while to render? What’s going wrong?

This topic has 3 replies, 4 voices, and was last updated 1 year, 9 months ago by Dwayne Savage.

Viewing 4 posts - 1 through 4 (of 4 total)

Author

Posts
December 3, 2024 at 11:58 pm #19289
Sid Edwards
Participant
When I open tutorial files from CG-cookie, they usually render pretty fast with looking reasonably photorealistic-like.

But when I try to set up the lighting on my own to test building a simple wax material, even when I set the max number of bounces to 1, the scene is very choppy and slower to load than other files I’ve downloaded.

What are some common ways to speed up the Cycles render engine? Unfortunately I can’t upload my .blend file to this site.
December 4, 2024 at 2:53 am #91566
Martin Bergwerf
Participant
Some screenshots of your Settings and Shader Nodes, might help, but you can also upload your .blend file to Dropbox, GoogleDrive, or so and post a link here.
December 4, 2024 at 8:52 am #91567
Omar Domenech
Participant
Yeah most likely those files have been optimized for test renders. Rendering is a balancing game, quality over time or time over quality. Usually you’re trying to struck some middle ground. The most common way is just to play with the noise threshold and samples, if you want to boil it down to one setting. But each scene is different, there isn’t a global standard number to set, you have to be the judge depending on what you’re working on and what price are you willing to pay.
December 4, 2024 at 9:56 am #91568
Dwayne Savage
Participant
Make sure you are set to use GPU and not CPU. Also reduce the number of samples or newer blender versions have a noise threshold setting and a max time setting. Another thing is denoising which allows you to use even less samples, but it’s a balancing act. Blurry vs noise.
Author

Posts

Viewing 4 posts - 1 through 4 (of 4 total)

The topic ‘Is it normal for such a simple shader to take a while to render? What’s going wrong?’ is closed to new replies.