Proxies, invisible lights and coverage/renderID elements

[jensl]

Hi guys,

I've been having some issues with renderID and coverage, using nightly 08-17-2010. I have a fairly large scene with lots of objects, and it seems renderID is running out of colors (haha), or is having an issue with a V-Ray proxy. The bush all the way to the right is not a proxy and shows up in renderID, whereas the other bushes in the middle are missing and are proxies. The new coverage pass is great, but currently lights render into it, even when they are invisible (that's what those squares are), and the proxied bushes are also missing. Last image is the diffuse pass, for comparison. Thanks,


Jens

[Zdravko]

It seems like there is some kind of transparent geometry that blocks the render elements to see the heel behind?
Also, I will forward your lights/coverage pass request to our developers.

[jensl]

Hi Zdravko,

I have updated the first post with screen grabs, there is no transparent geo blocking things. All of the rear bushes and rear hill are part of one proxy, even though they were separate objects in Maya. When I created the proxy, they were separate geo but once they are one proxy they are one object, and get only one color in renderID. It would be useful if objects could be individual within a single proxy, or if renderID could take this into account (maybe this is a feature request, is it possible?). I don't see why they shouldn't still show up in coverage, though, as they need anti-aliasing just like anything else. Thanks,

Jens

[vlado]

For the proxies, you can try using the material ID instead of the render ID. As for the coverage element and the lights - this looks like a bug and I'll look into it.

Best regards,
Vlado

[jensl]

Hi Vlado,

I've gotten around the coverage/renderID problem by switching the V-Ray Proxy export options to 'Export each selected object in a separate file.' In a quick test, there's no interactive render speed difference between 300 vrmesh files and 1 big 20mb vrmesh file, which is great, as I had thought loading 300 small files would be much slower than loading one large one. This method creates 300 more shaders, shading groups, vraymeshNodes, and expressions, though. It seems bugged to me that even when 'export animation' is off, an expression for vraymesh.currentFrame is created for each proxy. Shouldn't this be removed for non-animated proxies, or perhaps be a direct connection. This seems to need a timeToUnitConversion node, but as I understand it anything is faster than an expression. I still wish a single vrayProxy could consist of multiple objects for simplicity and efficiency. Thanks,


Jens