This may sound like a trivial question, and I'm referring to vray v5 so it's possible that my issue has been fixed.
So I'm thinking of converting materials that have previously used the 3ds max bitmap texture to those using the vraybitmap texture. In the material/bitmap navigator the name of the bitmap is shown automatically for max bitmaps but apparently not for vray bitmaps. See the attached file - look at "ColorC Layer 3 (Mask): Map #86" where the long file name follows. Compare that to ColorB Layer 2 (Mask): Map V-Ray for Maya :: General where all that follows is VrayBitmap. I know that I can type in the file name instead of "Map 86" but I'd just as soon avoid that step, as it would add unnecessary time, because I make a lot of these materials and just copy the material, click on the files in navigator and swap them for a different one. Seeing all the names automatically makes it much more convenient.
Am I missing something? Would this be an easy programming fix? I don't imagine anyone would want to do this for v5, but if it's the same problem in v6 and it was fixed for that version it would help nudge me into upgrading .
thanx --ds
So I'm thinking of converting materials that have previously used the 3ds max bitmap texture to those using the vraybitmap texture. In the material/bitmap navigator the name of the bitmap is shown automatically for max bitmaps but apparently not for vray bitmaps. See the attached file - look at "ColorC Layer 3 (Mask): Map #86" where the long file name follows. Compare that to ColorB Layer 2 (Mask): Map V-Ray for Maya :: General where all that follows is VrayBitmap. I know that I can type in the file name instead of "Map 86" but I'd just as soon avoid that step, as it would add unnecessary time, because I make a lot of these materials and just copy the material, click on the files in navigator and swap them for a different one. Seeing all the names automatically makes it much more convenient.
Am I missing something? Would this be an easy programming fix? I don't imagine anyone would want to do this for v5, but if it's the same problem in v6 and it was fixed for that version it would help nudge me into upgrading .
thanx --ds
Comment