E-Cycles - The fastest render engine for Blender. 3.2 release available now!

[duketogo]

E CYCLE only works with GPU

[rafbr]

New benchmark single GPU:
As you can see here E-Cycles is about 25% faster but a lot noisier

E-Cycles - The fastest render engine for Blender. 3.2 release available now!

I bought 2.8x e-cycles and now I am moving to the fully-featured 2.79 e-cycles build. Mathieu worked right away to have all my issues answered almost instantly. This scene is true light example. No AO. Cycles: [7bistrot_512spp] 4:06 pathtracing E-Cycles: [7bistrot_512spp_E-Cycles] 2:25 pathtracing

[TiborNyers_BC]

I have reproduced the interior rendering demonstration that @bliblubli already posted a few times, but this time without screen recording overhead - 720p, 100 spp, 0.02 scrambling distance —> 5 sec render time with 2080Ti

[BD3D (Dorian B.)]

@TiborNyers_BC

I have reproduced the interior rendering demonstration that @bliblubli already posted a few times, but this time without screen recording overhead - 720p, 100 spp, 0.02 scrambling distance —> 5 sec render time with 2080Ti

texture and object data already cached in vram right ?

what is the result for a similar noise nevel of cycles 2.8 official

[bliblubli (mathieu)]

Hi,
I’m on it. You provided the file 13 hours ago, I do my best. It can even take some days to get fixed. Look at this bug for example which affects many archviz scenes https://developer.blender.org/T54486. reported more than a year ago, still no fix although the BF has many devs and now very good funding. You found a scene which has problem, I’m sorry for that, but I think it’s normal to give some time to people to react. Did you ever made a bug report to Microsoft or Autodesk?
If I can’t fix it in a reasonable time, I refund you. But I used to bug fixing, most bugs I got reported got fixed in a day or two. Look here for a bug report and here for the solution and here what the same customer who experienced bugs says. A bit of patience please

[bliblubli (mathieu)]

So I did several test and couldn’t reproduce your noise bug. I used both the march version and the latest beta, both render with the same noise level. The noise is different (normal as E-Cycles uses a new sampler), but not higher:
Master takes 80 secs to do the path tracing and outputs this image (time is written on the line "time without synchronisation):

E-Cycles only 39sec and output this image(AI Denoiser):

This is the noisy image:

Did you use the exact same file?
Did you use the latest beta (I added a new one yesterday during the sales, maybe you got an old beta?)

[PaulStormblader]

I’m someone who occasionally does long renders, and am interested in this project - curious about how compatible / comparable it is to this:

https://remingtongraphics.net/tools/d-noise/

Thanks!

[bliblubli (mathieu)]

Hi,
here, an E-Cycles user did a comparison:

E-Cycles - The fastest render engine for Blender. 3.2 release available now!

Original noisy render [noisy] nvidia optix denoiser from dnoise [dnoise] inter open ai denoiser [intel] dnoise lose a lot of informations compare to the intel denoiser

you have to download the images and zoom at 100% to see the difference.

Kind regards,
Mat

[rafbr]

Yes same file.
I am downloading beta again just to be sure.

[bliblubli (mathieu)]

Hi Tibor,
Thanks a lot for showing the true speed of E-Cycles with external recording I should get such a setup too. But the slowdown of live screen recording helps some to believe.
5 seconds for archviz

[PaulStormblader]

so you’re using the intel denoiser? Does it still work with the nvidia denoiser?

[bliblubli (mathieu)]

I’m using the Intel denoiser indeed. It should work with the NVidia denoiser of course. Addons compatibility is the same as for official Blender.

[BD3D (Dorian B.)]

about that, any news from a viewport denoiser ? both from stefan and brett?
i talked about stefan on twitter about cpu viewport denoising + gpu calculation he’s saying its possible

[mib2berlin]

Hi, Brecht has answered at https://devtalk.blender.org/
The patch is https://developer.blender.org/D2862
He was not very enthusiastic about the patch but was working fine with my GTX 560Ti and GTX 760 on Linux.
May you have a look, is not that big.

Cheers, mib

[bliblubli (mathieu)]

Thanks for the link I’ll look asap.

[bliblubli (mathieu)]

It’s on my huge todo list. Somehow, the more things I implement from my todo, the bigger the todo list is

[BD3D (Dorian B.)]

ahahah same problem here, i think the third of the forum have a to-do list problem
could we know whats in the near future of your to-do list ?

[bliblubli (mathieu)]

I have a 10% speedup already in good shape, but I didn’t decide yet what will come next, the April update was just released. So I’m concentrating on making it stable and polished first. Rendering an archviz in 5sec or 4.5sec (10%faster) doesn’t make much difference. It already allows E-Cycles users to avoid long uploads and downloads of huge PNGs/EXR by rendering locally, even on low end cards. And with RTX being worked on…
So I’ll also concentrate on making the documentation, tutorials and UI better so that users can even easier get the most out of E-Cycles. A better heuristic also to automatically choose parameters on the fly.
And of course a better viewport. I don’t remember if I posted it, the thread became so huge, it’s using the current 2.79 April beta:

[BD3D (Dorian B.)]

amazing keep up the good work !
can’t wait to see the result of the 2.79 beta in 2.8

[bliblubli (mathieu)]

For those who already tested the new preset system, what do you think, should I let the sample count user defined and only include the other parameters?

• Yes please, sample count user defined
• It’s good as it is