tonyvilters posted at 6:25AM Tue, 16 July 2019 - #4357120

Speeding up render times is actually quite easy if you remember that everything you add has to be calculated.

I see some adding nodes and nodes and nodes, but remember. . . . . Everything you add has to be calculated.

Same goes for polycount, number of material zones, number and size of textures, number and type of lights.

And if you use the "modern" PBR workflow with older content, please remove all old "cheating nodes" when it is render time.

Many have proved that all content renders pretty good with very few nodes.

Less calculations to perform, and avoiding contradicting calculations speeds renders up.

In the end? Each rendered pixel has just a single R,G,B, value, and the pixel does not care where that came from.

Nodes aren't the real problem though with PBR. It's how the light bounces around during render times. If you'll notice, most of the suggestions for speeding up rendering are actually for how much, how and where the light bounces around a scene. Firefly fakes a lot of this, but PBR actually does calculate the light bounces in a scene.