Mantra: AOV per light multiplies volume rendering time by 20 SOLVED

   2706   9   1
User Avatar
Member
532 posts
Joined: Nov. 2016
Online
A volume with two lights plus emissive objects. Without light AOV's, renders in about 20 minutes, with them in about 8 hours. RAM isn't capped. Anybody knows what might cause that, or how to avoid it?
Edited by Tanto - March 25, 2022 17:22:47
User Avatar
Member
8170 posts
Joined: Sept. 2011
Offline
That's news to me. I haven't seen a difference in performance. Is this with LPE tags or oldschool light breakouts?
User Avatar
Member
532 posts
Joined: Nov. 2016
Online
Just the "Combined Lighting (Per-Light)" and "Combined Emission" image plane presets. No tags.
User Avatar
Member
9237 posts
Joined: July 2007
Online
I havent seen that with lights
but I noticed something similar with Emission AOVs and volumes, not sure if that's your case
since emission AOVs by default are Full Opacity Sampling and that for some reason slows down rendertime when rendered together with lit density
rendering density and emission separately is fast even when emitssion render is held out by density, I didnt have time to investigate why, but this is in 18.5
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Member
532 posts
Joined: Nov. 2016
Online
Yes I did have an emission AOV. Thank you, I'll try rendering just that separately. And this was in 19.0.498.
User Avatar
Member
9237 posts
Joined: July 2007
Online
Tanto
Yes I did have an emission AOV. Thank you, I'll try rendering just that separately. And this was in 19.0.498.
I mean quick try would be to change emission aovs from Full Opacity Filtering to Opacity Filtering but that would use stochastic sampling and may be grainier, however if it speeds up you'll know your culprit
rendering separately was fast for me for emissive volumes even without stochastic sampling
Edited by tamte - March 25, 2022 16:59:15
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Member
532 posts
Joined: Nov. 2016
Online
tamte
I mean quick try would be to change emission aovs from Full Opacity Filtering to Opacity Filtering but that would use stochastic sampling and may be grainier

That did the trick. Thanks tamte!
User Avatar
Member
8170 posts
Joined: Sept. 2011
Offline
tamte
Tanto
Yes I did have an emission AOV. Thank you, I'll try rendering just that separately. And this was in 19.0.498.
I mean quick try would be to change emission aovs from Full Opacity Filtering to Opacity Filtering but that would use stochastic sampling and may be grainier, however if it speeds up you'll know your culprit
rendering separately was fast for me for emissive volumes even without stochastic sampling

Tanto
Just the "Combined Lighting (Per-Light)" and "Combined Emission" image plane presets. No tags.

Combined emission is a no-no. It should never be used with volume rendering as the direct component requires full opacity samples for quality, and the indirect component should be done with screendoor samples for performance.

Using the combined plane requires a compromise.
User Avatar
Member
9237 posts
Joined: July 2007
Online
jsmack
Combined emission is a no-no. It should never be used with volume rendering as the direct component requires full opacity samples for quality, and the indirect component should be done with screendoor samples for performance.
ah, that makes sense
so having direct_emission at Full Opacity Sampling
and indirect_emission at Opacity Sampling
should work fine and in fact that seems to be the default for those AOVs
Edited by tamte - March 25, 2022 17:44:24
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Member
532 posts
Joined: Nov. 2016
Online
Thanks to you both. Was trying to have identical AOVs for comp as renders from another software, but this certainly argues for separate direct and indirect AOVs in these cases, maybe combining them in a post-process.
  • Quick Links