Why is my alpha pass binary (just 0's and 1's) in Cycles?

Why is my alpha pass binary (just 0's and 1's) in Cycles?



In Blender Render, my rendered alpha pass has intermediate values (e.g., 0.83) at the boundary -- great for anti-aliasing compositing!



enter image description here



However, when I switch to Cycles, my alpha channel is always binary, i.e., consisting of only 0's and 1's.



enter image description here



For some other reasons, I have to stick with Cycles. How would I produce an alpha pass with intermediate values in Cycles?







@wizzwizz4 Monochrome is single chroma, single hue in colorspace. The term Binary image is correct here. Binary is subset of Grayscale and that is subset of Monochrome.
– Jaroslav Jerryno Novotny
Aug 25 at 15:24





@wizzwizz4 Since there is an image showing what it is and there is even explanation in brackets in the title, I fail to see the problem you are trying to solve. At least people will learn what Binary image is. Black&White is used as synonym for Grayscale, it's misleading same as Monochrome was. People not understanding something is normal and does not justify avoiding correct terms, it even might spread confusion. Binary is the best how to call this and there is no problem with it because this is not a casual site, here you will come across many more technical terms.
– Jaroslav Jerryno Novotny
Aug 25 at 16:10




1 Answer
1



You have only 1 sample set for Cycles:



cycles sampling panel showing render samples set to 1



Any particular sample in Cycles will return either 1 or 0 for the alpha channel. Antialiased alpha edges are built up by averaging multiple samples, some of which strike the occluding object and some which do not. Using a larger number of samples, such as 16, will fix the issue.





This is cool. But how many samples are enough? Hmmm.
– Sibbs Gambling
Aug 25 at 14:35






That's one of those nebulous "it's enough samples when it's good enough for you" things. Technically, any sample count greater than 1 gives some antialiasing. The more samples, the more antialiasing. There's no way to say definitively when it's enough. 10-20 is a nice ballpark in a lot of cases, but who knows? Rendering is complicated.
– JtheNinja
Aug 25 at 20:44





Roughly speaking, ~32 samples will clean up images with only diffuse and no bounce. But usually you'll have much more than that. If you have bounce light, you're looking at ~250 for diffuse to clear up, ~500 for glossy, and anywhere from 1,000-3,000 if you have complex reflections, glass, volumetrics, etc. This can be brought down with certain settings, and the use of the denoiser.
– Drudge
Aug 28 at 19:21






By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Popular posts from this blog

𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

How do I collapse sections of code in Visual Studio Code for Windows?

ャフサォクコ ケウ,コ,ワ メ,ロスョノ゙,クネ,フムカヤヲニ,エコ゚ツ ウイオン゙ケワサネォキモュキォウイノンコチ゚メヌナイゥフュ,カヒウネェ ネ,ホノケ,ムュキ ッボーミュハ,チ ツス ィ メウイマヤ,゙ウチ ヅ ロ,ォジヌェ ャヌット ェ,マャ,チナエヒネソキツテ トホヲヲミーァ