Eevee vs Cycles – speed comparison
Marius Iatan writes:
As Blender 2.80 development advances toward the first Release Candidate, Eevee becomes more stable and receives more features. With Blender Internal out of the picture and the promise of greatly improved speed, Eevee generates a lot of excitement – and a corresponding amount of questions. The most important two are, of course, “how fast is it?” and “how does the output quality compare to Cycles?”
We decided to run a few tests on our farm and see what the results will tell us. We picked three different scenes that have both Cycles and Eevee versions and rendered them on our servers.
I love using Eevee for real-time visuals while building a scene. Just today, I managed to use Eevee for a final render on a client project; however, most of the time, I wind up doing the final render in cycles due to its better handling of reflections and nicer shadows. For some purposes, Eevee is good for final renders (especially real-time applications naturally), but even if you don’t use it for the final, it’s a joy to work in. It feels so hands-on. I could never go back.
I was wondering why I’d bother to read this article—only to discover it’s from the Render.st blog. I think Render.st should be mentioned in the title, as it adds more credibility.
Thanks for the feedback and for the vote of confidence, B-FUZE. I didn’t want it to sound like an advertorial, so I didn’t include the render.st name in the title. Maybe I should have :)