Regarding the reported bug, I’m still investigating, but at least using an HDRi from HDRi haven (as I don’t have pro lightning skies) on RTX cards and even using the 2.8 april beta with scrambling distance, it looks the about the same in buildbots and E-Cycles:
master:
Thx for the times!
Since you have 2 2080Ti’s: Have you tried connecting them via NVLink to join the Vram ?
(2x 11GB => 1x 22GB) Is this even possible from the get go?
Transforming a 980Ti into a 2080Ti for 42€ is possible
Thanks a lot for the very serious test and the full logs. Very precious for in depth analysis on different architectures. It definitely helped to make E-Cycles even better
Actually, to be correct, the 980Ti is even 16% faster than the 2080Ti.
Some of you asked for a video of a render session. As there was a lot of post today, I add it here again. Real render time without screen recording and compression is around 8sec per frame with one GPU only. It uses the preprocessing option of 2.79x.
and if you want the 2x speedup and the AI denoising node on top of a branch of your choice like Mantaflow or Fracture modifier branch, you can learn to make your own Blender here https://gum.co/ecycle/gumroadday (with 30% off today)
carreful with interpreting this benchmark, e-cycles scale a bit less than 2.8 master, two gpu for my case in master is +1.9x power, e-cycles is 10% less, so for a single gpu the result would be better up there
the april update is still really good !
still in beta and 2.79 only tho
Hum I am not seen any speed up here. All I see is the great Intel denoiser in action.With exactly same settings it is slower than Cycles. And to me Cycles have less firefly. Or am I missing something?
I would need the number and model of GPUs, and CPU if you activated one as well as the exact name of the build you used. I already hear problems of people having D-Noise activated in parallel. To avoid conflicts, it’s always good to try with factory default, then only activate the new AI denoiser addon and the GPUs without CPU.
The new parameter can be tricky to use (scrambling distance) I will add a doc to explain how to use it soon. In the mean time, you can use the presets and set the spp as you wish or set scrambling distance to simply 0.1 and it should work in most cases.
If you still have problems, please provide a file and the steps to reproduce, I’ll have a look asap.
The doc will be my priority tomorrow to explain all the new functionality of the April beta