Author Topic: Corona vs Vray: moving object animation and rendertime comparison  (Read 20662 times)

2014-09-17, 14:13:08
Reply #15

spdb

  • Active Users
  • **
  • Posts: 13
    • View Profile
After some days tweaking and testing differents setting, we've reached to render frames in 11/12 min, without flickering or big noise problem.
We are quite satisfied with the overall quality.

I attached raw render and one slightly denoise with Nuke.

2014-09-17, 19:35:44
Reply #16

cecofuli

  • Active Users
  • **
  • Posts: 1578
    • View Profile
    • www.francescolegrenzi.com

2014-09-17, 20:20:30
Reply #17

juang3d

  • Active Users
  • **
  • Posts: 636
    • View Profile
For video I prefer the "no-denoise" picture, the noise gives the video a grain effect that looks great to me, I don't like the cg-clean pics :)

Cheers.

2014-09-17, 22:32:38
Reply #18

Nekrobul

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 1028
    • View Profile
For video I prefer the "no-denoise" picture, the noise gives the video a grain effect that looks great to me, I don't like the cg-clean pics :)

Cheers.

Do not listen to this guy.

It is better to add film grain in post pro.

12-13 min i say not bad at all )
---------------------------------------------------------------
https://www.blackbellstudio.com/
https://www.behance.net/blackbell3d
CEO at "Blackbell Studio"

2014-09-18, 09:22:40
Reply #19

spdb

  • Active Users
  • **
  • Posts: 13
    • View Profile
Frames were rendered by a render farm (6racks with bi-xeon E5645 @2.4GHz).
We used PT-HDCache, default settings for PT, we precompute HDCache first (about 20 min with settings below).

Please share some optimizations if you see some!

2014-09-18, 09:32:45
Reply #20

Ludvik Koutny

  • VIP
  • Active Users
  • ***
  • Posts: 2557
  • Just another user
    • View Profile
    • My Portfolio
Those HDcache settings are ridiculous overkill, especially for an exterior scene. If you precompute HDcache, it won't flicker no matter what, with these settings, you just increase your precomp time 10 times without any noticeable benefit quality-wise.

2014-09-18, 09:51:18
Reply #21

spdb

  • Active Users
  • **
  • Posts: 13
    • View Profile
We tried some lower settings for HDCache, but frames took 3 to 4 min more to be calculated.
And some low settings give us flickering in some dark spots...
We are learning Corona, maybe we could be better next time...

2014-09-18, 12:27:25
Reply #22

Nekrobul

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 1028
    • View Profile
It is better to use PT+PT for animation to maintain noise regularity.
---------------------------------------------------------------
https://www.blackbellstudio.com/
https://www.behance.net/blackbell3d
CEO at "Blackbell Studio"

2014-09-18, 12:57:53
Reply #23

spdb

  • Active Users
  • **
  • Posts: 13
    • View Profile
Yes we tried, but render time to avoid noise were way too high (about 35-40 min)...
Still testing different setting found all over differents threads on the forum, but it's quite hard to find an effective method...

For the moment, we are quite happy with our frame render time, but we keep searching great setting to reach fast render..

2014-09-18, 13:18:57
Reply #24

Ludvik Koutny

  • VIP
  • Active Users
  • ***
  • Posts: 2557
  • Just another user
    • View Profile
    • My Portfolio
That's strange. If HDcache is properly saved, it should not flicker regardless of settings. Nor should lowering HDcache quality make rendertimes longer.

2014-09-18, 14:30:50
Reply #25

Nekrobul

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 1028
    • View Profile
Yes we tried, but render time to avoid noise were way too high (about 35-40 min)...
Still testing different setting found all over differents threads on the forum, but it's quite hard to find an effective method...

For the moment, we are quite happy with our frame render time, but we keep searching great setting to reach fast render..

Key to time might be hidden in the materials.

First things eating rendertime are opacity maps and CoronaAO
---------------------------------------------------------------
https://www.blackbellstudio.com/
https://www.behance.net/blackbell3d
CEO at "Blackbell Studio"

2014-09-18, 15:19:13
Reply #26

spdb

  • Active Users
  • **
  • Posts: 13
    • View Profile

Key to time might be hidden in the materials.

First things eating rendertime are opacity maps and CoronaAO

Yes i agree... I've tweaked quite a lot materials in this scene, cause it was roughly converted from Vray...
Unfortunaly, we have a limited full geometry trees and plants library, and our clients often have specific requests about vegetation.
We have a blend material driven by AO for walls, I reduced its sampling to something like 8, don't remember.
Maybe I'll do some tests without...

2014-09-19, 23:38:58
Reply #27

Nekrobul

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 1028
    • View Profile

Key to time might be hidden in the materials.

First things eating rendertime are opacity maps and CoronaAO

Yes i agree... I've tweaked quite a lot materials in this scene, cause it was roughly converted from Vray...
Unfortunaly, we have a limited full geometry trees and plants library, and our clients often have specific requests about vegetation.
We have a blend material driven by AO for walls, I reduced its sampling to something like 8, don't remember.
Maybe I'll do some tests without...

You can try to turn of texture filtering in devel\debug settings sometimes it helps a lot but its tricky and might bring out fire flys, but sometimes it decreases rendertime 2x 3x times.

Also you can chek albeedo white stucko material seem to be overlitt
---------------------------------------------------------------
https://www.blackbellstudio.com/
https://www.behance.net/blackbell3d
CEO at "Blackbell Studio"

2014-09-19, 23:55:55
Reply #28

spdb

  • Active Users
  • **
  • Posts: 13
    • View Profile
I've checked albedo render element, and no problem with that ( some slight pink area on the windows ( white 210 or 220), otherwise everything great).
We've test filtering option on the dev panel, but it produce some fireflies on the moving guy...
I've read this thead https://forum.corona-renderer.com/index.php/topic,3649.0.html about geometry vs opacity render time, and this one https://forum.corona-renderer.com/index.php/topic,4640.0.html about filtering theory...
Well, quite a lot to study!! Thx for your advices and comments, great to see such an active community!