Tweet
Hi,
I am not sure if this is a bug or designed function. I extracted normal maps from a model that has 20 tiles in Mudbox. Since I didn't sculpt details in each tile, I only export say 6 tiles out of 20. (ex. I only have tile 1, 2, 5, 6, 7, 15 exported and stored in the hard drive)
When rendering, the areas that correspond to the tiles that are not existing in the hard drive are rendered with incorrect black splotches. A workaround I found is to manually create neutral normal maps in Photoshop (each one with solid neutral purple color) to feed information for VRay, then the render looks correct.
This issue didn't happen on displacement rendering. I guess Vray treats non-existing tiles as solid black and hence doesn't displace the surface during rendering.
I expect that for scalar maps (bump, displacement, or normal), if a tile isn't existing, VRay won't affect the surface.
I am not sure if this is a bug or designed function. I extracted normal maps from a model that has 20 tiles in Mudbox. Since I didn't sculpt details in each tile, I only export say 6 tiles out of 20. (ex. I only have tile 1, 2, 5, 6, 7, 15 exported and stored in the hard drive)
When rendering, the areas that correspond to the tiles that are not existing in the hard drive are rendered with incorrect black splotches. A workaround I found is to manually create neutral normal maps in Photoshop (each one with solid neutral purple color) to feed information for VRay, then the render looks correct.
This issue didn't happen on displacement rendering. I guess Vray treats non-existing tiles as solid black and hence doesn't displace the surface during rendering.
I expect that for scalar maps (bump, displacement, or normal), if a tile isn't existing, VRay won't affect the surface.
