Anyone else notice that the V-Ray MultiSubTexture does not work in the Fog Color slot? Is there a reason for this? Using V-Ray 3.10.01 btw.
thnx,
-chad
Anyone else notice that the V-Ray MultiSubTexture does not work in the Fog Color slot? Is there a reason for this? Using V-Ray 3.10.01 btw.
thnx,
-chad
Great thanks!
Svetlozar,
Try changing the the “Get ID from” to Random by node and you’ll see it does not work.
I managed to reproduce that - thanks for the clarification.
The following modes of VrayMultiSubTex do not work inside FogColor slot of VrayMtl:
Object ID / Random by Node Handle / Random by Render ID / Random by Name
A note about this issue has been added into our system - we will let you know when we have some news on that matter.
bump this old crusty bug
Hi @piotrus3333 , we’ve haven’t fully resolved this yet - I will make sure to bump its priority additionally (internal bug-tracking number ID: VMAX-2850).
It appears that if you render with Standalone (right-click in your scene > Export and Render) or with GPU (on CPU mode) it gets the right results for all modes except ParticleID and InstanceID. Please check if this would be a suitable workaround for you until we fix this. Thanks for the patience!
Ahah, you gave me a hearty giggle.
Well done!
I just badly needed it to work and since I had seen your post mentioning VRayPluginNodeTex I’ve been exploring a bit.
houdini nodes in max. fancy or what? haha
Right?
It’s one of the very best features of V-Ray, and possibly the one known the least. ![]()
I don’t see these noise types in the rollout. Are they in some other update that maybe I don’t have?
There’s a ton of stuff in it (f.e. Phoenix, Maya, Modo, XSI, Nuke) which is otherwise inaccessible.
Mind you, it’s meant for translation (i.e. vrscene) and not for direct use, so it’s not for the faint of heart (some things are really not meant for manual use, and won’t work via UI).
But it’s *mostly* very usable. ![]()
No problem, I can get a nightly - thanks.