VRay Clipper issues - dirty clipper

I am using a VRayClipper object to cut away some portions of my scene. I am using the ‘replace mesh with clipper’ option, and the object is a simple box. For some reason, I am getting a lot of dirty edges as you can see in the attached render. It is almost as if there is co planar geometry or something, but all this area should be clipped out anyway (not that there is any coplanar stuff happening in any case).

This isn’t the only project where I have seen this. We had another job with the same problem, but we managed to paint out the problem areas.

Any ideas how to solve this? I need the clips top be clean as we are animating this. This is quite urgent.

Hello,

It would be best if you could send us the scene? Also what are your Max and V-Ray version?

Best regards,
Yavor

Hi Yavor - can you let me know what email to send to please?

We are using VRay 3.60.02 and Max 2016. I tried upping the Max transp levels from 50 to 500 but it made no difference.

I have just PM’d you a link Yavor

Thank you, got it. Will write back when I find something.

Don’t suppose you’ve figured anything out?

Mmm. When I looked at the dirty area, I thought it looked a bit like the geometry of some of the trees in the scene (even though there are no trees in this area). I excluded my ForestPro objects from the clipper object and the problem appears to have gone. The Tree models (inside the ForestPro objects) are VRayProxies. Is there an issue with VRayClipper and VRayProxies perhaps?

In the scene you’ve sent - which camera and which frame is the problem one? Trying to reproduce it here but no luck so far.

There isn’t any specific issue with VRayClipper and VRayProxies that I know of.

Camera was the un-named physical camera. Frame doesn’t matter as that one isn’t animated. You don’t have the vrayproxies with the file I sent. I will send you a link to those too.

EDIT: I’ll send a link to the entire archived project so you have everything. Hold fire…

Try to raise the max transparency levels.

Made no difference unfortunately. It seems to have something to do with Forest Pro or VRayProxies I think, but waiting for support to check it out.

Still no luck with the newer file. Here’s what i get so far:

One other thing (but I doubt it) - I’m currently using Forest Pro 6.0.1b and RailClone 3.10, what are your versions ?

I had excluded the FP objects from the clipper. Try removing them from the exclusion list. I am using FP version 5.4.1 and RC version 3.0.9

Any luck Yavor?

Yes now I see the issue. Excluding the forest seems like a valid solution while I check why is it needed in the first place.

It’s indeed because of some of the tree models around the building - specifically “Forest RhineVeg”. The tree models have single sided leafs that throw off some of the clipper calculations.

Is there an easy way to fix that?

Excluding the forest from the clipper seems like the easiest solution.