Although V-Ray does not yet support some Cycles nodes, I think it would be very convenient if it did.
What nodes do you have in mind specifically?
These nodes for the most part have direct alternatives in V-Ray. RGB Curves is VRayRemap and the Gradient/Ramp combo is our Gradient Ramp texture. The UVW mapping is assigned slightly differently in V-Ray but that’s just how V-Ray works. Can you describe in more detail what exactly is missing from our nodes and what you prefer about the Cycles ones?
This isn’t a matter of choosing one over the other — many Blender assets are built with Cycles nodes. Converting everything to V-Ray nodes is messy and unnecessary. Since V-Ray already supports Cycles nodes, it would be practical to let us use them directly for tweaking simple materials.
Hey @binjun_wu ,
I understand the reasoning why you prefer having the cycles node available for editing in the V-Ray Node editor, however there are some cases where a material needs to be fully converted to work correctly within V-Ray. Also leaving all Cycles nodes available for creation in the V-Ray Node editor isn’t the most friendly thing for a beginner V-Ray user and might produce more confusion than solve a particular workflow.
If we find a good middle ground we will for sure find a way to expose them.