Vray Triaplanar normal maps an uv error

Hi,

So im getting this error with using normalmaps and triplanar. Scene attached. Pretty sure I’ve seen this on previous vray versions.

Using :

  • GPU rtx,
  • maya 2022.1,
  • recommended nvidia drivers,
  • 2080ti
  • V-Ray 5 for Maya, update 1.2 (v5.10.22, revision 30963 from Sep 1 2021)

So i have 4 flat planes, with vraymatl and normal map using triplanar. If you look at the image, plane 01, is default, plane 02 has UV’s that are incorrect and Plane 03 has no uv’s. And with those the normal map issues occur.

Also for some reason the background color, of the bump render element is different between cpu and gpu…bit odd.

Presumably there shouldnt be any interaction with UV when using triplanar?


Example of corrupt UV (plane 02)


_bugs.zip (150 KB)

Hi Franco. It’s my understanding that you shouldn’t use normal maps with vray triplaner. They don’t work. And still require good uvs which kinda defeats the purpose of projection. Plenty of discussions here. I would stick to Grayscale bumps and projection mapping.

Thanks for the report. Triplanar projected normal maps should work regardless of objects’ UVs. I’ve logged the issue (internal bug-tracker id: VGPU-5597) for developer investigation. Not sure why the background color is different, to be honest. I’ll ask around.

Depends what your definition of working is…

The link below you acknowledge there is an issue with normal maps and UV randomiser
https://forums.chaosgroup.com/forum/…-uvwrandomiser

The link below Vlado acknowledges there is an issue with normal maps and vray triplaner.

https://forums.chaosgroup.com/forum/…-problem/page2

The link below there is confirmation that the orientation of uvs effects normal maps

https://forums.chaosgroup.com/forum/…ffected-by-uvs

There have been many requests to finally put an end to this conversation about using normal maps with projections, but yet again it’s here… again and you are still promotomg its use

I noticed this bug is still in V-Ray 5 for Maya, update 2.2 (v5.20.02, revision 31249 from Feb 9 2022). Any ETA?

We do know the source of the issue, however, we have not yet started fixing it. Can’t give an exact estimate, however, I’ll bump its priority additionally.

This one is kind if a big deal. For automotive interiors it basically means UV-ing loads of CAD data, or using bump maps instead of normals. Not the end of the world, but not ideal either.