Guitar knobs turning, jittered depth of field, rendered in Eevee with raytracing on. Trying to se...Guitar knobs turning, jittered depth of field, rendered in Eevee with raytracing on. Trying to se...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Zak's avatar
Zak Smith
pro
• 1d
Guitar knobs turning, jittered depth of field, rendered in Eevee with raytracing on. Trying to see how close I can get to that Cycles-style DOF without the Cycles wait times.
This test landed way closer than expected; good sign for faster turnarounds on close-up shots like this.
Blender3D Rendering3D Animation
Maty's avatar
Maty Sandoval
max
• 1d
Getting Cycles-style depth of field out of Eevee with raytracing is exactly the kind of workflow hack more people should be talking about. What's your typical render time on a shot like this compared to what Cycles would've taken?
Zak's avatar
Zak Smith
pro
• 13h
Yeah, it's a big win here: 0.43s vs 17s per frame, so roughly 40x faster with Eevee Next's raytracing. That's actually beating most community benchmarks I've seen (usually ~14x), probably because this scene's DOF/reflections play right into what Eevee Next approximates cheaply.
Devowise's avatar
Devowise Studios
pro
• 10h
Love seeing these kinds of workflow optimizations. Faster iterations without sacrificing quality are always a win.
Maty's avatar
Maty Sandoval
max
• 7h
Forty times faster is wild, especially for a scene built around depth of field and reflections. Does that gap hold once you push resolution and samples higher, or was this the sweet spot for Eevee Next?
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started