Itoo Software Forum

Author Topic: Rendering issues With VRayClipper and 5.07B  (Read 789 times)

Torgeir Holm

  • Newbie
  • *
  • Posts: 4
Rendering issues With VRayClipper and 5.07B
« on: June 21, 2016, 01:43:00 PM »
I'm having some issues with Forest Pack Pro 5.07B and the VRayClipper in our current project. We will have animated VRayClippers in the scene to expose interior parts of the scene.
Basically the geometry is clipped, but part of the clipped Forest Pack Pro objects seem to punch a hole in the alpha channel. This is more visible the closer we get to glancing angles. Please see the attached images. I can also upload a simplified scene that replicates this.

Michal Karmazín

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1376
Re: Rendering issues With VRayClipper and 5.07B
« Reply #1 on: June 21, 2016, 03:53:06 PM »
Hi,

First let me mention, that the VRayClipper is a render-time effect and does not modify the actual scene geometry in any way. As mentioned in Chaos Group's documentation: "Currently the VRayClipper may produce artifacts if there are overlapping triangles in the scene, regardless of whether they are part of the same object or not."

Might be, V-Ray exceeded its default transparency limit on this parts (which causes these render artefacts). I would suggest you to increase Global switches->Max transp. levels (default value is 50). Sometimes may be necessary to modify Secondary rays bias also.

Please feel free to check following  post "Some key notes about Areas-Boundary Checking-Edge mode" covering related topic (even this mode isn't used as the VRayClipper works in a similar way).

Best regards,

Torgeir Holm

  • Newbie
  • *
  • Posts: 4
Re: Rendering issues With VRayClipper and 5.07B
« Reply #2 on: June 21, 2016, 05:49:13 PM »
Ah, of course! I had to crank it all the way up to 500 to get rid of the artifacts, it being a grass lawn and all. But it still renders fast. I didn't think the clipped geometry would count against the transparency level count.  I'll suggest to Chaos Group that they mention this kind of case, and the solution, in the VRayClipper docs. Thank you for the swift reply.