![]() ![]() I am still uncertain whether this is due to a bad AA default setting, or an actual "feature" of this path tracer.Īnyway, this is not meant to dish on LW2018's new path tracer. Other users here have commented on this as well. It just takes less time to try things out and see the results displayed in (almost) real-time with a scene like this.īlender's denoiser removes fireflies automatically (if any), and delivers a noise-free result on top of all this.Īside from the benefits that GPU rendering brings to the table, again I notice how LW2018's high-lighted edges render very jaggy - something I never witnessed with other path tracers so far. ![]() That the render preview viewport renders very (VERY) fast (versus the slow VPR in 2018) is an additional workflow boon due to the GPU speedup, and speeds up lighting setup. This is what I meant in previous posts regarding flexibility: while my CPU is relatively slow, my GTX 1080 GPU allows me to not only render much faster, but also to increase the overall final quality while render times remain very manageable. With an additional sun light (to simulate the 5 minute 2018 and the 2015 render with the nice highlight) and denoising activated, the render is finished in 1 minute. Then I turned on GPU rendering in Cycles, and your original blender file renders in 22 seconds. I didn't care to wait for them to finish. My old i7 920 CPU renders much slower compared with your CPU.
0 Comments
Leave a Reply. |