Page 1 of 1

Shadow passes do not perfectly line up with alpha

Posted: Wed Aug 24, 2016 12:11 pm
by darkline
This is actually something i've been having issues with for a long time but only now is it becoming a real problem. I'm using the latest version of Octane 2 (uninstalled 3 for the moment)

The problem I have is when rendering out using the layer/passes system. On final compositing, there seems to be a small pixel wide gap between the beauty render and the shadow pass. When you comp it all together this results in an almost halo like outline around the beauty pass. Anyone know of a way around this because it's hard to fix in post, if you scale the shadow layer up or move it then you get an outline appearing elsewhere.

Normally when I render out shadow pass with other renderers they do not 'cut out' the shape of the shadow casting object and so do not leave any margin for error.


Is there any way we could have an option for a shadow pass that includes all the shadows cast (not one which cuts out/outlines the shadow casting object?) Shadow layers generally sit behind everything in the stack so it doesn't need to have anythig sut out of it.

Anyhow I don't know if this is an issue with the 3dsmax plugin or standalone, but it is very problematic for me.
shadow passes.jpg

Re: Shadow passes do not perfectly line up with alpha

Posted: Wed Aug 24, 2016 12:40 pm
by milanm
Hi

It's fixed, we just have to wait for the next release of V3.

viewtopic.php?f=30&t=55903

Edit: Sorry, I just noticed you were asking about V2, I'm not sure about that one.

Regards
Milan

Re: Shadow passes do not perfectly line up with alpha

Posted: Wed Aug 24, 2016 4:09 pm
by darkline
Thanks, have posted a link to this thread there, so hopefully they may look at V2 also.

Re: Shadow passes do not perfectly line up with alpha

Posted: Sun Aug 28, 2016 10:49 pm
by azen
Hi,

Thank you for reporting this issue. Since this fix was a applied on the significantly refactored Octane 3 rendering core, it is uncertain whether it is possible to replicate this fix in Octane 2. The best option would be to post your issue in the Standalone support forums - from there, the core team can best determine what can be done with this issue in v2.