A gorgeous beach scene by zkart.
- 1920/1080 p
- 100 sampling
- 450 frame _ 7h of rendering
- 52 sec per Frame
- Volumetric + Depth of field
A gorgeous beach scene by zkart.
- 1920/1080 p
- 100 sampling
- 450 frame _ 7h of rendering
- 52 sec per Frame
- Volumetric + Depth of field
13 Comments
Hello,
He uses micro-displacement with Eevee?
I so, how did he do that? Experimental mode is available only with Cycles.
Thank you
Nah he didn't. That's just good old classic Displacement.
I'm guessing it's just a mesh + normalmap thing. Anyways, nice work.
52 sec per frame? I guess with denoiser I could get to that number also with cycles, since this is an exterior scene.
Nice!
However, 52 seconds per frame (=0,019 fps!) is very far from real time.
Also, one little thing that bothers me a bit: the water surface has displacement, little "dents" here and there. It doesn't seem to be a flowing river or anything, so the water surface should be completely flat. This it looks more like clear plastic wrap.
You say it's real-time but then say: 450 frame _ 7h of rendering @52 sec per Frame...
I'm confused.
Its quite close to realtime, so not too shabby. to me the main thing is the audio track that indicates flowing water but it is static. Also the sounds are conflicting in that we have a stream and ocean sounds at the same time.
Still going back to the video, would be nice if the water would be animated a bit in some way to add more life. If it is, then at least at my current location and possibly low bandwidth, I don't see it.
How is 52 sec per frame close to real time?? Maybe he has a slow outdated GPU, someone with a high end GPU might get one frame per second, still far cry from 24 frames per second but I would consider close to real time.
Appologies.. totally missed it while it is right there in front right above the video. thanks for the correction.
And also too bad, I woudl expect that this video woudl be much closer to realtime then the 52 second per frame... bummer
Nice.
Vector displacement would be awesome in this scene.
Sooo... Real time or seven hours... Can't be both!
Sure it is not real time, but for the result, 52 seconds a frame is really good. For me Eevee is going to be a real killer app in Blender. Cycles is amazing, but is often too slow to do animation for quick turn around jobs. Eevee, however is going to fill that gap very nicely. Speedy renders often outweighs accuracy in render results for my line of work, motion graphics.
That's definitely the market for eevee. However, if the new RTX cards will be what they say to be, and possibly with optix superresolution, There will probably be a way to get results from cycles at comparable speeds.