VRay 5 GPU/RTX doesn't support 2nd UV channel...or normal maps?

[HowardDay]

Okay, I'm using a material with a couple of OSL shaders being used to distort UVs for parallax mapping, and I'm running into some strange behavior/bugs.
The first issue - using a 2nd UV channel in the material. It works in CPU:

But not in GPU. In GPU mode I get something that looks like it's using some sort of "default" channel mapping?

When I remove the 2nd channel usage, it goes back to using the 1st channel, but you get obvious stamping of the interiors:

I'd really like access to that 2nd channel.

The second issue is that Normal mapping is not working in RTX mode. Here's just the normal and opacity map in CPU:

Nice shading, fits the normals, works great.
Now, same shader in GPU/RTX:

Nothing.
Here are my test scenes.
GPU UV#1 (normals broken):
https://drive.google.com/file/d/1n_c...ew?usp=sharing
GPU UV#2 (normals broken, UVs broken):
https://drive.google.com/file/d/1-CL...ew?usp=sharing
CPU UV#2 (normals ok):
https://drive.google.com/file/d/1RQY...ew?usp=sharing

I'm also seeing massive progressive slowdown in rendering these tests - as described here:
https://forums.chaosgroup.com/forum/...n-rtx-gpu-mode

Please help.
Thanks!

[HowardDay]

VRayNormal map is stated as being supported in GPU mode. https://docs.chaosgroup.com/display/...orted+Features

[HowardDay]

Reported to support. Ticket #307-345-0816

[HowardDay]

Any idea on this one..or two? Normal maps not working really seems weird.

[hermit.crab]

Thank you for the provided scenes. Both of the issues are due to some unsupported parts of the OSL code (in the OSL UVW node in this case) in V-Ray GPU. I have logged them for support implementation (internal-bug tracker id: VGPU-4925, VGPU-4924). I have also informed our development team about the matter. The issues are related to your other topic here.

[ikomitov]

Alternative UVW channels (i.e. the "UV%d", "uv_%d", "w", and "w_%d") are not supported at the moment but we are working on implementing them. However the GetUVW.osl and similar shaders would still have to be modified to avoid any dynamic string operations (like format("UV%d", UVSet)) to make them work on the GPU.

Best regards,
Ivan

[HowardDay]

Okay, thanks guys! Would you consider releasing your own set of UVW OSL operators that *would* work with GPU? (once it's supported, of course)

[ikomitov]

Sure, I'll try to make a drop-in replacement for the entire GetUVW shader.

Best regards,
Ivan

[HowardDay]

Any updates on this? I'm back in this, almost 4 years later, and it still seems completely unsupported. :/