Customdata render element, strange result

Hi guys,

Here’s an attempt to use a custom render element:

dropbox.com/s/9ezo5uvp7oo6m … 1.png?dl=0

These are two PRT loaders, I’ve assigned red to one and green to the other, and I’ve assigned the same colors in the custom render element. I was expecting the result to be the same, but it’s not. Multiplying by the density didn’t give a correct result either.

Basically, I want to make a PRTId render element so comp can control them separately, and it would be great if i can avoid rendering twice, and use the custom render elements.

Thanks!

Is the Filter option turned off?

It’s on.

And what happens when it is turned off? :slight_smile:

Not the correct thing either - I’m getting what’s expected without filtering, but wrong again.

What is wrong with it? Send an image.

There is a screenshot at the dropbox link at the OP.

Here’s the image:

dropbox.com/s/9ezo5uvp7oo6m … 1.png?dl=0

Here is my test using a teapot and a cylinder, converted to PRT Volumes.
Lit by one Omni light.

I added a Magma to each PRT Volume and set the Mapping2 channel to a different color (pure red, pure green).
I then added a Custom Data Render Element and output Mapping2 as the render element data. Set Filter to off.
As you can see, the render element output represents in pure color value the closest particle to the camera, no shading at all.

If I enable filtering, the particles would be drawn using the current (Bicubic) filter, so where a particle partially overlaps a pixels, you might get a mixture of red and green. With Filter OFF, all pixels partially overwritten by the closest particle will have the pure color of that particle.

Knowing this, where did you get it wrong?

Same thing - I redid it in a test scene and it works. Something might be messing up the original scene. I’ll check eventually, quite busy now :slight_smile: Thanks!