AO pass black - Cycles - Latest build

I am using the build from 24 april, cycles, windows 10.
Before when I enable the AO pass in the renderlayers, I get indeed an AO pass. ( Of which I still didn’t figure out how to mix it properly in the compositor by the way. I did a mixture of multiply and overlay. )
Now with this build I noticed that the AO pass gives a black render, unless I enable under world settings AO, which is not what I want because that effects the image render layer as well.

Could it be a setting I accidentally turned on, or did they change something, or could it be a bug ?

Have you tried it in an official release build? If it works in there, but not in the later build, you might want to report it as a bug.
More likely you’re going to get a black result in the official release as well, in which case you should upload your .blend file so we can have a look!

I’m no good at cycles, but I think this is how it’s done…
Leave AO on in the world, and create a new render layer…


That seems to work on my end, but I don’t know. :slight_smile:

Have Fun!

Skip

@benu, I will attach the blend file here ( I did a factory reset first so it will be a very clean blend file ) . Indeed the problem doesn’t occur with earlier versions of blender.

@SkpFX, Your solution seems to work, though isn’t it that blender is now rendering twice ? I also have the idea that the AO in the world settings gives other results than the AO pass.
See blend file attached. ( From blender build 23-04-2016. )

Confirmed (OS X):
It works in the 2.77a release on my machine:

But it renders black in a buildbot version that I just downloaded:

Attachments



I think this is a bug, by the way. Enabling AO for the scene (so it is visible in the base render) does allow it to show up in the AO pass. I don’t think this is intentional. Somehow, adding the “Use AO” feature has muddled things up. Anyone feel otherwise?