Title pretty much says it all, it appears that my triplanar texture in vray RT (CUDA GPU) is being ignored in both the bump and refraction amount slots. I can post pics and a scene when I get to work in the morning if necessary.
Hi,
Which V-Ray build is that ?
Make sure that you are using only bitmaps with our Triplanar node in GPU, because won’t work with procedural maps.
I’m on the latest stable release. I’ve got a file texture going into a remapValue node, then into a triplanar. Would that cause an issue?
A scene would be helpful, yes. Please attach one if possible, so we can have a look.
Here’s a scene file: https://drive.google.com/open?id=0B790tcPr5l7CNGdnUndtaVh4cWc
I’ve uploaded a few picture that show the problem. The fist image is the CPU, second is GPU. Left side is triplanar with file texture, right side is standard file texture. The third picture shows that the GI pass sees the triplanar correctly, but as soon as it hits the second rendering stage it loses it. It does the same thing for bump except the bump map shows up a little bit very lightly, no amount of increase in bump amount changes the look. It also does the same thing in the GI pass, i could only upload five images.
Refraction amount.
Bump
Thank you for the file.
The first problem with V-Ray triplanar node and refraction amount slot is fixed for the next service pack release. However, the second one when its in the bump slot has been forwarded to our developers for a further investigation. We will let you know when we have any news.
Any news on why triplanared bitmap bump maps doesn’t work?
Hi,
We have some improvements on this actually in the latest builds. What is the difference you are getting, between CPU and CUDA render ? Can you send us the problematic scene and screenshots to support@chaosgroup.com ?
can I get some clarification on this, I’m using the latest release, not nightlies, and triplanar doesnt work with normals and cuda…is this correct?
(video attached)
triplanar_normals.zip (1.45 MB)
Hi,
It doesn’t work on V-Ray Next GPU yet, but we are working on it right now. So when we have a build and all QA tests passed, will let you know.
i just realized this post started in 2017…thats bad.
yes indeed, perhaps it was a bit down in the list. However, we are testing the potential fix and if everything goes well, will be added to the nightly builds.