Proxy with SSS and Glas Material renders incorrect

Hi,

Simple Scene: A Glass Object with Milk ( SSS ) Material inside renders not correct if I render it as proxy object. The Fog color seams not to working properly. It always appears much more green than it should.

Scene Files are attached.

kind regards

Jonathan


proxy_prob_test.zip (2.99 MB)

Keep the glass and the milk as separate proxies and it should be fine. You’ve merged them in one when exporting and that is messing up the refractive shader.

Thank you!

“You’ve merged them in one when exporting”
Yea actually I do this very often because that is what I like with proxy objects :slight_smile:

Would you recommend to separate objects always as separate proxys or only when working with refractive materials? Or is this some special case because of the SSS Material ?

kind regards

No, not always. Overlapping volumes with refractive materials may cause problems.

What exactly do you mean with outer and inner polygons. Are you talking about surface/material IDs? I have only two material ID?s in the scene and i dont change them after I export the proxy object. So the surface ids shouldn?t change after exporting the proxy objects?!

Also if you compare the proxy with original mesh you can see the IDs are the same!

I also checked that. If I extract the mesh again from the proxy all the IDs are fine.

But I discovered now that it even renders wrong if I attach the original Mesh to one Object without to create a proxy at all. Than the error occurs.

So maybe this is the error that I cant have a single object with different refractive shaders? At least the fog value seems to mess up somehow.

kind regards

It seems that VRayFastSSS2 causing the issue we are considering this as a bug for now as a workaround you can keep the object separately or use different material instead of VRayFastSSS2 like VRayScatterVolume or VRayALSurfaceMtl.

I remember some issues with SSS and/or refraction in relation to materialIDs and not seperate objects. Don’t know what exactly it was back then, maybe it is fixed now, but it may be the same issue and may not have to do with proxies.