Hi All -
Been playing with Vray fur to make some grass and it was working okay but I have run into an intermittent problem with some buckets rendering oddly - pls. see the attachments. They are noisy but that doesn't affect the issue at all. The problem looks kind of like jpg artifacting or a DR problem - but it isn't either of those.
The fuzzy background is a plane of Vray fur (actually 3 of them to add variety) and the foreground object is another set of 3 vray fur objects growing out of an object. I get this issue with 1, 2 or 3 of the vray fur active.
This happens with or without DOF on - it's just easier to see the pattern with it, and it happens with all the different GI methods, with and without DR active, and with varying bucket sizes. The odd thing is that sometimes just turning off the Vray fur item or changing a parameter seems to make it go away or render differently (the odd buckets do vary every time you render it though)
It's a bit hard to predict and it ruined a 4 hour render today - is this a known bug or there something that might cause this?
Been playing with Vray fur to make some grass and it was working okay but I have run into an intermittent problem with some buckets rendering oddly - pls. see the attachments. They are noisy but that doesn't affect the issue at all. The problem looks kind of like jpg artifacting or a DR problem - but it isn't either of those.
The fuzzy background is a plane of Vray fur (actually 3 of them to add variety) and the foreground object is another set of 3 vray fur objects growing out of an object. I get this issue with 1, 2 or 3 of the vray fur active.
This happens with or without DOF on - it's just easier to see the pattern with it, and it happens with all the different GI methods, with and without DR active, and with varying bucket sizes. The odd thing is that sometimes just turning off the Vray fur item or changing a parameter seems to make it go away or render differently (the odd buckets do vary every time you render it though)
It's a bit hard to predict and it ruined a 4 hour render today - is this a known bug or there something that might cause this?
Comment